View Single Post
Old 06-20-2016, 07:04 PM
jdev's Avatar
jdev jdev is offline
VanDyke Technical Support
Join Date: Nov 2003
Location: Albuquerque, NM
Posts: 955
So you already have some sessions configured to use others as a firewall (like in a jump host or gateway scenario where your jumphost/gateway is an SSH2 server and you need to get to hosts behind that machine)?

What version of SecureCRT are you using?

If you have a session already configured to connect via a "firewall" that points to another session, you won't need to connect to the "firewall" session first... SecureCRT will automatically connect to it and set up the port forwarding necessary to get through to the secondary host behind the gateway/jumphost.

What specific errors are you seeing?

If you need further assistance with troubleshooting, please send Trace Options output to Trace Options output is best generated by performing these steps:
  1. File -> Log Session, and specify a name for the log file to be generated. Something like %APPDATA%\..\..\Desktop\SCRT_Log.txt will work if you're on Windows.
  2. File -> Trace Options. This won't do anything super fantastic immediately... other than enabling a check-mark for the menu item next time you open the File menu to let you know that it's on/active.
  3. Attempt your connection to the session configured to connect to the secondary host (has as its firewall configuration the session that connects to your gateway/firewall host)
  4. With Trace Options output enabled, you should see a good deal of debug information in SecureCRT's terminal window. Once the connection attempt fails, turn off logging (File -> Log Session again to toggle logging off) and then send the captured log file to for further assistance. Don't post this information to the forums, as it can contain sensitive information that I doubt you'll want to be made publicly available to all who visit here.

Jake Devenport
VanDyke Software
Technical Support
YouTube Channel:
Reply With Quote