From owner-freebsd-questions@FreeBSD.ORG Sun Sep 19 21:30:08 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 07B3116A4CE for ; Sun, 19 Sep 2004 21:30:08 +0000 (GMT) Received: from auk1.snu.ac.kr (auk1.snu.ac.kr [147.46.100.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 789C243D53 for ; Sun, 19 Sep 2004 21:30:07 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: from [147.46.44.181] (spamrefuse@yahoo.com) by auk1.snu.ac.kr (Terrace Internet Messaging Server) with ESMTP id 2004092006:21:09:379220.2862.2812951472 for ; Mon, 20 Sep 2004 06:21:09 +0900 (KST) Message-ID: <414DFA58.7080502@yahoo.com> Date: Mon, 20 Sep 2004 06:30:00 +0900 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040901 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-TERRACE-SPAMMARK: NO (SR:0.92) (by Terrace) 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 21:30:08 -0000 Pota Kalima wrote: > 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) > What is there in /var/log/messages about refused sshd connections? How are you allowing sshd connection in /etc/hosts.allow ? If you have made /etc/hosts.allow restrictive, then be sure there's a line like: sshd : ALL : allow or replace 'ALL' by those you want to access your machine by sshd. Rob.