then it starts to mark sockets that have been in TIME_WAIT

来源:服务器技术网nifengsoft.com- 阅读:107087

摘要:服务器技术网nifengsoft then it starts to mark sockets that have been in TIME_WAITWindows is configured by default to handle 1000 to 2000 concurrent tcpip connections.

 then it starts to mark sockets that have been in TIME_WAIT

Thanks in advance

Tags: Category:

Very nicely written article! Recently, all our computers were upgraded to Windows 7. One particular application that runs makes multiple tcp connections to a another application when the connection is made! Then application has to be closed and opened again and sometimes it still makes more than one connection. Any suggestion?


 then it starts to mark sockets that have been in TIME_WAIT state for more than 60 secs as free. It is possible to configure thifoganglao佛冈网s limit: [HKEY_LOCAL_MACHINE \System \CurrentControlSet \services \Tcpip \Parameters] MaxFreeTWTcbs = 1000 (Default = 1000 sockets) Note with Win2k3 SP1 the reuse of sockets have been changed

Note even if having optimized Windows to handle many concurrent connections, then connections might still be refused when reaching a certain limit, in case a NAT-Router/Firewall is placed infront of it, which is unable to handle so many concurrent connections.
More Info MS KB137984
Note if using the Professional/Home edition of Windows then it is very likely that it is crippled (By Microsoft) not to handle many concurrent TCP connections. Ex. Microsoft have officially stated that the backlog limit is 5 (200 when Server), so the Professional edition is not able to accept() more than 5 new connections concurrently. More Info MS KB127144

My company hasgot a 50 terminal server licence but only 5 clients log on at the same time. I check the terminal server configuration->RDP-TCP->properties->network adapter->Maximum connections is 5 I can't change it. Could you please help me?

To keep the TCP/IP stack from taking all resources on the computer, there are different parameters that control how many connections it can handle. If running applications that are constantly opening and closing connections (P2P), or are providing a service which many tries to connect to at the same time (Web-server like IIS), then one can improve the performance of these applications by changing the restriction limits.

 then it starts to mark sockets that have been in TIME_WAIT state for more than 60 secs as free. It is possible to configure thifoganglao佛冈网s limit: [HKEY_LOCAL_MACHINE \System \CurrentControlSet \services \Tcpip \Parameters] MaxFreeTWTcbs = 1000 (Default = 1000 sockets) Note with Win2k3 SP1 the reuse of sockets have been changed

More Info MS KB149532
AndrewK says:

TcpNumConnections = 0x00fffffe (Default = 16,777,214)
Tasneem says: