ASA 5505/SSH Times out

Unanswered Question
Jul 21st, 2009

I have an ASA 5505 that is causing me some issues. I set up ssh on the ASA and had it working. I then shipped it to the customer and the ssh no longer works. I have SSH wide open right now. I have also zeriozed the key and regenerated the key and nothing seems to work. Any suggestions? Also, I just decided to try to telnet and that does not work either. Thanks for your help in advance.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
rob.stoop Tue, 07/21/2009 - 10:32

Do you get a hit on your outside ACL? Do you even get a response or nothing?

Don't forget to use "outside"

ssh xx.xx.xx.xx outside

shoemakerjoel Tue, 07/21/2009 - 10:38

I have basically this.

ssh outside

I don't even see it hit the outside interface which is weird because I can get ASDM to work.

shoemakerjoel Tue, 07/21/2009 - 10:39

I have basically this.

ssh outside

I don't even see it hit the outside interface which is weird because I can get ASDM to work.

rob.stoop Tue, 07/21/2009 - 10:42

don't forget to check the logging with asdm when you connect to your device.

dschuckman1 Tue, 07/21/2009 - 10:36

The next thing I would look at is are you accessing the ASA from inside or outside and have you added the corresponding SSH permit statements?

So if you are trying to connect to the outside interface and you are comming from X.X.X.X you would need the statement:

ssh X.X.X.X outside

Make the subnet mask equivalent to whatever IP range you will be coming from... If you will always come from a single address use the if you know you will come from a /29 network use the and so on.

Have a good Day!


Kevin Redmon Wed, 08/05/2009 - 18:28

This sounds like an upstream issue if you do not see any evidence that it reaches the ASA. Some ISPs and/or network administrators will block network management protocols such as Telnet and SSH due to the damage that they can cause by malicious users. It is difficult and impractical to block the HTTPS used for ASDM.

You can configure packet captures on the outside interface of the ASA in question specifically for the host IP trying to SSH. For instance, consider the following capture syntax:

access-list TAC extended permit tcp host host eq 22

access-list TAC extended permit tcp host eq 22 host

cap capout int outside packet-l 1522 buffer 512000 access-list TAC

After attempting to connect once or twice to the outside IP address, you should see packets in this packet capture - 'show capture capout'. If no packets are seen, the traffic is likely being blocked upstream.

Hope this helps.

shoemakerjoel Thu, 08/06/2009 - 04:03

Sorry I didn't post that this has been solved. The ISP was blockin ICMP and SSH and I had them make the proper changes and all is well now. Thanks!!!


This Discussion