topic Re: SSH Issue with ASA 5505 running 8.3(2) in Network Security

SSH Issue with ASA 5505 running 8.3(2)

aubreyrhame — Mon, 11 Mar 2019 21:07:18 GMT

Hello,

I'm replacing a new ASA 5505 due to a corrupted flash. On the original unit, I had the ability to SSH into the device using TeraTerm with no problems.

While configuring the new device, I entered the following commands to enable SSH into the unit:

crypto key generate rsa modulus 1024

write mem

ssh 192.168.0.0 255.255.255.0 inside

ssh timeout 30

However, now, using TeraTerm, anytime I attempt to SSH into the unit, I get the following message:

All the encryption algorithms that this program and the server both understand have been disabled. To communicate with this server, you will have to enable some more ciphers in the TTSSH Setup dialog box when you run Tera Term again. This connection will now close.

please help.

Aubrey

SSH Issue with ASA 5505 running 8.3(2)

mvsheik123 — Thu, 04 Aug 2011 20:47:20 GMT

Have you tried clearing the ssh key and recreating the same?

Thx

Re: SSH Issue with ASA 5505 running 8.3(2)

aubreyrhame — Thu, 04 Aug 2011 20:52:21 GMT

Yes, I have

Re: SSH Issue with ASA 5505 running 8.3(2)

lcaruso — Thu, 04 Aug 2011 21:16:00 GMT

re: ssh 192.168.0.0 255.255.255.0 inside

did you intend to use subnet zero?

if not, try 192.168.0.0 255.255.0.0

maybe that will make a difference

then make sure whatever you use on the ASA is exactly the same on the SSH client

Re: SSH Issue with ASA 5505 running 8.3(2)

aubreyrhame — Thu, 04 Aug 2011 21:54:22 GMT

Yes, this way anyone on the 192.168.0.1-192.168.0.254 subnet could ssh into the ASA device

Re: SSH Issue with ASA 5505 running 8.3(2)

lcaruso — Thu, 04 Aug 2011 22:31:10 GMT

it was worth a shot

if there is anyway you can view the ASA log to see what messages lurk there, I'd try that.

having a console connection while the ssh attempt is made to view the log and/or debug can be helpful