That will only apply if you are running sshd through inetd and tcpd (not recommended) or you have compiled in tcp wrappers support into sshd. I suspect that sshd is no longer running - or the "~/.ssh/known_hosts" file on the client machine has a different server key (RSA?) listed than the server is currently using. Try removing the key from the client and see if you get the following: The authenticity of host 'cascade.veldy.net' can't be established. RSA key fingerprint is fe:43:1c:81:89:0a:b8:da:c4:2c:4c:19:8b:79:c5:ff. Are you sure you want to continue connecting (yes/no)? or the equivalent. Tom Veldhouse veldy at veldy.net ----- Original Message ----- From: Chuck Milam <chuck at milams.net> To: <tclug-list at mn-linux.org> Sent: Thursday, July 27, 2000 11:16 AM Subject: Re: [TCLUG:19871] Debian Potato SSH > > On Thu, 27 Jul 2000, Jason J wrote: > > > > I have had Debian Potato running an sshd for several months with no > > problems. All of a sudden sshd is refusing connections. > > /var/log/auth.log > > Jul 27 11:00:48 guru ssdh[1003]: refused connect from #.#.#.# > > Check your tcp_wrappers (/etc/hosts.allow, /etc/hosts.deny). > > -- > Chuck Milam > chuck at milams.net > > > --------------------------------------------------------------------- > 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