Quote Originally Posted by softmessager View Post
Thanks for all the replies ...

I will be posting the code.

Meanwhile what are the external reasons that the windows socket can fail?
-- coz the time out for this error is Exactly 1 hour...
Shouldn't your software have much more diagnostics than just a trace file, given the fact you are dealing with sockets and communication? Maybe the computer is running an app that closes the socket, maybe their TCP/IP settings have a role in this, etc.

The point being that you should have had most, if not all of these bases covered. Where is the information on the TCP/IP settings? Do you collect that information? Maybe the computer puts the network card to sleep after 1 hour and never wakes up (for whatever reason).

I could go on about it, but if you're going to distribute a program to the public that relies on TCP/IP, that program can't just be an ordinary application with just a trace file to help you out.

Regards,

Paul McKenzie