Windows 7 Enterprise in Server 2003 Domain Loses Network About 50% of Times it Reboots
I have rolled out Windows 7 Enterprise to a student lab. Everything is beautiful unless a client (Windows 7 Dell) has to reboot. Then there is better than a 50% chance that the client will not have networking at reboot. The only way to log on (other than local admin) is with cached credentials. "Welcome" is displayed for a long time and when machine finally opens to Desktop, there is no network connectivity. It can usually be restored with ipconfig /release (from its 192. address) and ipconfig /renew (back to the 10. network). I think a static IP address may fix the problem, but I have not tested it enough and do not have enough static addresses. Any suggestions greatly appreciated. Thank you! I originally thought it was a DNS problem as nslookup did not see my domain name (just server IP address), but I got that resolved yesterday by installing a Reverse Lookup Zone.
February 3rd, 2010 12:09am

Hi, Based on my research, I would like to suggest the following: 1. Update the NIC driver. 2. If the computer is connecting to a router, update the router’s firmware. 3. Check your DHCP server. 4. Check Event Log and see if there are any related errors. 5. Please also refer to: Event ID 5719 is logged when you start a computer on a domain, and the computer is running Windows Server 2003, Windows XP, or Windows 2000 In addition, may I know if other Windows 7 clients have the same hardware configuration (such as NIC) with this computer? Thanks.Nicholas Li - MSFT
Free Windows Admin Tool Kit Click here and download it now
February 8th, 2010 2:10pm

Thanks so much for the reply. I will investigate some things when I get to work, but here is one thing: In one lab there are 14 Windows 7 machines and 21 Windows XP machines. All are on the same switch, etc. A reboot of all 21 XP machines would return them all instantly to perfect network connectivity. A reboot of the 14 Windows 7 machines would leave about 1/2 of them without networking. You may be on to something with your router firmware update idea. Another thing: when they remained undisturbed (no power downs) for a couple of weeks, they seemed OK with a reboot. But them we had a sudden power loss and they were back to 50% reliability. I will check to see if they increase reliability (return to networking at reboot) with time. This suggest to me something in the router or DHCP, as you also suggested (perhaps a table is rebuilt over time).The thing is, it is hard for me to get much of a response from our network guy because it is evidently not his problem. That is why I am having to sort it out and have started reading Cisco stuff. Thank you again.
February 26th, 2010 2:29pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics