Winsock woes

  • Thread starter Thread starter Timm
  • Start date Start date
T

Timm

I recently installed the drivers for the D-Link USB Bluetooth adapter on my
laptop, and have had nothing but problems since. (I did notice that there
was a message that it updated the Winsock drivers during the installation.)

The biggest problem seems to be the corruption of the Winsock, which is
fairly common from what I've heard. I've already copied the winsock
registry entries from a working XP machine and have deleted the
corresponding entries from the laptop and installed the copies. I've also
downloaded and run a WinsockXPFix program to help. Each of these fixes
works.... temporarily.

Whenever I change networks (I have to change the IP address and change from
a workgroup to the domain we have at work), the problem arises again. I
have to reapply the fix and then everything seems to be working.

I've tried reinstalling the OS over the top (with the Bluetooth drivers
still installed). I've uninstalled the nasty D-Link drivers, and
reinstalled the OS _again_. Nothing seems to help.

Any suggestions
 
Scanned for spyware and removed a bunch. However, the problem is still
there. I've managed to "localize" the problem. It happens when I make
changes to the TCP/IP settings when I'm switching networks. One network
requires me to specify the address, gateway, and DNS server. I change the
settings back to automatic at home.

Ken Wickes said:
Scanned for spyware?

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.


Timm said:
I recently installed the drivers for the D-Link USB Bluetooth adapter on my
laptop, and have had nothing but problems since. (I did notice that there
was a message that it updated the Winsock drivers during the installation.)

The biggest problem seems to be the corruption of the Winsock, which is
fairly common from what I've heard. I've already copied the winsock
registry entries from a working XP machine and have deleted the
corresponding entries from the laptop and installed the copies. I've also
downloaded and run a WinsockXPFix program to help. Each of these fixes
works.... temporarily.

Whenever I change networks (I have to change the IP address and change from
a workgroup to the domain we have at work), the problem arises again. I
have to reapply the fix and then everything seems to be working.

I've tried reinstalling the OS over the top (with the Bluetooth drivers
still installed). I've uninstalled the nasty D-Link drivers, and
reinstalled the OS _again_. Nothing seems to help.

Any suggestions
Click to expand...
Click to expand...
 
When things are not working run "winmsd" and go to
Components/Network/Protocol. Copy the data in the right hand pane and post
it here.

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.


Timm said:
Scanned for spyware and removed a bunch. However, the problem is still
there. I've managed to "localize" the problem. It happens when I make
changes to the TCP/IP settings when I'm switching networks. One network
requires me to specify the address, gateway, and DNS server. I change the
settings back to automatic at home.

Ken Wickes said:
Scanned for spyware?

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.


Timm said:
I recently installed the drivers for the D-Link USB Bluetooth adapter
Click to expand...
on
my
laptop, and have had nothing but problems since. (I did notice that there
was a message that it updated the Winsock drivers during the installation.)

The biggest problem seems to be the corruption of the Winsock, which is
fairly common from what I've heard. I've already copied the winsock
registry entries from a working XP machine and have deleted the
corresponding entries from the laptop and installed the copies. I've also
downloaded and run a WinsockXPFix program to help. Each of these fixes
works.... temporarily.

Whenever I change networks (I have to change the IP address and change from
a workgroup to the domain we have at work), the problem arises again. I
have to reapply the fix and then everything seems to be working.

I've tried reinstalling the OS over the top (with the Bluetooth drivers
still installed). I've uninstalled the nasty D-Link drivers, and
reinstalled the OS _again_. Nothing seems to help.

Any suggestions
Click to expand...
Click to expand...
Click to expand...
 
Back
Top