Welcome to the VanDyke Software Forums

Join the discussion today!


Go Back   VanDyke Software Forums > Secure Shell

Reply
 
Thread Tools Display Modes
  #1  
Old 08-28-2018, 06:14 AM
jodyrex jodyrex is offline
Registered User
 
Join Date: May 2018
Posts: 3
Unhappy SSH for Avocent ACS5000 Console Session

I am unable to SSH to an Avocent ACS5000 console server connected to console ports on Cisco devices using Secure CRT. The methods below work so I feel confident that the issue is the string sent via Secure CRT to the console server.

1. Putty string: user:700x@x.x.x.x
2. CMDR shell string: ssh -l user:700x x.x.x.x

700x is the port number for each Cisco device. Port numbers range from 7001 to 7016.
x.x.x.x is the IP address of the console server.

The user name seems irrelevant since anything will work in Putty and CMDR but the SSH session will fail if a username isn't specified. I have not been able to successfully recreate the strings sent via SSH on port 700x in Putty or CMDR in Secure CRT.
Reply With Quote
  #2  
Old 08-28-2018, 09:13 AM
bgagnon bgagnon is offline
VanDyke Technical Support
 
Join Date: Oct 2008
Posts: 4,116
Hi jodyrex,

There's really not enough info here to help.

Please list the explicit steps taken to configure SecureCRT.

To my thinking, to match Putty's string, in a Quick Connect dialog (SSH2 protocol) in SecureCRT, you would put:

x.x.x.x in Hostname field
700x in Port field
user in Username field

If that fails, please send Trace Options output to support@vandyke.com per the below instructions.

Unless you only get about 5-10 lines of debugging info and one of those has something like "0 bytes sent, 0 bytes received" in it. In that case, you likely have personal firewall software blocking your outgoing connection. (Meaning an exception has been made for Putty, but not SecureCRT.)


To enable trace options output:
  • First, open SecureCRT's main File pull-down menu and select Trace Options. If you open the File pull down menu again you should see a checkmark next to Trace Options, indicating that troubleshooting output is now enabled.
  • Next, connect to the remote machine. With trace options enabled, you will notice debugging information displayed in the terminal window that isn't normally there by default when SecureCRT is attempting to establish a connection, and at certain times throughout the lifetime of the connection.
  • Once the problem occurs, please right-click inside the terminal window and choose Select All, then right-click again and choose Copy to transfer the information to the clipboard.
  • Finally, open a text editor, paste the information from the clipboard into the editor program, and save it as a text file.
Since trace options can contain sensitive information, feel free to send it as an attachment via email to support@vandyke.com. Please reference "Attn Brenda - Forum Thread #13231" in the subject line.

NOTICE: The requested troubleshooting data may include sensitive information (usernames, passwords, publicly-accessible host names or IP addresses, etc.).

Please redact sensitive information that would not be appropriate for email communication prior to sending the requested information.

If there is sensitive information that must be conveyed in order to provide a complete picture of the scenario you're facing, please let us know and we will set up a secure upload mechanism that can be used.
__________________
Thanks,
--Brenda

VanDyke Software
Technical Support
support@vandyke.com
(505) 332-5730
Reply With Quote
  #3  
Old 08-28-2018, 10:10 AM
bgagnon bgagnon is offline
VanDyke Technical Support
 
Join Date: Oct 2008
Posts: 4,116
Hi jodyrex,

A colleague mentioned it appears your console server requires the user:port syntax.

So in the Username field, you would put user:700x.

If using command-line:

SecureCRT /L user:700x x.x.x.x
__________________
Thanks,
--Brenda

VanDyke Software
Technical Support
support@vandyke.com
(505) 332-5730
Reply With Quote
  #4  
Old 08-28-2018, 10:29 AM
jodyrex jodyrex is offline
Registered User
 
Join Date: May 2018
Posts: 3
There does not appear to be any useful information in the trace.

[PRINTER] : Printer initialization succeeded
[LOCAL] : SSH2Core version 8.3.0.1699
[LOCAL] : Connecting to x.x.x.x:7001 ...
SecureCRT - Version 8.3.4 (x64 build 1699)
[LOCAL] : Changing state from STATE_NOT_CONNECTED to STATE_CLOSED
[LOCAL] : Connected for 18 seconds, 0 bytes sent, 0 bytes received

[LOCAL] : Stream has closed [CLOSE_TYPE_NONSPECIFIC] : Connection timed out

Connection timed out

Telnet works in Secure CRT for this connection but SSH fails.

[PRINTER] : Printer initialization succeeded
SecureCRT - Version 8.3.4 (x64 build 1699)
RCVD will 44
SENT dont 44
RCVD will ECHO
SENT do ECHO
RCVD will SUPPRESS GO AHEAD
SENT do SUPPRESS GO AHEAD
RCVD will BINARY
SENT do BINARY
RCVD do BINARY
SENT will BINARY

3850 line 0

***************************************************************************
* *
* Access to this system is restricted to authorized personnel only. Any *
* unauthorized use of the system is unlawful, and may be subject to *
* civil and/or criminal penalties. Any use of this system may be logged *
* and monitored without further notice, and the resulting logs may be *
* used as evidence in court. *
* *
***************************************************************************



User Access Verification

Username:

SSH works in other applications for this type of connection to the console server and Secure CRT works for all other SSH/Telnet connections so I do not believe an application filter is the issue. This appears to be a Secure CRT specific configuration issue.

Thanks
Reply With Quote
  #5  
Old 08-28-2018, 10:31 AM
jodyrex jodyrex is offline
Registered User
 
Join Date: May 2018
Posts: 3
That worked!! Thank you Brenda! :)

Quote:
Originally Posted by bgagnon View Post
Hi jodyrex,

A colleague mentioned it appears your console server requires the user:port syntax.

So in the Username field, you would put user:700x.

If using command-line:

SecureCRT /L user:700x x.x.x.x

Last edited by jdev; 08-28-2018 at 05:15 PM.
Reply With Quote
  #6  
Old 08-28-2018, 04:48 PM
bgagnon bgagnon is offline
VanDyke Technical Support
 
Join Date: Oct 2008
Posts: 4,116
Hi jodyrex,

Great! Thanks for posting an update!
__________________
Thanks,
--Brenda

VanDyke Software
Technical Support
support@vandyke.com
(505) 332-5730
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -6. The time now is 10:20 AM.