On 02/24/2011 03:01 PM, Matthew Marlowe wrote: > On Thursday, February 24, 2011 10:09:22 am dhk wrote: >>>> >>>> I still haven't gotten this to work. Am I the only one using this? The >>>> "ssh -i .ssh/id_dsa.pub host" didn't work. I get a message "Read from >>>> socket failed: Connection reset by peer" with or without the -i option. >>>> > > I encountered a similar, if not the same, problem this morning. > Upgraded SSH, rebooted server, and no longer able to login. Logs showed > errors I had not seen before. > > I managed to solve the problem when I noticed that ssh'ing to the fqdn of the > server failed, but ssh'ing to the server hostname worked. This implied there > might be an issue with the known_hosts file, so I blew away that on both the > client and server and all was well. > > I'm guessing the upgrade modified the default ssh host keys, the new code > somehow doesn't give the normal error about discrepencies in known_hosts, and > consequently although ones user keys are still fine, it fails. The issue > here > is really the new error isn't nearly as understandable as the old. > > Anyhow, try it and I hope it works. > > Matt
Thanks, but I've tried that. ssh'ing to the hostname and loopback address work. However, when I go out to the WAN it doesn't. So I can't ssh user@123.123.123.123 even though I have port 22 open on the switch for my ip.
