Hello Wilfried, That's right, the client was connected without socket error.
On one of the PCs it happens persistently since recently. (It didn't happen on that pc before.) One another PC, it gets 10053 once in a while but it can be a few dozen times a day. On those PCs, other applications (IE, etc.) just run fine. This has been puzzling me for a while ... -- Best regards, Jack Wednesday, April 5, 2006, 11:12:43 AM, you wrote: > Hello Jack, > 10053 is WSAECONNABORTED or in words: 'Software caused connection abort' > witch means that the OS has decided to abort the connection due to some > uknown reason. It is not nececary the OS, can also be a decision of a > router. > Question: You are getting connected without winsock error do you ? > I have also seen this error because of software firewalls doing their > job incorrect. Also seen it on large networks interconnected by routers > where transport failures happens over the (leased) line. > Hope this helps a little to determine where the problem could be ? > --- > Rgds, Wilfried [TeamICS] > http://www.overbyte.be/eng/overbyte/teamics.html > http://www.mestdagh.biz > Wednesday, April 5, 2006, 17:10, Jack wrote: >> Hi Francois and all, >> I have a client software. On some of the PC, when the client >> is connected to the server and wants to send some data, a twsocket >> OnSessionClosed() event is triggered with an error code of 10053. >> When this happens, it will happen again and again. Other applications >> like IE, firefox, email, etc. on the same PC seem to work fine. >> This problem didn't happen before even on this PC. And a similar >> problem happens on some other PC as well. Any idea what can cause >> this? >> -- >> Best regards, >> Jack -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
