lost ssh access to pix 506e

Jun 23, 2005 6 Replies

Rate this thread:

John Schleigh 21 years ago

I had a working ssh connection to my pix 506e until I changed the internal ip address. Of course the session would drop because I changed from

192.168.1.3 to 192.168.1.1. I have done this before and reconnected to the new internal address with no problem.

This time, though, it did not work; ssh_exchange_identification: Connection closed by remote host

I rebooted the pix to restore the previous configuration and it does respond to pings at 192.168.1.3, but the ssh still does not work.

ssh -v -l pix 192.168.1.3

OpenSSH_3.9p1, OpenSSL 0.9.7d 17 Mar 2004 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to 192.168.1.3 [192.168.1.3] port 22. debug1: Connection established. debug1: identity file /home/john/.ssh/identity type -1 debug1: identity file /home/john/.ssh/id_rsa type -1 debug1: identity file /home/john/.ssh/id_dsa type -1 ssh_exchange_identification: Connection closed by remote host

Any ideas?

The only other changes made recently were to the hostname and domain-name of the pix. It still worked afterwards, though.

Vote

Jyri Korhonen 21 years ago

Try regenerating the RSA key:

ca zeroize rsa ca generate rsa key 1024 ca save all

More information:

formatting link

Vote

Gerd EMail 21 years ago

Hi John,

another solution can be:

You have an existing ssh key for the host192.168.1.3 in your known_hosts table.

Erase the entry for the new ip address in /home/john/.ssh/known_hosts, then reconnect to the pix.

Greetings Gerd

Vote

John Schleigh 21 years ago

Already tried that. No luck, but thanks.

Vote

Gerd EMail 21 years ago

Please write down the your ssh_config (client)

Greetings Gerd.

Vote

John Schleigh 21 years ago

/etc/ssh/ssh_config Host * ForwardX11Trusted yes

Vote

Walter Roberson 21 years ago

:> another solution can be:

:> Erase the entry for the new ip address in /home/john/.ssh/known_hosts, :> then reconnect to the pix.

:Already tried that. No luck, but thanks.

You need to follow Jyri's suggestion to regenerate the ssh key. The ssh key is dependant on the hostname and domain name, so when you changed those, you invalidated the stored keys.

Vote

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required