With the release of Service Pack 2 (SP2) for Microsoft Windows XP, the SP2 has introduced a feature that limit concurrent TCP connection attempts that are possible to 10 per seconds. In Service Pack 1 or without Service Pack, there is no limit on concurrent TCP connection attemps.
This feature is introduced in order to reduce the threat of computer worms spreading too fast without control. With the limit, only a maximum of 10 connection attemps per second are allowed. This may have affects applications, servers and p2p programs that attemp to open many outbound connections at the same time.
To know if you’re hitting concurrent TCP connection attempts limit, use the Event Viewer. Under “System”, look for TCP/IP Warnings saying: “TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts”. It has the Event ID of 4226.
To change or remove the limit imposed on connection attempts in Windows XP SP2, you can use the following program that works on every language of Windows XP:
The available configuration settings are as below:
remotepeerlimit = 41
localpeerlimit = 35
totalpeerlimit = 51
simulconnectingpeer = 30
The value of above is the default setting. All of the settings are quite self-explanatory as its name. You may not see the above lines in setting.ini configuration file. If it’s not in the setting.ini, add it in.
It’s hard to determine the best setting for all as each user’s computer and network configuration is different. So the best way is to try it out yourself and determine for yourself. I set all my 4 settings to 100, and able to achieve a very smooth streaming and almost without disconnection.
http://www.mydigitallife.info/2005/11/15/ppstream-connection-limit-in-configuration-settings/
http://technet.microsoft.com/en-us/windowsvista/aa905086.aspx
http://www.microsoft.com/technet/community/columns/cableguy/cg1105.mspx
http://torrentfreak.com/vistas-virgin-stack-to-speed-up-your-torrents/
http://blogs.msdn.com/wndp/archive/2006/04/25/winhec-2006-tcpip-advances.aspx