 |
 |
I found this paragraph from the article rather oddly worded: One of the components of the Internet connection on your computer is a > built-in set of instructions called TCP/IP. TCP/IP can sometimes become > damaged or corrupted. If you cannot connect to the Internet and you have > tried all other methods to resolve the problem, TCP/IP might be causing it. Steve, did that work? I also wondered if you or the user simply tried System Restore to go back to a known working time. /rich (PS, Steve, are you a fan of NCIS? You sounded like Agent Gibbs demanding that a solution be found in an arbitrarily short period of time. :-) ) On Thu, Jun 17, 2010 at 12:20 PM, Al Puzzuoli <[log in to unmask]> wrote: > Have you tried resetting the Stack? I think this applies to XP as well > as later versions of windows. See the following article: > http://support.microsoft.com/kb/299357 > > --Al > > -----Original Message----- > From: STeve Andre' [mailto:[log in to unmask]] > Sent: Thursday, June 17, 2010 11:45 AM > To: [log in to unmask] > Subject: [MSUNAG] Sigh... A new Windows XP problem > > So I have a user who said his networking was blitzed on his T500 > Thinkpad running XP. After having him rip out the network drivers and > having Windows reinstall things, the IP stack is working, except for > DNS. DNS does not work. The DHCP data is correct, and in fact I've > used a static address for DNS, but it doesn't work. This problem ocurrs > for both the wireless card and ethernet card, so its not in the drivers > but in the stack or just above it and I can't figure out a way to fix > this. Googling for it reveals many people who can't seem to enter IP > addressed correctly, but not my problem. This is the first time I have > ever seen part of the stack blitzed like this. > A ipconfig /all says that there was a registry probllem reading tcpip, > so I'm pretty sure there is deep trouble here. > > I'm making a backup now of the machine so I can rebuild it. > If anyone can come up with interesting ideas when thats done, I wouldn't > have to rebuild. > > You have two hours. ;-) > > T H A N K S for any ideas. > > --STeve Andre' >