From owner-freebsd-questions@FreeBSD.ORG Sun Sep 19 17:44:37 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 805DC16A4CE for ; Sun, 19 Sep 2004 17:44:37 +0000 (GMT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D49343D2F for ; Sun, 19 Sep 2004 17:44:37 +0000 (GMT) (envelope-from hpota@mac.com) Received: from mac.com (smtpin01-en2 [10.13.10.146]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id i8JHiaao017299; Sun, 19 Sep 2004 10:44:36 -0700 (PDT) Received: from [192.168.0.2] (host217-42-111-1.range217-42.btcentralplus.com [217.42.111.1]) (authenticated bits=0)i8JHiYrx006558; Sun, 19 Sep 2004 10:44:35 -0700 (PDT) User-Agent: Microsoft-Entourage/11.0.0.040405 Date: Sun, 19 Sep 2004 18:47:10 +0100 From: Pota Kalima To: Kevin Stevens Message-ID: In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit 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:44:37 -0000 On 19/9/04 6:24 pm, "Kevin Stevens" wrote: > > 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 > Well, here goes, $ ssh -v 192.168.0.5 [Rapid scroll of screen load of stuff, and then ...from about half-way down the screen] ... debug1: Host '192.168.0.5' is known and matches the DSA host key. debug1: Found key in /home/pota/.ssh/known_hosts:3 debug1: ssh_dss_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received Sep 19 18:29:09 localhost sshd[627]: fatal: Timeout before authentification for 192.168.0.5 Connection closed by 192.168.0.5 debug1: Calling cleanup 0x804c7a4(0x0) $ (Can't tell WTF this means) Pota