From owner-freebsd-questions@FreeBSD.ORG Fri Aug 26 15:09:33 2005 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 74D4A16A41F for ; Fri, 26 Aug 2005 15:09:33 +0000 (GMT) (envelope-from apircalabu@bitdefender.com) Received: from mail.bitdefender.com (ns.bitdefender.com [217.156.83.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3C0343D45 for ; Fri, 26 Aug 2005 15:09:30 +0000 (GMT) (envelope-from apircalabu@bitdefender.com) Received: (qmail 12903 invoked by uid 1010); 26 Aug 2005 17:59:53 +0300 Received: from apircalabu.dsd.ro (10.10.15.22) by mail.bitdefender.com with AES256-SHA encrypted SMTP; 26 Aug 2005 17:59:53 +0300 Date: Fri, 26 Aug 2005 18:11:45 +0300 From: Adi Pircalabu To: sjmorgan@gmail.com Message-ID: <20050826181145.623276bf@apircalabu.dsd.ro> In-Reply-To: References: <430DC324.6030708@thegeekzone.com> Organization: BitDefender X-Mailer: Sylpheed-Claws 1.9.13 (GTK+ 2.6.9; i386-portbld-freebsd5.4) X-BitDefender-Scanner: Clean, Agent: BitDefender Qmail 1.6.2 on mail.bitdefender.com Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BitDefender-SpamStamp: 1.1.4 049000040111AAAAAAE X-BitDefender-Spam: No (0) Cc: freebsd-questions@freebsd.org Subject: Re: cannot ssh to machine on lan when it has no internet connection 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: Fri, 26 Aug 2005 15:09:33 -0000 On Thu, 25 Aug 2005 17:47:40 +0100 Simon Morgan wrote: > Thanks for the reply. That would probably fix it but ideally I'd like > to fix the root of the problem. Not being able to resolve the IP of a > client really shouldn't stop them from connecting using SSH and if > there's a bug in there somewhere I'd like to get it fixed so that it > doesn't bite anybody else. You could also search your /etc/hosts.allow for the following line: ALL : PARANOID : RFC931 20 : deny Comment it out and see if it fixes your problem. -- Adi Pircalabu (PGP Key ID 0x04329F5E)