From owner-freebsd-questions@FreeBSD.ORG Tue Mar 22 04:50:31 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 4B9DB16A4CE for ; Tue, 22 Mar 2005 04:50:31 +0000 (GMT) Received: from smtp.nexband.com (valinux.intop.net [206.156.254.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEA9A43D49 for ; Tue, 22 Mar 2005 04:50:30 +0000 (GMT) (envelope-from freebsd@usmstudent.com) Received: from [192.168.0.100] (208-149-64-30.adsl.nexband.com [208.149.64.30]) by smtp.nexband.com (8.12.11/8.12.11) with ESMTP id j2M4oUtB030062 for ; Mon, 21 Mar 2005 22:50:31 -0600 Message-ID: <423FA414.2050409@usmstudent.com> Date: Mon, 21 Mar 2005 22:50:28 -0600 From: darren User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <423E116D.50805@usmstudent.com> <423EEE60.2050205@dial.pipex.com> In-Reply-To: <423EEE60.2050205@dial.pipex.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ssh password delay -- SOLVED X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd@usmstudent.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2005 04:50:31 -0000 Thanks to all. I seemed to have resolved the problem by setting my /etc/host.conf file to look like: order hosts,bind multi on And, of course, I have the correct IP's were in the /etc/hosts file. My laptop gets two different IPs depending on whether I go through the wireless or not. My host.conf already looked like the one below, but it wasn't working. Thanks again. I am so glad to get this problem resolved. darren Alex Zbyslaw wrote: > Gary Smithe wrote: > >> If that is your resolv.conf, then that explains some things. Your box >> is looking at the ISP for name resolution and the ISP has no idea (nor >> could care) what your internal LAN address space is. Change the >> resolv.conf to look at itself (127.0.0.1) and setup BIND with some >> simple DNS and RDNS records. You could use pretty much any box on >> your network for DNS, but the key is that it has to know about the >> internal space. >> >> > Or fix your /etc/host.conf to lookup in files first and then use DNS, > then put your local network in /etc/hosts. Much simpler for a small > network. > > E.g. /etc/host.conf > > # First try the /etc/hosts file > hosts > # Now try the nameserver next. > bind > > > And /etc/hosts > > 192.168.0.1 myhost > > Then leave resolv.conf alone. It will be used for anything not in your > local hosts file. > > --Alex > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > >