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

SSH

Gathering Basic Troubleshooting Information

Most connection problems can be solved by running sshg3 in verbose mode and examining the output.

Enter the command -v (or --verbose) to get the diagnostic output:

$ sshg3 -v user@server.example.com

You can also get the diagnostic output from the old connection attempts afterwards. The following command lists the old connection attempts and their connection IDs:

$ ssh-broker-ctl list-connections --disconnected

The following command shows the diagnostic output from the old connection attempts:

$ ssh-broker-ctl connection-status <connection-id>

On Windows, the Tectia - SSH Terminal provides error dialog messages for failed connection attempts. Moreover, you can get the connection information and the last 5 messages displayed by the Tectia ConnectSecure by opening the Tectia - SSH Terminal and selecting HelpTroubleshooting.... A window like the one shown in Figure 7.1 is then opened.

Window containing troubleshooting data

Figure 7.1. Window containing troubleshooting data


 

 
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