Is anyone else having problems getting a valid IP address/configuration from a DHCP server? My server is set up to serve 192.168.etc addresses - but on reboot I always get no connectivity because an address starting with 169.254 has been assigned to the PC running Windows 7. The Network and Sharing Center shows "Public Network" instead of the expected "Home Network". The problem gets fixed by using the troubleshooter and run as Administrator. The following reboot gets an address from 192.168 as expected. A subsequent reboot will wreck it all over again.

This is wierd one. I haven't experienced any issue getting an IPv4 address from my home network. Is it maybe the network card driver? is it a beta driver? Also is this a wireless network or a wired network? Daniel Nerenberg MCT MCSE MCITP MCTS MVP

Wow. That is interesting. However, you can save yourself a reboot when it goes south. Open up the command prompt as Administrator and type ipconfig /renew. You should then get an IP from your router.

This is the Intel(R) 82562V-2 10/100 Network Connection, 10/9/2008, driver version 9.13.4.4 provided by Microsoft and does not appear to be a Beta driver. It is a hard-wired network.Thanks for the suggestion of ipconfig /renew - I will try that next time.