Resetting Winsock Protocol

chev65 said:

If you really want help with this problem then post a screen shot of your ipconfig /all here the next time you lose the connection and I will see if I can find a problem. This procedure has worked for me over 600 times to solve problems and I can assure you that your network problem is no different than anyone else's.

Thank you Rob. I appreciate the offer. If things follow the usual pattern of behavior I probably won't lose my connection again until the end of the month or so.

If you are only losing the connection once a month I would probably have to blame the ISP or their hardware.

Jacee said:

Do you have an automatic backup scheuled at the end of the month, or around that time?

No. I've always done manual backups, manual Windows Updates, etc out of fear that something might try to reboot my computer in the middle of it all.

I know it's an old post, but how about checking the MTU of the modem? Default MTU for Windows is 1500, try 1400 or 1300 on your pc to see if it helps.

Most ISPs now have their devices set to 1500, but some may still be in an old place about this.

Bill2 said:

1) Windows sockets configuration (Winsock) can get corrupted for various reasons such as installation of networking software, or malware infection, or even by security apps. When Winsock corrupts, you'll run into networking errors like "Page cannot be displayed” error messages.

What netsh winsock reset command does is to reset the Winsock Catalog to a clean state or default configuration. It removes all Winsock LSP (Layered Service Providers) previously installed, including the potential malfunctioning LSP that causes loss of network packets transmission failure. So all previously-installed LSPs must be reinstalled. This command does not affect Winsock Name Space Provider entries.

To check which LSPs are installed, use netsh winsock show catalog command.

2) For your connectivity problems, I think you need to explore alternate drivers. Also, if you have a spare NIC, test with that.

I had the same issue this weekend, on multiple Windows 2008 R2 servers - some just recently configured and other that have been in service for more than a year, but rebooted this past weekend for patches, some at remote sites, some in our primary datacenter. -All Windows 2008 R2, all use Sophos, firewall settings default from Microsoft. The fact that someone says that they have fixed the issue over 600 times tells me this is not related to a single misconfiguration error. This sounds like it's something with Winsock inside of Windows 7 / Windows 2008 R2.

The latest one I had to work on has all of the latest Microsoft patches and all of the latest firmware provided by IBM. It is brand new and our processes have us update everything on Day one to as new as it can be upgraded. New out of the box, with a standard image on it, I sent out 5 of these devices last week. Only one experienced the issue. All 5 are identical otherwise.

I know this thread is old, but I have this same problem with a Dell laptop running Windows 8.1. My husband's laptop is on the same router and network, and he does not experience the problem. The problem occurs about once a month, always a day or two after a Windows security update.