Your browser does not allow storing cookies. We recommend enabling them.

SSH Tectia 
PreviousNextUp[Contents] [Index]

    About This Document>>
    Installing SSH Tectia Client >>
    Getting Started >>
    Configuring SSH Tectia Client >>
    Connecting to a Remote Host Computer>>
    Transferring Files>>
    Tunneling Applications>>
    GUI Reference>>
    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 >>
    Command-Line Tools >>

Disconnected; Authentication Error

The "Disconnected; Authentication Error (No further authentication methods available.)" message indicates that none of the methods that have been used to authenticate you to the server have 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 to do 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 Secure Shell server.

PreviousNextUp[Contents] [Index]


[ Contact Information | Support | Feedback | SSH Home Page | SSH Products ]

Copyright © 2010 SSH Communications Security Corp.
This software is protected by international copyright laws. All rights reserved.
Copyright Notice


 

 
Highlights from the SSH.COM blog:

  • Cryptomining with the SSH protocol: what big enterprises need to know about it

    Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency.
    Read more
  • SLAM the door shut on traditional privileged access management

    Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity?
    Read more
  • We broke the IT security perimeter

    Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so.
    Read more