Hi Sharyn. If they are XP with SP2 then try the following at a command prompt:
netsh winsock reset catalog
Cheers
Mark
_____
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sharyn Schmidt
Sent: August 28, 2007 11:09 AM
To: [email protected]
Subject: RE: [IMail Forum] WAY OT: corrupt tcp/ip stack?
Thanks, that didn't work but I appreciate it.
-----Original Message-----
From: Marc Catuogno [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 28, 2007 9:39 AM
To: [email protected]
Subject: RE: [IMail Forum] WAY OT: corrupt tcp/ip stack?
Try this:
http://www.majorgeeks.com/download4372.html
_____
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sharyn Schmidt
Sent: Tuesday, August 28, 2007 9:25 AM
To: [email protected]
Subject: [IMail Forum] WAY OT: corrupt tcp/ip stack?
Hi Folks,
Need to pick the brains of the gurus out there. We are having a weird problem
with some of our desktops. This has happened 3 times
in the last 3 weeks. We thought the first one was a fluke, then the 2nd one,
now a third. I have googled the solutions to this and
tried everything that I can find online, but so far the only fix has been to
reinstall windows which isn't a good option.
Here are the errors. It looks like, for some reason, the tcp/ip stack is being
hosed, but replacing it doesn't seem to work.
When doing an ipconfig, we get the following error:
An internal error occurred: The request is not supported.
Please contact MS product support services for further help.
Additional information: Unable to query routing information
When pinging 127.0.0.1:
Unable to contact IP driver, error code 2
In device manager, when, show hidden devices, non plug and play devices, there
is a yellow circle/explanation point icon next to the
tcp/ip protocol driver. When looking at the properties of this device its says:
This device is not present or not working properly or does not have all its
drivers installed (code 24)
When trying to repair the local area connection, the error is:
Failed to query tcp/ip settings of the connection.
This, to me, all points to a hosed tcp/ip stack. So far, I have deleted the
winsock entries in the registry and replaced the tcp/ip
stack, replaced the NIC (even though I didn't think that would work) launched
the windows recovery console and run a chkdsk /r , and
done all the usual things to troubleshoot tcp/ip errors. I'm out of ideas,
nothing seems to work.
Anyone encountered this before and actually fixed it without reinstalling
windows? This has been happening on our Win XP sp2
machines. No patches or any other additional software have been installed.
Thanks in advance!
Sharyn
