What causes winsock 10055 errors? How should I troubleshoot?

Solution 1:

Ram shortages can cause this also, according to Google searches, among other things. An error condition I observed via Google in finding some of below was low memory issues where the base operating system had little access to RAM. My guess is that same type of problem could easily be recreated in a virtual environment that is starved for ram.

A more fundamental troubleshooting question is quite simply - what is different with your production environment?

Have you tested the application in Windows 2003 x64 or Windows 2008?

Onto the 2nd part of your questions..

The following tools can be used for troubleshooting and fixing Winsock errors.

Sniffers:

http://www.wireshark.org/ 

Shims:

http://www.sstinc.com/winsock.html
http://www.win-tech.com/html/socktspy.htm

General purpose tools to track the system status and resources

http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
http://technet.microsoft.com/en-us/sysinternals/bb896645

Tool to detect the API calls

http://www.apimonitor.com/
http://www.nektra.com/products/spystudio-api-monitor/

Debuggers

http://www.ollydbg.de/
http://www.immunitysec.com/products-immdbg.shtml

Reversing tools or decompilers

http://www.hex-rays.com/products/ida/index.shtml
http://www.hex-rays.com/products/decompiler/index.shtml

Your standard IDE and compiler

http://www.microsoft.com/visualstudio/en-us

Here is a list of other tools:

http://www.sockets.com/devtools.htm

Other references found:

https://stackoverflow.com/questions/8118870/howto-debug-winsock-api-calls

http://brandon.fuller.name/archives/2007/01/24/19.44.29/

http://tangentsoft.net/ <---- Probably the best one

Solution 2:

Reinstall with 2008 R2 server, this will work hopefully. There is absolutely new driver architecture and way better networking scalability.