<div class="gmail_quote">On Thu, Aug 27, 2009 at 5:00 PM, Fred Roller <<a href="mailto:froller@tnclimited.com" target="_blank">froller@tnclimited.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> [snip] <div>On Thu, 2009-08-27 at 16:33 -0400, Verde Denim wrote: > 192.168.1.101 > 255.255.255.0 > 192.168.1.1 </div>[snip] Just taking a wag at this one, but, most off the shelf commercial routers start their dhcp services issuing IP's at 100 (192.168.1.100). If your router issues dhcp addy's could you have a conflict with the *.101 addy? Perhaps you could set the card to DHCP just to see if it comes up and communicates on the network, assuming this server is not the DHCP server. Also, have you pinged yourself? Just to make sure the nic *is* working. I know this is all basic but just troubleshooting. If you have already tried these or other things in addition to your OP let us know. Fred </blockquote><div> Fred I appreciate your help. The system was working fine up until the updates which required a reboot. At this point, I can ping myself at 192.168.1.101 I have 5 systems on an 8-port router, all with IPs from 101 through 108. All the other systems are working fine. The router currently has all dhcp settings turned off. If I turn it on for this machine, I'll need to manually reset the other 7 as well, since I'd need to reconfigure the router to use DHCP first. I'm googling about and finding lots of hits on ADDRCONF (NETDEV_UP): eth0: link is not ready, so maybe there's something here... A few of them seem to indicate a bug ith udev among other things. But at this point I know that the box worked, the cable worked, the interface worked - all before today's updates... I did check to make sure, and there is only one eth interface. Update... This is strange... I rebooted the box, went into bios and disabled the onboard LAN. booted up and found no eth0 (as expected) I rebooted again - this time re enabling the onboard LAN. booted up, and eth0 is back! A Windoze kludge to be sure - but it did get the interface back online. Not sure why... it always gives me a creepy feeling when a windoze fix solves a linux problem. Thanks for the help. I guess the maintainers still have a bit of noodling to do on this one. Regards Jack </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> -- <div><div></div><div>ubuntu-users mailing list <a href="mailto:ubuntu-users@lists.ubuntu.com" target="_blank">ubuntu-users@lists.ubuntu.com</a> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-users" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-users</a> </div></div></blockquote></div>