Stephen Nosal, 2002-Mar-10 15:51 -0500: > Well, folks, I'm still having no success here. Here's an excerpt from my > syslog files: > > Mar 10 15:24:38 lambic dhclient-2.2.x: send_packet: Network is down > Mar 10 15:24:53 lambic dhclient-2.2.x: DHCPDISCOVER on eth0 to > 255.255.255.255 port 67 interval 14 > Mar 10 15:24:53 lambic dhclient-2.2.x: send_packet: Network is down > Mar 10 15:25:07 lambic dhclient-2.2.x: DHCPDISCOVER on eth0 to > 255.255.255.255 port 67 interval 11 > Mar 10 15:25:07 lambic dhclient-2.2.x: send_packet: Network is down > Mar 10 15:25:18 lambic dhclient-2.2.x: DHCPDISCOVER on eth0 to > 255.255.255.255 port 67 interval 2 > Mar 10 15:25:18 lambic dhclient-2.2.x: send_packet: Network is down > Mar 10 15:25:20 lambic dhclient-2.2.x: No DHCPOFFERS received. > Mar 10 15:25:20 lambic dhclient-2.2.x: No working leases in persistent > database. > Mar 10 15:25:20 lambic dhclient-2.2.x: execve (/etc/dhclient-script, ...): No > such file or directory > Mar 10 15:25:20 lambic dhclient-2.2.x: exiting. > Mar 10 15:25:20 lambic dhclient-2.2.x: Sleeping. > > As far as I know, roadrunner in NYC requires no host name - the modem > validates the mac address of the ethernet card. It works fine when I boot to > NT..., so I'm pretty confident the network is good, but I'm really at a loss > right now... > > Thoughts?
Can you confirm that the DHCPDISCOVER packets really are going out? My thought is that the NIC driver isn't working properly. jc -- Jeff Coppock Systems Engineer Diggin' Debian Admin and User
