From owner-freebsd-stable@FreeBSD.ORG Wed May 25 03:16:51 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08A6516A41C for ; Wed, 25 May 2005 03:16:51 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1B1C43D48 for ; Wed, 25 May 2005 03:16:48 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (Xserve/8.12.11/smtpout11/MantshX 4.0) with ESMTP id j4P3GlmG020247; Tue, 24 May 2005 20:16:47 -0700 (PDT) Received: from [192.168.1.6] (pool-68-161-53-96.ny325.east.verizon.net [68.161.53.96]) (authenticated bits=0) by mac.com (Xserve/smtpin07/MantshX 4.0) with ESMTP id j4P3GjQS002918; Tue, 24 May 2005 20:16:46 -0700 (PDT) In-Reply-To: <000001c560d3$545e4f80$0401a8c0@laptop> References: <000001c560d3$545e4f80$0401a8c0@laptop> Mime-Version: 1.0 (Apple Message framework v730) X-Priority: 3 (Normal) Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable From: Charles Swiger Date: Tue, 24 May 2005 23:16:45 -0400 To: Matt Smith X-Mailer: Apple Mail (2.730) Cc: freebsd-stable@freebsd.org Subject: Re: SSHD timeout X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 May 2005 03:16:51 -0000 On May 24, 2005, at 10:42 PM, Matt Smith wrote: > I have a friend that has 5.4 where SSHD keeps timing out before > authentification. Box has a hardwired 3com NIC. We=92ve tried =20 > everything > but can't find the cause of the timeouts. What gives? Try "ping _machine_" and see whether that works. Run "ssh -vvv _machine_" and it will give more information. If you experience a two-minute delay your reverse DNS is probably =20 broken. --=20 -Chuck PS: God kills a kitten every time someone top-posts while quoting an =20 entire daily digest of 30+ archived messages. If you don't care =20 about saving the kittens, at least consider saving bandwidth...