Date: Sun, 19 Sep 2004 10:24:14 -0700 From: Kevin Stevens <freebsd@pursued-with.net> To: Pota Kalima <hpota@mac.com> Cc: "<freebsd-questions@freebsd.org> <freebsd-questions@freebsd.org>" <freebsd-questions@FreeBSD.ORG> Subject: Re: Ssh connection Message-ID: <BA36931E-0A60-11D9-AABF-000A959CEE6A@pursued-with.net> In-Reply-To: <BD737DD7.2F92%hpota@mac.com> References: <BD737DD7.2F92%hpota@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 19, 2004, at 10:17, Pota Kalima wrote: > On 19/9/04 5:56 pm, "Kevin Stevens" <freebsd@pursued-with.net> 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[581]: 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. KeS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BA36931E-0A60-11D9-AABF-000A959CEE6A>