Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

kaicho

Re: * Access denied * No supported authentication methods left to try!

I could not determine this from the messages log, it says only that the connection was refused.

I was able to get in as user with WinSCP, transfer files to home directory, then in Putty as root, copy them to the right place.

Tried generating ssh2 keys per putty help, no success.
martin

Re: * Access denied * No supported authentication methods left to try!

Check your server log to see reason why it denies you to login. Maybe root is allowed to login only using interactive terminal (Putty) and not with non-interactive session (WinSCP). This rule generally applies to 'su' command, so it may apply even to normal login in you case.
kaicho

* Access denied * No supported authentication methods left to try!

I love this program, no problems on other systems. I posted this once but don't see it, trying again, sorry if I goofed.

host: Linux i686 2.6.5-gentoo
client: wxppro (new computer)

login error:

Authentication log (see session log for details):
Using username "root".
Access denied
No supported authentication methods left to try!

Connection has been unexpectedly closed. Server sent command exit status 0.

I CAN connect with Putty as 'root' but can NOT connect with WS, even as user.

I have removed and reinstalled several times, including registry entries left by uninstall. Each time I accepted proposed key.

I have run the following on the host:
ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key

ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key

WinSCP log from latest attempt after reinstall:

. ----------------------------
. WinSCP Version 3.4.2 (Build 197)
. Login time: Sunday, June 20, 2004 1:22:59 PM
. ----------------------------
. Session name: root@192.168.0.7
. Host name: 192.168.0.7 (Port: 22)
. User name: root (Password: Yes, Key file: No)
. Transfer Protocol: SFTP
. SSH protocol version: 2; Compression: No
. Agent forwarding: No; TIS/CryptoCard: No; KI: Yes
. Ciphers: aes,blowfish,3des,WARN,des; Ssh2DES: No
. Ping interval: 60 sec (0 = off); Timeout: 15 sec
. SSH Bugs: -,-,-,-,-,-,-,-,
. Proxy: none
. Return code variable: Autodetect; Lookup user groups: Yes
. Shell: default, EOL: 0
. Local directory: default, Remote directory: home, Update: No, Cache: Yes
. Clear aliases: Yes, Unset nat.vars: Yes, Resolve symlinks: Yes
. Alias LS: No, Ign LS warn: Yes, Scp1 Comp: No
. -------------------------------------
. Looking up host "192.168.0.7"
. Connecting to 192.168.0.7 port 22
. Server version: SSH-2.0-OpenSSH_3.7.1p2
. We claim version: SSH-2.0-WinSCP-release-3.4.2.197
. Using SSH protocol version 2
. Doing Diffie-Hellman group exchange
. Doing Diffie-Hellman key exchange
. Asking user:
. The server's host key is not cached in the registry. You have no guarantee that the server is the computer you think it is. The server's key fingerprint is: ssh-rsa 1024 4b:ff:ed:6c:10:85:ab:e0:e6:ea:2b:d9:44:06:9a:9d
.
. If you trust this host, press Yes. To connect without adding host key to the cache, press No. To abandon the connection press Cancel.
.
. Continue connecting and add host key to the cache? ()
. Host key fingerprint is:
. ssh-rsa 1024 4b:ff:ed:6c:10:85:ab:e0:e6:ea:2b:d9:44:06:9a:9d
. Initialised AES-256 client->server encryption
. Initialised AES-256 server->client encryption
! Using username "root".
. Server prompt (Password: )
! Access denied
. Access denied
! No supported authentication methods left to try!
. No supported authentications offered. Disconnecting
* (ESshFatal) Authentication failed.
* Authentication log (see session log for details):
* Using username "root".
* Access denied
* No supported authentication methods left to try!
*
* Connection has been unexpectedly closed. Server sent command exit status 0.