Deprecated: Assigning the return value of new by reference is deprecated in /home/holiday/public_html/wp-settings.php on line 520

Deprecated: Assigning the return value of new by reference is deprecated in /home/holiday/public_html/wp-settings.php on line 535

Deprecated: Assigning the return value of new by reference is deprecated in /home/holiday/public_html/wp-settings.php on line 542

Deprecated: Assigning the return value of new by reference is deprecated in /home/holiday/public_html/wp-settings.php on line 578

Deprecated: Function set_magic_quotes_runtime() is deprecated in /home/holiday/public_html/wp-settings.php on line 18
Windows XP SP 2, Vista, TCP connections, download speed limit FIX - Holiday Beard

Windows XP SP 2, Vista, TCP connections, download speed limit FIX

Windows XP Service Pack 2 places a very low limit on how many tcp connections can be opening at one time. This was done to cut down on the spread of internet worms. However this limit can cause problems with network applications such as Soulseek, and other downloading applications that uses multiple connections, which when doing things like returning a large amount of search results can easily surpass this limit.

If you suspect you have this problem, and are seeing the message "EventID 4226: TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts" in your Event Viewer, in order to rectify this problem you will need to run a small program that will allow you to change the connection attempt limit to a higher number. It is available at www.lvllord.de.

Run this program and increase the maximum number of connections from 10. A maximum setting of 50 connections might be a good place to start but you may need to go even higher to get the best performance from soulseek and other downloading programs that uses multiple connections.

Be careful when you run this patch! It changes important system settings and if done incorrectly could cause you major problems. USE AT YOUR OWN RISK!


VISTA

The same thing can happen to you if you are using Windows Vista.

A patch that works for all operating systems since XP sp2 is available here. It must be applied again after Microsoft hotfix or service pack modifies tcpip.sys.

Another possibility is not patching the tcpip.sys file but patching it in memory after it loaded (you can run the memory patcher once (thus needing to apply it again after reboot) or by installing a driver that does it automatically after booting). More info here or here.

Again, use at your own risk.

Leave a Reply