Kevin Stevens <[EMAIL PROTECTED]> writes:
> On Sep 19, 2004, at 10:17, Pota Kalima wrote:
> > On 19/9/04 5:56 pm, "Kevin Stevens" <[EMAIL PROTECTED]> wrote:
> >> What happens if you try to ssh to the machine from itself?
> >> KeS
> > Tried to ssh to machine itself and got the following:
> > $ Ssh 192.168.0.5
> > The authenticity of host '192.168.0.5 (192.168.0.5)' can't be
> > established.
> > DSA key fingerprint is 42:98:e3:11:
> > Are you sure you want to continue connecting (yes/no)? Yes
> > Warning: Permanently added '192.168.0.5' (DSA) to the list of known
> > hosts.
> > [There was a prolonged pause here, I almost rebooted the machine]
> > Sep 19 18:10:00 localhost sshd: fatal: Timeout before
> > authentification
> > for 192.168.0.5
> > Connection closed by 192.168.0.5
> Well, there you go. Better get it working locally before worrying
> about connecting from other machines - at least it's easier to
> troubleshoot that way. You can start adding -v's to your session
> command to get more details.
I suspect that making sshd log more verbosely will be important, not
just seeing the error messages from ssh.
[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"