From owner-freebsd-questions@FreeBSD.ORG Wed Mar 1 21:18:56 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 B182516A420 for ; Wed, 1 Mar 2006 21:18:56 +0000 (GMT) (envelope-from kurt.buff@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 432DE43D45 for ; Wed, 1 Mar 2006 21:18:56 +0000 (GMT) (envelope-from kurt.buff@gmail.com) Received: by xproxy.gmail.com with SMTP id h26so161251wxd for ; Wed, 01 Mar 2006 13:18:55 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Xr5bvNIVc9v9UyQFoIHIlRviIg37xYbnvNqH7UxA7S02uXC73PSz8yYNrdqCAtYS9syr7n/Z+I2J1WSRXO18AG53VOXSoKzTZUWrPG++PmK1UHAr/TjewlZv4w90sxatwy4eCBw+C247u7l+IwUPFeU/+BHoCrpCwI74yibgRg0= Received: by 10.70.17.3 with SMTP id 3mr2282587wxq; Wed, 01 Mar 2006 13:18:55 -0800 (PST) Received: by 10.70.18.13 with HTTP; Wed, 1 Mar 2006 13:18:55 -0800 (PST) Message-ID: Date: Wed, 1 Mar 2006 13:18:55 -0800 From: "Kurt Buff" To: luke , freebsd-questions@freebsd.org In-Reply-To: <5fee5e300602281339o4c7fdc41pf1c00555d703fe57@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <440434E5.5050701@dial.pipex.com> <5fee5e300602281339o4c7fdc41pf1c00555d703fe57@mail.gmail.com> Cc: Subject: Re: SSHD working in a funky fashion X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Mar 2006 21:18:56 -0000 On 2/28/06, luke wrote: > my initial guess is that your firewall is blocking ssh traffic, tcp port = 22, > on the interface you're trying to log in on. double check your firewall > rules and make sure it's explicitly allowed No firewalls involved, sorry to say. See my response to