From owner-freebsd-questions Sun Jan 18 05:32:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA03638 for questions-outgoing; Sun, 18 Jan 1998 02:32:20 -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 CAA03422 for ; Sun, 18 Jan 1998 02:30:00 -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 WAA06303; Sat, 17 Jan 1998 22:12:53 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Sat, 17 Jan 1998 22:12:53 -0800 (PST) From: Doug White Reply-To: Doug White To: chas cc: freebsd-questions@FreeBSD.ORG Subject: Re: NIC woes : server visible on our network only. In-Reply-To: <3.0.32.19980117110938.009379b0@peace.com.my> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk On Sat, 17 Jan 1998, chas wrote: > We have been having woes > > - When our machine boots/restarts, the messages appear on the screen > and all seems to be going well in the boot process until > it gets to the NIC config. > ep0 : ...... ether > Once this appears on the screen, the process seems to halt. > I then have to press CTRL + C to get it to finish booting. > (the next line says something about clearing /tmp) It's sticking on a nameserver lookup. 1. Modify /etc/rc.conf to not use any hostnames on the ifconfig_xxx lines. 2. Make sure /etc/resolv.conf's `nameserver' items point to your nameservers for your network. 3. Make sure your network connections are plugged in and operating propelry. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major