[Contents] [Index]

Introduction >>     Configuration >>     Connecting >>     Terminal Window >>     File Transfer >>     Toolbar Reference >>     Menu Reference >>     Advanced Information >>     Troubleshooting >>         Error Dialogs At Startup>>         Error Dialogs During Operation >>             Authentication Failure             Confirm Disconnect             Confirm File Overwrite             Connection Failure             Disconnected; Authentication Error             Disconnection             Enter Passcode             Enter Passphrase For Private Key             Enter PIN             Error Renaming             Failed To Create An Incoming Tunnel             Host Identification             Host Identification Failed             New PIN             PAM Response             Password Needed for PFX Integrity Check             The Remote Host Uses SSH1 Protocol             Wrong Passphrase             Wrong Password - Enter Again         PKCS #11 Keys>>         SSH1 Specific Error Messages >>     Appendices >>

Disconnected; Authentication Error

The error message "Disconnected; Authentication Error (No further authentication methods available.)" indicates that any of the methods that have been used to authenticate you to the server have not been successful.

A relatively common situation is one where the remote host computer is expecting public-key authentication to be used and you have not sent your public key to the host. You can do this by following the instructions in section Uploading Your Public Key.

This error is also produced if the system's name server is not doing reverse lookups correctly. Ask your system administrator to configure the name server so that it does reverse lookups properly.

If this is not possible, the system administrator has to edit the file /etc/ssh2/sshd2_config on the Secure Shell server and change the RequireReverseMapping setting to no.

This is a common problem for modem connections. Typical modem connections use dynamic IP addresses. This means that the IP address changes from one connection to another, and these dynamic IP addresses have no permanent name server entries in the Domain Name System (DNS). If this is the case, you will have to ask your service provider to edit the sshd2_config file on the SSH server.