Emergency: Disconnected: No supported authentication methods available

From: Gentian Hila (genti.tech_at_gmail.com)
Date: 05/31/05

  • Next message: David Surkov: "Unable to get shell prompt after logon" 
    Date: Tue, 31 May 2005 10:43:46 -0400
To: secureshell@securityfocus.com

    Hi,

    I had openssh server working fine on RedHat ES 3, now I cannot connect
    anymore. It disconnects me and says Disconnected: No supported
    authentication methods available. I login as root and root was working
    fine earlier.

    Here it is a debug from sshd

    [root@server1 tec]# /usr/sbin/sshd -d
    debug1: sshd version OpenSSH_3.6.1p2
    debug1: private host key: #0 type 0 RSA1
    debug1: read PEM private key done: type RSA
    debug1: private host key: #1 type 1 RSA
    debug1: read PEM private key done: type DSA
    debug1: private host key: #2 type 2 DSA
    socket: Address family not supported by protocol
    debug1: Bind to port 22 on 0.0.0.0.
    Server listening on 0.0.0.0 port 22.
    Generating 768 bit RSA key.
    RSA key generation complete.
    debug1: Server will not fork when running in debugging mode.
    Connection from *********** port 1807
    debug1: Client protocol version 2.0; client software version PuTTY_Release_0.58
    debug1: no match: PuTTY_Release_0.58
    debug1: Enabling compatibility mode for protocol 2.0
    debug1: Local version string SSH-1.99-OpenSSH_3.6.1p2
    debug1: permanently_set_uid: 74/74
    debug1: list_hostkey_types: ssh-rsa,ssh-dss
    debug1: SSH2_MSG_KEXINIT sent
    debug1: SSH2_MSG_KEXINIT received
    debug1: kex: client->server aes256-cbc hmac-sha1 none
    debug1: kex: server->client aes256-cbc hmac-sha1 none
    debug1: SSH2_MSG_KEX_DH_GEX_REQUEST_OLD received
    debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent
    debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT
    debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent
    debug1: SSH2_MSG_NEWKEYS sent
    debug1: expecting SSH2_MSG_NEWKEYS
    debug1: SSH2_MSG_NEWKEYS received
    debug1: KEX done
    debug1: userauth-request for user root service ssh-connection method none
    debug1: attempt 0 failures 0
    debug1: Starting up PAM with username "root"
    Failed none for root from *********** port 1807 ssh2
    debug1: PAM setting rhost to "****************"
    debug1: userauth-request for user root service ssh-connection method
    keyboard-interactive
    debug1: attempt 1 failures 1
    debug1: keyboard-interactive devs
    debug1: auth2_challenge: user=root devs=
    debug1: kbdint_alloc: devices ''
    Failed keyboard-interactive for root from ************* port 1807 ssh2
    Received disconnect from *************: 11: No supported
    authentication methods available
    debug1: Calling cleanup 0x806f140(0x0)
    debug1: Calling cleanup 0x8063b10(0x0)
    [root@server1 tec]#

    I changed the ip and host name to ******************* just for
    security purposes.

    I have openssh-server-3.6.1p2-33.30.4 installed

    Please help, I need it to work remotely.

    Thank you

  • Next message: David Surkov: "Unable to get shell prompt after logon"

    Relevant Pages

    • Re: using rsa to log on without password
      ... > debug1: No more authentication methods to try. ... > Any idea why DSA disabling impacts the use of rsa keys? ...
      (comp.security.ssh)
    • pam-1@ssh.com authentication & OpenSSH
      ... debug1: Reading configuration data /etc/ssh/ssh_config ... debug1: read PEM private key done: type DSA ... Host 'pine.jhu.edu' is known and matches the DSA host key. ... No more authentication methods to try. ...
      (SSH)
    • Non root scp problem
      ... This is a production web server and the webmaster uses a non-root account to copy files constantly. ... debug1: Connecting to ares port 22. ... invalid collation element ...
      (SSH)
    • Ora-rg could not start using scswitch command!
      ... So oracle server could not be started. ... Is Shockwave Plugin available for Solaris??? ... debug1: read PEM private key done: type RSA ...
      (SunManagers)
    • SSH-Login via LAN ok, WAN fails (OpenSSH Windows, SecureCRT)
      ... v3.5p1-3 server with Public Key Authorisation. ... the 120 seconds idle timeout the connection is FINed. ... I have been reading OpenSSH's manuals, SecureCRT manuals, ... debug1: read PEM private key done: type RSA ...
      (comp.security.ssh)