I have recently run Windows 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 in several cases, after the updates, I 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, and I see no fundamental difference in the state of the udpates before or after the update other than this problem when compared to computers not having the problem.Specifically, after the updates, I cannot access pages in IE8 (Page cannot be found), cannot resolve DNS names when pinging, 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, 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, and I have one more in front of me now for which my last resort will also be a repair installation. There has got to be a simpler answer for something that is obviously just something corrupt in TCP/IP, yet not resolvable by the above means.How can I test to determine the specific file or function that is failing, and how can I resolve this issue without a Windows repair installation?1 person needs an answerI do too