Quoting Jonathan Brooks
Hi,
The link light was/is on - and I forgot to mention that it works fine under windows. Having said all that - I just tried to boot the machine today and it worked :)
It still fails to get an IP address during the boot process, but magically by the time the login screen is put up it has configured itself. I wonder if there is some process that `/etc/init.d/network start` is waiting for, that gets started later in the boot process - which the (backgrounded) dhcpcd then finds and works? It seems a bit unlikely that it should take longer than the 5 second default timeout to get an IP address from DHCP - and it *always* fails - irrespective of the load on the network.
Any ideas?
Is it getting the same IP address everytime? Switching back and forth between Windows and Linux will mess w/ DHCP. Only one will have the lease info and the other will try and grab it, fail, then get a new address. In environments like this, static IPs work better. On Linux, look for the scpm profile manager. This will allow you to have different profiles for different environments, i.e., one for wireless, one for DHCP, one for static IP, etc. I have the following four profiles: Home: static IP on 10/100/1000Base-T Ethernet interface. Central time. Central: wireless w/ DHCP and/or dialup on Central time. Pacific: wireless w/ DHCP and/or dialup on Pacific time. DHCP: DHCP on 10/100/1000Base-T Ethernet. Central time. So far, these four cover it. Also, when it boots, F4 (IIRC) will allow you to change the active profile. HTH, Jeffrey -- Vote early and often. Apathy only encourages the bums.