Windows XP SP2 released by Microsoft adds the limit for simultaneous TCP connection attempts and is set to a very small value of 10. When the system's TCP connection attempts exceed this value, the system rejects the connection due to security reasons. This is intended to prevent worms such as shock waves, but some P2P software suffers. When the connection is busy, all network connections may fail. In the control panel-Administrative Tools-time viewer-system, you can see the warning that the ID of the source TCPIP is 4226: "TCP/IP has reached the security limit for the number of concurrent TCP connection attempts." Microsoft described this warning as follows: Event 4226, event_tcpip_tcp_connect_limit_reached [LINK]. This problem is especially evident for bitcomet Intranet users, because Intranet users can only actively initiate TCP connections to connect to other clients.
A third-party Patch [Download] [forum discussion] can be used to change tcpip. sys to correct the system connection limit. Currently, the operating system that can use this third-party patch is Windows XP SP2 (RC2 or above) or Windows 2003 Server SP1 beta. The current version of this patch is 2.11a, which can be downloaded here: http://www.lvllord.de/download.php? Url = EN/EvID4226Patch211a-en.zip
The simplest installation method is to run evid4226patch.exe by pressing "Y", and then press "Y" (this limit is relaxed to 50 by default. If you press "C", you can change it to a larger number ). Because the system file tcpip. sys is modified, the Windows File Protection dialog box is displayed in windows. Click Cancel and choose to retain the current version. It takes effect after restart.
Http://mitglied.lycos.de/lvllord/download-mirror.htm about this patch (I just downloaded)