removed all entries from known_hosts on both client and server same stupid ssh_exchange_identification: Connection closed by remote host error "Thomas T. Veldhouse" wrote: > Looks like a new host key and the client doesn't like it because it changed > and doesn't trust the server anymore. Try removing the server's entry from > ~/.ssh/known_hosts on the client machine. > > Tom Veldhouse > veldy at veldy.net > > ----- Original Message ----- > From: Jason J <jasonj at innominatus.com> > To: <tclug-list at mn-linux.org> > Sent: Thursday, July 27, 2000 11:59 AM > Subject: Re: [TCLUG:19871] Debian Potato SSH > > > ssh localhost fails same as from remote > > > > this is OpenSSH-1.2.3 > > > > when i start it with -d > > > > root at guru /etc/init.d>/user/sbin/sshd -d& > > sshd version OpenSSH-1.2.3 > > debug: Bind to port 22 on 0.0.0.0 > > Server listening on 0.0.0.0 port 22. > > Generating 768 bit RSA kde. > > RSA key generation complete. > > debug: Server will not fork when running in debugging mode. > > > > > > Same error recevied on the client side > > > > sshd -v give an invalid option. > > > > > > > > > > Jim Crumley wrote: > > > > > On Thu, Jul 27, 2000 at 11:31:02AM -0500, Jason J wrote: > > > > When I telnet it works fine. Although i am running telnet-ssl so I > might not > > > > be getting the troubleshooting info your looking for. > > > > I will walk through a session quick > > > > > > > > Client: > > > > root at gohan /root> ssh jasonj at innominatus.com > > > > ssh_exchange_identification: Connection closed by remote host > > > > > > > > Server: > > > > /var/log/auth.log > > > > Jul 27 11:00:48 guru sshd[1003]: refused connect from #.#.#.# > > > > > > > > I have rebooted (although I shouldnt have to, I tried) and restarted > sshd > > > > numerous times. Same result. > > > > > > > > Troy: I have not installed anything recently. I tried to apt-get > upgrade > > > > several times a week, however I have not done this at the time the > problem > > > > started. I did attempt this after the problem started hoping for an > update to > > > > sshd. > > > > > > Can you ssh to the from that box to itself OK? (ssh localhost) > > > > > > Have you tried turning up the verbosity on bothh ssh and sshd - > > > it might give a better hint to what's going on. (sshd -d and > > > ssh -v). > > > > > > -- > > > Jim Crumley | > > > crumley at belka.space.umn.edu | > > > Work: 612 624-6804 or -0378 | > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: tclug-list-unsubscribe at mn-linux.org > > > For additional commands, e-mail: tclug-list-help at mn-linux.org > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: tclug-list-unsubscribe at mn-linux.org > > For additional commands, e-mail: tclug-list-help at mn-linux.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tclug-list-unsubscribe at mn-linux.org > For additional commands, e-mail: tclug-list-help at mn-linux.org --------------------------------------------------------------------- To unsubscribe, e-mail: tclug-list-unsubscribe at mn-linux.org For additional commands, e-mail: tclug-list-help at mn-linux.org