From owner-freebsd-questions@FreeBSD.ORG Sun Sep 19 17:22:09 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30A5016A4CE for ; Sun, 19 Sep 2004 17:22:09 +0000 (GMT) Received: from pursued-with.net (adsl-66-125-9-244.dsl.sndg02.pacbell.net [66.125.9.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id B299A43D31 for ; Sun, 19 Sep 2004 17:22:08 +0000 (GMT) (envelope-from freebsd@pursued-with.net) Received: from [10.0.1.101] (unknown [10.0.1.101]) by pursued-with.net (Postfix) with ESMTP id 90ABB287E3E; Sun, 19 Sep 2004 10:22:08 -0700 (PDT) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Kevin Stevens Date: Sun, 19 Sep 2004 10:24:14 -0700 To: Pota Kalima X-Mailer: Apple Mail (2.619) cc: " " Subject: Re: Ssh connection X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2004 17:22:09 -0000 On Sep 19, 2004, at 10:17, Pota Kalima wrote: > On 19/9/04 5:56 pm, "Kevin Stevens" 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