WinSock client locking up all tcp/ip traffic on local machine
-
I have a simple client-server socket application. After the client runs for a while (2/3 days) the client machine gets to a state where it cannot make any outbound tcp/ip connections (i.e., browser, http requests, etc). Once I restart the client (running as a service) then everything seems to work fine. I ran the scoket code through BoundsChecker to look for any memory or resource leaks and didnt find any. Has anyone here faced this or a similar issue? Any help would be greatly appreciated. TIA
-
I have a simple client-server socket application. After the client runs for a while (2/3 days) the client machine gets to a state where it cannot make any outbound tcp/ip connections (i.e., browser, http requests, etc). Once I restart the client (running as a service) then everything seems to work fine. I ran the scoket code through BoundsChecker to look for any memory or resource leaks and didnt find any. Has anyone here faced this or a similar issue? Any help would be greatly appreciated. TIA