What is the 4226 issue in Windows XP SP2?
Windows XP SP2 limits the number of TCP connection attempts to 10 (quite small ). If there are more concurrent TCP connection attempts, Windows generates a warning: EventID 4226: TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts. You can go to Xp's Admin tool, event viewer, look in system tab and notice tcpip entry (with yellow warning sign). The detailed discription can be found in Microsoft documentation: Event 4226, EVENT_TCPIP_TCP_CONNECT_LIMIT_REACHED (
http://go.microsoft.com/fwlink/event...=5.1.2600.2180)
In Windows XP SP2 there are only 10 concurrent TCP connection attempts possible, while in SP1 it has not been limited. (A connection attemp is a query to a computer, if it accept the TCP connection or not. If the computer is for example no more existent, it will be waited for a few seconds, until a timeout occurs and the connection attemp get canceled. )
[edit]
Do I need to patch tcpip.sys for 4226 issue in Windows XP SP2?
BitComet 0.55 or above can work correctly under Windows XP SP2 without patch. However, limiting the connection attempt by the system may result in a slower speed at the beginning of downloading, since fewer peers can be connected at the same time. For those behind a NAT or firewall, the thrid-party [
http://www.lvllord.de/ patch] for tcpip.sys to fix that SP2 issue is still recommended.