[RESOLVED] Winsock fails after 1 hour

[Paul McKenzie]

NOTE : This is failing in only one setup. we have 1000's of people usng our product in around 100's of these setup's including 2003 , 2008 xp windows 7 etc
This problem is only seen with one particular customer and he is able to reproduce it 100% of his time.

If Mike's explanation solves your issue, then the quote from you above doesn't sound too promising.

A product that has been running on thousands of machines and on different OSes, and no one at your end who maintains the socket communication knew anything about this setting? This is where your software needs to write to the trace file all of the settings. You can start here, and add to the trace all of these settings you see here:

http://msdn.microsoft.com/en-us/libr...=vs.85%29.aspx

Even if you don't understand those settings, write the values of those settings to your traces. Then when you get the trace, you see exactly what you're dealing with. Yes, there could be many standard settings, but if you really do have a product that you distribute to customers, it is your responsibility to have this information.

This is exactly how my company's software deals with scanners -- in our trace file, we record practically everything about the device our software is communicating with. My software calls a series of functions when running in "diagnostic mode" that retrieves all of the information about the devices we're communicating with. Otherwise, we have a deficient product and would not be ready when that odd scanner used by some far-flung customer doesn't work correctly with our software.

Regards,

Paul McKenzie