Home > OS >  A TCP client connection WindowsServer2008 machine server timeout, no error error for "10061&quo
A TCP client connection WindowsServer2008 machine server timeout, no error error for "10061&quo

Time:11-04

network environment: LAN, client and server in the same subnet
Server: WindowsServer2008
Client: Windows 7

Phenomenon:
When the server start up listening on port, the client program TCP can connect to the server and normal communication;
When the server application closed (i.e., there is no listener port), the client program TCP connection to a Socket times "server not found, may be the address of the server setting error, connection timeout." mistakes,

Question:
When the server program shut down (i.e., there is no listener port), the client program should be submitted to the TCP connection to a Socket "server rejected the connection, may be the server didn't open or port setting is wrong, the connection fails." error (error code is 10061), and the error will return immediately, instead of waiting for 20 seconds the Socket to the default connection timeout, in our company local area network (LAN) and most of the customers within the local area network (LAN) is the normal errors, but appear in a client the connection timeout problem, now I have modified the program, increase the timeout when establishing a connection, but I want to know is what did WindowsServer2008 firewall or tactical Settings, or local area network (LAN) what did the firewall Settings, led to such problems?


CodePudding user response:

No great god knows?
  • Related