Author Topic: TCP/IP.sys Half-open connection limit guide.  (Read 2986 times)

Offline javajolt

  • Administrator
  • Hero Member
  • *****
  • Posts: 36193
  • Gender: Male
  • I Do Windows
    • windows10newsinfo.com
TCP/IP.sys Half-open connection limit guide.
« on: March 22, 2009, 02:55:15 AM »
TCP/IP.sys Half-open connection limit guide. by Dark Shroud

Ok, this is the start of a guide on the tcpip.sys limit of 10 half-open simultaneous/concurrent connection attempts added to XP in SP-2 and in SP-1 for Server 2003, Vista & Server 2008. How it works why it was put in place and of course why you don't need to mess with it.

Vista users: if you use Vista don't even try messing with the tcpip.sys file. It's updated for performance & security very often. You'll be wasting your time and giving yourself many head aches trying to fight Vista.

Before I begin a courtesy link to the LvlLord website.

Now how many times have you seen the following:

"My download speed is slow. How do I make it go faster? Have you patched your copy of XP yet?"
"BitTorrent is slow! What am I doing wrong? "Have you patched service pack 2 yet?"
"My downloads are taking forever! Patch your connection limit."

This is all to common across the web and it's all wrong.

This limit of 10 incomplete outbound TCP/IP connection attempts per second. It is not a limit on ports, complete connections, nor does it drop or block connections. The connections past 10 are put into a queue or put on hold. Meaning when one connection is either completed or timed out it moves onto the next waiting connection. This queue does not fill up either. So once again I will say no connection is dropped, blocked, or lost. This limit only affects connecting to other clients, not the actual downloading of data from them. If you’re on a proper high speed connection you will not even notice this because it only slows you down by a matter of seconds when the .torret is started. Just leave BitComet's half-open connection limit of 8 alone (Note: double check this setting, some versions are set to 10 by default). With that setting you'll still be able to web surf while using BitComet, after all you want to leave your browser to slots to connect to web pages.

This was put in place to help prevent the spread of worms like Blaster and hinder a computer's use in performing DOS attacks.

This does not affect any type of DHT connection for any of the p2p programs that use DHT. Because DHT uses UDP for connecting, this is not limited in any way other than the speed of your connection. So just use DHT at start up and you’ll be fine.

In addition all the people who do not know what they're talking about in regards to the "patch" need to stop posting about it. It is very outdated so it screws up your internet connections. If you're using XP Pro Media Center Edition it will kill your connection all together and you'll need to do a system restore to fix the damage. I know this first hand from the last time I tried to do some tests using my new media center edition computer.

There are a couple of patches out there claiming to be "accelerator patches for BitComet" and that is the problem. The LvlLord patch is the only one I know of that doesn't contain spyware/adaware. The other patches don't even do anything to help.

This "patch" was made for use with older p2p networks designs, like Fast Track, & Gnutella where you search nodes, super nodes, and servers. Back then majorities of the users were still on dial-up, and bad dial-up at it. So all they understood was the word limit and this limit would slow them down so it had to go. So a few people with limited knowledge wrote various "patches" for this evil TCP/IP limit to either set it to a higher number or in one case remove it all together.

This patch is only capable of setting up more connections in the same amount of time as normal so it can appear to speed up downloads when its not actually helping the download its self. But it’s no longer needed with high speed connections and the new structure of p2p networks like and features such as using DHT for starters. Programs like BitComet, µTorrent and many others have already adjusted their connection structure for it. Most importantly May 1st, 2005 was its last bug fix release for the LvlLord patch. Every few months Microsoft releases a new tcpip.sys for XP, since this patches last update, tons of stuff for Win2k3 and a different TCP/IP structure for XP Media Center Edition that the patch won’t work with at all. Lets not even get started with Vista's security updates. Not to mention that Microsoft is well aware of the “patch” so windows update will remove it, this is a good thing. While MS continue to find ways to block these mods.

Microsoft wrote:

Limited number of simultaneous incomplete outbound TCP connection attempts— The TCP/IP stack now limits the number of simultaneous incomplete outbound TCP connection attempts. After the limit has been reached, subsequent connection attempts are put in a queue to be resolved at a fixed rate. Under normal operation, when applications are connecting to available hosts at valid IP addresses, no connection rate-limiting occurs. When it does occur, a new event, with ID 4226, appears in the system’s event log. What works differently? This change may cause certain security tools, such as port scanners, to run more slowly. How do I resolve these issues? Stop the application that is responsible for the failing connection attempts.

From microsoft.com

10 half-open simultaneous/concurrent connection ATTEMPTS are more than enough, even for P2P. This limit is a rate limiter, not a connection limiter. You can have tons of half-open connections, just not have them initialized all at the exact same time. Please note the difference between 'half-open connection attempts' and 'half-open connections'.