First of all, I apologize for posting a Windows XP question in the Windows 7 forum, but the XP support forum responses, one by a MS Support person, both directed me here for my answer, and the only current XP forum in TechNet is specific to the installation of SP3. Over that last two months, I have run Windows (XP) Updates manually on many of my clients' Windows XP Pro systems that had gotten somewhat behind on updates (~100 - 200 MB per PC, critical & optional updates combined), and some of them have lost some DNS client functionality. Out of perhaps 75 computers updated, five have had this problem, but it is quite severe when it occurs. Specifically, after the updates, these things fail: IE8 (404, page cannot be found), cannot resolve DNS names when pinging, domain login script does not run, and cannot access resources on network shares. However, in every case, nslookup does work to resolve names, I can ping LAN and Internet IP addresses, DHCP client works fine, and I can open websites and network shares using their IP addresses instead of URLs. In NO case has any of the following resolved the problem: netsh int ip reset, netsh winsock reset, netsh winsock reset catalog, ipconfig /flushdns, ipconfig /registerdns, and manual removal of the winsock registry entries & subsequent reinstallation of TCP/IP. In one case, one of the MS Fixits (50202 or 50203, I believe), resolved the issue, in another, the winsockxpfix EXE worked. In two cases, both of these also failed, and I was reduced to running a Windows XP repair installation. I have one more in front of me now for which my last resort will also be a repair installation, but I suspect there is a solution targeted on the specific TCP/IP issues. How can I test to determine the specific file or function that is failing so that I can (hopefully)resolve this issue without a Windows repair installation?

Hi, Thank you for posting here. I suggest you try the safe mode with network to see the DNS whether can work properly, if work, it maybe the application issue, you need check your firewall or other related applications, If not work, you need to check whether the client can connect the DNS server, tell me that how many DNS servers do you build? I suggest you try to install the SP3. if you try all the steps above but the issue persists, it must be one Network issue, you need check all your network devices.

Hi, Thank you for posting here. I suggest you try the safe mode with network to see the DNS whether can work properly, if work, it maybe the application issue, you need check your firewall or other related applications, If not work, you need to check whether the client can connect the DNS server, tell me that how many DNS servers do you build? I suggest you try to install the SP3. if you try all the steps above but the issue persists, it must be one Network issue, you need check all your network devices.

I just upgraded to Windows XP SP3 - that is when the problem began. I am sure it is not a networking device, because the other six computers at this location work correctly, and this problem occurred immediately after a set of Windows updates. Windows firewall is disabled, as it should be in a corporate network with a hardware firewall. I finally gave up and just did a Windows repair installation on the last one with the problem, then reapplied SP3 & all Windows updates. It is working now, but I will try it in safe mode with networking if I encounter another one, though - good suggestion.

To answer your DNS question: there is a single DNS server, and it is my Windows 2003 SBS domain controller. I repeat, though: nslookup is able to identify the DNS hosts perfectly fine, so DNS is evidently fully accessible. Ping, on the other hand, is unable to find the host, but I do not know enough about nslookup and ping to determine what app layers are between each of them and the IP stack.

I can confirm the same issue on multiple machines, so much so that I wont run windows updates on live client machines. It only started in the last 2 months or so. I've noticed it mainly in complete reloads, I'll reload a machine, install IE8 manually from a download and then run all available windows updates (except drivers, which I usually do manually from the manufacturer). Then after a reboot therse about a 1 in 5 chance the machine wont be able to resolve dns afterwards. nslookup works fine I can access my server by using //192.168.2.20 I can even access websites by using their IP addresses. I have tried uninstalling EVERYTHING from add/remove programs one at a time to see what triggers it but that doesnt do any good. winsockxpfix hasn't helped the problem I've tried replacing the network card, updating network drivers, even firefox will not resolve a website.... I had to of worked before the updates... or else I couldn't have gotten to windows update in the first place. once a machine has "the bug" it appears that the only solution is to do a reload and hope it doesnt happen the second time. I had one machine I reloaded 3 times before I was able to get the updates to take without screwing up DNS.

Good day all, As well I have been hunting for a cause or resolution for months as well. We repair alot of systems and don't have time to troubleshoot software issues so most get reloaded on the spot. Systems have SP3 and IE8 installed before doing updates. Everything is online and running great until the updates are run. It seems to be so spreatic. Run windows update and it works, run on another system it doesn't. As well it is not manu specifi. Can be an Intel or realtek or other. Only solution I have is to run system restore then re-download/install updates again ( and in some cases the DNS dies again ). I thought maybe it was the Malicous Software removal tool ( as I had Issues installing IE8 with windows updates ) but even not installing that update the issue still comes and goes. The funny thing about this issue is it is not the DNS servers or the ability to reach the DNS server. PIng, tracert etc any IP or want and it works. Do google by IP and the webpage works. ONLY BY DOMAIN www.something.com will not resolve. I can even ping the DNS server IP's listed in IP CONFIG. Set static info and still no. NO info int he event log, no services seem to bve stopped or failed to start. Every Network Fix ( Winsock, LSP, IP STACK rebuild, Reload NIC, Install new PCI NIC, flushdns, etc. will not work. I tried last night just to see by instralling this KB http://support.microsoft.com/kb/953761 but still no. If anyone has any other suggestions ( even the old Voodoo Candle in the dark to get a compaq modem to connect ) I more then happy and test it out and see how it does. Thank You All.

Well not sure if anyone is reading this, however, I will post up my findings so far. I found a site talking about KB 951746 and dns updating but, when you look at the list of OS's SP3 says not applicable. Further digging found that there is another update. KB951748. Seems 746 is server side update and 748 is clientside workstation. Still showning SP3 in the list as N/A. So off to add remove programs and sure enough, KB951748 is in the list. Uninstall and reboot and internet is back up and running. Manually Downloaded/installed KB951748 http://www.microsoft.com/downloads/en/details.aspx?familyid=ed989a33-7a9e-4423-93a8-b38907467cdf&displaylang=en And DNS is function again. Just thought I would put that up there as I have been working on and off trying to resolve this for sometime and hopefully I can save 5 minutes of someone elses life :-) Will test it out on a few more systems and let you know.