DNS problem after Windows Update on SP2 machines
Hey guys,
We just had some updates approved and installed through our WSUS server in a Windows domain environment. The problem is, after the install ALL of our XP SP2 machines had no internet access. Upon further review it seems the dns server is being reset to 192.168.1.1 instead of our usualy dns servers that are assigned through dhcp. This problem affects only our SP2 machines, SP3 machines have no symptoms. If you do a release and renew or /registerdns you get the correct servers and internet connectivity back, but after about 30 minutes the DNS server is reverted back to 192.168.1.1 causing connectivity problems. Upgrading these machines to SP3 seems to fix the problem although some of them then need a IE 7/8 reinstall, the clinet launches IE and there are no menus or text displayed in the taskbar entry for IE.
I know the workaround, but it's a long process. I was hoping someone here could give me some insight as to which update causes this and why. All the installed updates say they apply to SP2 and 3. I have included a screenshot showing the recently installed updates (1/7/2010). Any help would be greatly appreciated. Thanks in advance!
updates.PNG
We just had some updates approved and installed through our WSUS server in a Windows domain environment. The problem is, after the install ALL of our XP SP2 machines had no internet access. Upon further review it seems the dns server is being reset to 192.168.1.1 instead of our usualy dns servers that are assigned through dhcp. This problem affects only our SP2 machines, SP3 machines have no symptoms. If you do a release and renew or /registerdns you get the correct servers and internet connectivity back, but after about 30 minutes the DNS server is reverted back to 192.168.1.1 causing connectivity problems. Upgrading these machines to SP3 seems to fix the problem although some of them then need a IE 7/8 reinstall, the clinet launches IE and there are no menus or text displayed in the taskbar entry for IE.
I know the workaround, but it's a long process. I was hoping someone here could give me some insight as to which update causes this and why. All the installed updates say they apply to SP2 and 3. I have included a screenshot showing the recently installed updates (1/7/2010). Any help would be greatly appreciated. Thanks in advance!
updates.PNG
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Jason Watkins
I would make sure all XP machine are at SP3, and have the latest updates. Come 7/13/10, XP SP2 will no longer be supported.
I know the questions finished, but in case anyone else finds this whilst searching for similar issues, and also has ZoneAlarm installed on their clients, this may be of help: http://support.microsoft.com/kb/951748