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
            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 >>

Authentication Failure

This error message indicates that the authentication process between your local computer and the remote host computer has failed.

Possible reasons:

  • The most common cause for failed authentication is an incorrect password, likely caused by a typing mistake.
  • The user name may be incorrect. Check that you have typed it correctly.
  • One possible reason for authentication failure is that the remote host computer may have been configured to require several authentication methods to be used. For example both password and public-key authentication could be used for increased security. Even if you entered your password correctly, another required authentication method could have failed. A relatively common situation is one where the remote host computer is expecting public-key authentication 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.
  • It is also possible that your account on the remote host computer has been disabled, or that the remote host computer is having temporary problems that cause errors with the login procedure.

Try to connect again and carefully type in your user name and password. If after a couple of retries you are sure that you have entered both of them correctly, contact the system administrator of the remote host computer.

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




What to read next:

  • Reduce Secure Shell risk. Get to know the NIST 7966.

    The NISTIR 7966 guideline from the Computer Security Division of NIST is a direct call to action for organizations regardless of industry and is a mandate for the US Federal government.
    Download now
  • ISACA Practitioner Guide for SSH

    With contributions from practitioners, specialists and SSH.COM experts, the ISACA “SSH: Practitioner Considerations” guide is vital best practice from the compliance and audit community.
    Download now