Re: Winsock Problem and XP
From: Ken Wickes [MSFT] (kenwic_at_online.microsoft.com)
Date: 02/18/04
- Next message: mcp6453: "Problem Accessing Shared Drive"
- Previous message: Ken Wickes [MSFT]: "Re: TCP/IP Protocol Corrupted"
- In reply to: RobH: "Winsock Problem and XP"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 17 Feb 2004 16:42:39 -0800
Typically it happens when installing or uninstalling 3rd party firewalls,
virus scanners and the like. I've never seen Windows alone corrupt it.
-- Ken Wickes [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. "RobH" <anonymous@discussions.microsoft.com> wrote in message news:1195e01c3f4d7$d6c55b30$a501280a@phx.gbl... > I have looked through these forums and have seen numerous > listings about the network connectivity issues concerning > Winsock getting corrupted. This has happened to me on two > seperate PC's on two seperate occasions on a home network. > Both PC's are running XP Home edition. My question is, why > is this happening? I have been using XP since it was first > released and have only just starting experiencing the > problem in the last several months. Is this being caused > by a recent Microsoft XP update (I keep both PC's current > on all updates)? According to the Knowledge base article > (811259) this happens when the registry keys get > corrupted, however I am not in the registry changing > things and I don't have any out of the ordinary > applications installed, both PC's are pretty much standard > home PC builds. It would be nice if a Microsoft Support > Rep could give us some insight as to why this is happening.
- Next message: mcp6453: "Problem Accessing Shared Drive"
- Previous message: Ken Wickes [MSFT]: "Re: TCP/IP Protocol Corrupted"
- In reply to: RobH: "Winsock Problem and XP"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
