Network cable unplugged - EWeek

[Lance]

How he fixed a "Network cable unplugged" error and possible cause:

Full story at:
http://story.news.yahoo.com/news?tmpl=story&cid=1738&ncid=1212&e=5&u=/zd/20040903/tc_zd/134436

Basically, he recovered from a corrupt WinSock and blames past or
present adware/spyware infections.

Lance
*****

Corruption at the Jersey Shore
Bill Machrone - PC Magazine

"...Later, when I had both machines connected wirelessly, the first one
kept nattering that a network cable was unplugged, and it would drop the
wireless connection at odd times.

I did a little poking around in the Microsoft Knowledge Base and found
that this was not an unusual problem and that it was caused by
corruption of the Winsock. I hadn't thought about the Winsock—the
Windows TCP/IP socket API and IP stack—in years, at least not since the
advent of Windows XP (news - web sites). But it used to be a veritable
Achilles' heel for Windows systems."

[Steve Winograd [MVP]]

In article >, Lance
> wrote:
>How he fixed a "Network cable unplugged" error and possible cause:
>
>Full story at:
>http://story.news.yahoo.com/news?tmpl=story&cid=1738&ncid=1212&e=5&u=/zd/20040903/tc_zd/134436
>
>Basically, he recovered from a corrupt WinSock and blames past or
>present adware/spyware infections.
>
>Lance
>*****
>
>Corruption at the Jersey Shore
>Bill Machrone - PC Magazine
>
>"...Later, when I had both machines connected wirelessly, the first one
>kept nattering that a network cable was unplugged, and it would drop the
>wireless connection at odd times.
>
>I did a little poking around in the Microsoft Knowledge Base and found
>that this was not an unusual problem and that it was caused by
>corruption of the Winsock. I hadn't thought about the Winsock—the
>Windows TCP/IP socket API and IP stack—in years, at least not since the
>advent of Windows XP (news - web sites). But it used to be a veritable
>Achilles' heel for Windows systems."

That's one of the best XP-related magazine articles I've seen. Thanks
for posting it. I'm sure that it will help people.

BTW, has Microsoft recognized the need to fix Winsock corruption and
added a command for it to XP Service Pack 2. Enter this at the
command prompt:

netsh winsock reset catalog
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

[GTS]

Thanks! The "netsh winsock reset catalog" command is a great piece of
info.

(Wish I'd know this yesterday - went through hell on a client's machine with
major spyware damage. LSPFIX etc. failed dismally. Got it straightened
out, but I wonder if this new command might have worked right off.)
--

"Steve Winograd [MVP]" > wrote in message
...
> In article >, Lance
> > wrote:
>>How he fixed a "Network cable unplugged" error and possible cause:
>>
>>Full story at:
>>http://story.news.yahoo.com/news?tmpl=story&cid=1738&ncid=1212&e=5&u=/zd/20040903/tc_zd/134436
>>
>>Basically, he recovered from a corrupt WinSock and blames past or
>>present adware/spyware infections.
>>
>>Lance
>>*****
>>
>>Corruption at the Jersey Shore
>>Bill Machrone - PC Magazine
>>
>>"...Later, when I had both machines connected wirelessly, the first one
>>kept nattering that a network cable was unplugged, and it would drop the
>>wireless connection at odd times.
>>
>>I did a little poking around in the Microsoft Knowledge Base and found
>>that this was not an unusual problem and that it was caused by
>>corruption of the Winsock. I hadn't thought about the Winsock-the
>>Windows TCP/IP socket API and IP stack-in years, at least not since the
>>advent of Windows XP (news - web sites). But it used to be a veritable
>>Achilles' heel for Windows systems."
>
> That's one of the best XP-related magazine articles I've seen. Thanks
> for posting it. I'm sure that it will help people.
>
> BTW, has Microsoft recognized the need to fix Winsock corruption and
> added a command for it to XP Service Pack 2. Enter this at the
> command prompt:
>
> netsh winsock reset catalog
> --
> Best Wishes,
> Steve Winograd, MS-MVP (Windows Networking)
>
> Please post any reply as a follow-up message in the news group
> for everyone to see. I'm sorry, but I don't answer questions
> addressed directly to me in E-mail or news groups.
>
> Microsoft Most Valuable Professional Program
> http://mvp.support.microsoft.com