From owner-freebsd-questions@FreeBSD.ORG Thu Feb 24 14:00:52 2005 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 3CB9B16A4CE for ; Thu, 24 Feb 2005 14:00:52 +0000 (GMT) Received: from mailgw3a.lmco.com (mailgw3a.lmco.com [192.35.35.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7BF643D54 for ; Thu, 24 Feb 2005 14:00:51 +0000 (GMT) (envelope-from Jed.Clear@lmco.com) Received: from emss04g01.ems.lmco.com (relay4.ems.lmco.com [166.17.13.122]) by mailgw3a.lmco.com (8.12.10/8.12.10) with ESMTP id j1OE0prx022437 for ; Thu, 24 Feb 2005 09:00:51 -0500 (EST) Received: from CONVERSION-DAEMON.lmco.com by lmco.com (PMDF V6.1-1X6 #30884) id <0ICF00J015LEWA@lmco.com> for freebsd-questions@freebsd.org; Thu, 24 Feb 2005 09:00:50 -0500 (EST) Received: from sde5.mds.lmco.com ([166.17.136.105]) by lmco.com (PMDF V6.1-1X6 #30884) freebsd-questions@freebsd.org; Thu, 24 Feb 2005 09:00:50 -0500 (EST) Received: from lmco.com (VFMWKLCV224.mds.lmco.com [166.17.124.109]) by sde5.mds.lmco.com (8.11.7p1+Sun/8.9.3) with ESMTP id j1OE0oF11009; Thu, 24 Feb 2005 09:00:50 -0500 (EST) Date: Thu, 24 Feb 2005 09:00:50 -0500 From: Jed Clear To: freebsd-questions@freebsd.org Message-id: <421DDE12.734D3A8C@lmco.com> MIME-version: 1.0 X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en Subject: cna't ssh localhost 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: Thu, 24 Feb 2005 14:00:52 -0000 Just off the top of my head, check that your DNS is working. My guess is that the sshd is trying to do a reverse DNS lookup, when you have the network configured. It takes a looooong time for a DNS lookup to time out. Try the ssh, wait at least 30 seconds (the DNS time out, IIRC). If it succeeds then, it's likely DNS related. -Jed