Friends who often use BT software to download may find a strange phenomenon: after upgrading the system to Windows XP SP2, they downloaded Rufei BT in the previous system, but often failed to connect. Even if connected, the download/upload speed is not as good as before.
At first I thought there was something wrong with the BT software, but after I tried almost all the BT software on the market, the situation still did not improve. I uninstalled the Rising Firewall again, but it still doesn't work. So I simply restored the system to SP1 (I kept the GHOST backup of SP1 when I upgraded to SP2), and BT came back to "live". So I concluded that the problem must be on SP2.
By chance, I saw many warnings about Tcpip in "Control Panel" → "Performance and Maintenance" → "Administrative Tools" → "Event Viewer" → "System". The event code is 4226, and the event time is exactly when I use BT software. So, I selected a Tcpip event and saw the description of the event in the "Operation" → "Properties" of the menu: "TCP/IP has reached the security limit of the number of TCP connection attempts. For more information, see the Help and Support Center in /fwlink/." It was learned through help that the Windows XP SP2 released by Microsoft has increased the limit of TCP simultaneous connection attempts and set it to a very small value of "10". When the system's TCP connection attempt exceeds this value, the system will refuse to connect due to security factors. The original intention of this is to prevent multi-threaded attacks from viruses such as shock waves and shock waves. However, in this way, some P2P software will suffer. When busy, all network connections may not be possible. The problem of BT software being unable to connect to often has finally been found.
We can solve this problem by installing a third-party patch. The operating system that can currently 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, and the download address is: /?url=en/
The easiest way to install is to decompress and double-click to run, and then press "Y" (the default limit is relaxed to 50, if you press "C", you can change it to a larger number). Because the system file is modified, Windows will pop up the Windows file protection dialog box, click Cancel and select Keep the current version. After restarting, we can go crazy with BT again.
At first I thought there was something wrong with the BT software, but after I tried almost all the BT software on the market, the situation still did not improve. I uninstalled the Rising Firewall again, but it still doesn't work. So I simply restored the system to SP1 (I kept the GHOST backup of SP1 when I upgraded to SP2), and BT came back to "live". So I concluded that the problem must be on SP2.
By chance, I saw many warnings about Tcpip in "Control Panel" → "Performance and Maintenance" → "Administrative Tools" → "Event Viewer" → "System". The event code is 4226, and the event time is exactly when I use BT software. So, I selected a Tcpip event and saw the description of the event in the "Operation" → "Properties" of the menu: "TCP/IP has reached the security limit of the number of TCP connection attempts. For more information, see the Help and Support Center in /fwlink/." It was learned through help that the Windows XP SP2 released by Microsoft has increased the limit of TCP simultaneous connection attempts and set it to a very small value of "10". When the system's TCP connection attempt exceeds this value, the system will refuse to connect due to security factors. The original intention of this is to prevent multi-threaded attacks from viruses such as shock waves and shock waves. However, in this way, some P2P software will suffer. When busy, all network connections may not be possible. The problem of BT software being unable to connect to often has finally been found.
We can solve this problem by installing a third-party patch. The operating system that can currently 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, and the download address is: /?url=en/
The easiest way to install is to decompress and double-click to run, and then press "Y" (the default limit is relaxed to 50, if you press "C", you can change it to a larger number). Because the system file is modified, Windows will pop up the Windows file protection dialog box, click Cancel and select Keep the current version. After restarting, we can go crazy with BT again.