SSH Issue from PC to Server through Cisco 4500

Unanswered Question
Mar 17th, 2009

the user and the pc are on different vlans but they are both connected to the same 4500 switch.

The user said he was able to reach the server at one time.

I can ping the server from the pc.

I cannot ssh from the pc to the server through the 4500.

I can ssh from the 4500 to the server.

There are no ACLs on the 4500.

Any ideas??

Thank you

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Leo Laohoo Tue, 03/17/2009 - 18:38

Can you ssh from your PC to the 4500?

If not, please check for the following commands are present:

line vty 0 15

transport input ssh


transport input all

glen.grant Wed, 03/18/2009 - 04:28

If no acls then the switch should have no bearing . Different SSH versions on the devices ???

ekuvinka Wed, 03/18/2009 - 08:35

the switch is using version 1.99 and i can ssh to the server from there.

only when im on my pc i cant ssh. im on a different vlan than the server, but both my pc and the server are directly connected to the switch and i can ping the server from my pc.

ekuvinka Thu, 03/19/2009 - 04:02

Just to add to the madness, when I do a traceroute from another switch not directly connected to the server, I get a bunch of question marks. I can however ping the server address.

bvellalath31 Fri, 03/20/2009 - 03:41


1. Please let me know whether you are trying to do the ssh to ip address of server or name of the server. If name please try to do with ip address of server.

2. What is the output of this command

telnet 22 if it is blank screen we should check in the sever policies.

ekuvinka Fri, 03/20/2009 - 04:12

I'm using the ip when trying to ssh. I'll check the results of the telnet test when I get to work. What would that test result tell me exactly?

bvellalath31 Fri, 03/20/2009 - 05:26

The command telnet 22

is trying to telnet port 22 (ssh).

If you are getting blank screen after u enter this command means there is no problem on your switch and we can start checking the policies on server side.

ekuvinka Fri, 03/20/2009 - 06:31

this is what happens when i try that in a cmd prompt:

telnet XX.XXX.XXX.40 22

Connecting To XX.XXX.X.40...Could not open connection to the host, on port 22:

Connect failed


This Discussion