I hate to suggest this, but did you try Windows system restore to a point
before it was non-functioning? Marc Catuogno
MIS Director
Prudential Rand Realty
845-825-8025
-----Original Message-----
From: "Sharyn Schmidt" <[EMAIL PROTECTED]>
Sent 8/28/2007 11:09:22 AM
To: [email protected]
Subject: RE: [IMail Forum] WAY OT: corrupt tcp/ip stack?v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
P {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New
Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
page: Section1
}
Thanks, that didn't work but I appreciate it.-----Original Message-----From:
Marc Catuogno [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 28, 2007 9:39
AMTo: [EMAIL PROTECTED]: 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 SchmidtSent: Tuesday, August 28,
2007 9:25 AMTo: [EMAIL PROTECTED]: [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 2In 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
