From owner-freebsd-questions Mon Mar 30 15:31:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22661 for freebsd-questions-outgoing; Mon, 30 Mar 1998 15:31:18 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22563 for ; Mon, 30 Mar 1998 15:30:48 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id PAA25035; Mon, 30 Mar 1998 15:30:39 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Mon, 30 Mar 1998 15:30:39 -0800 (PST) From: Doug White Reply-To: Doug White To: Khetan Gajjar cc: questions@FreeBSD.ORG Subject: Re: DHCP server giving out "wrong" addresses In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 30 Mar 1998, Khetan Gajjar wrote: > On Sun, 29 Mar 1998, Doug White wrote: > > >See http://home.san.rr.com/freebsd/dhcp.html; someone solved this problem > >for you. > > My question was concerned with Win95 client's being served by > isc-dhcp2 on a FreeBSD box. The above document (while interesting > reading) concentrates on booting a FreeBSD box via DHCP. Different > problems. My bad, sorry. I'm familiar with your problem, however, but it shouldn't be one. I would expect TCP programs to run a nameserver lookup against their own IP to get the correct name. (you're looking at winipcfg's idea of what the name is. We have tons of computers who think they are DEFAULT.uoregon.edu but they work fine.) Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message