Quote:
The patch that you suggest merely changes the maximum limit of outbound uncompleted tcp connections. It does not remove this limit, only changes it.
Quote:
Other note as well, like I said before, this still does not 'uncap' the limit, just changes it.
Correct. However, 1677214 WAS the limit cap for preSP2 on 2k and XP SP1. While it was called uncapped, the actual number was 1677214 because of how insanely high it is. That setting is no different than Pre SP1
Quote:
Even after setting it to 16,777,214 connections per second, I was still able to get event log to generate ID 4226 errors. 4226 is the new error code that is issued whenever windows reaches the set limit of outbound uncompleted tcp conncetions, and blocks further ones.
Then you need to make sure the settings held by running it again to verify (not reset, just run) the amount of allowed connections. I don't have any errors being logged even with trillian, firefox, bittorrent (hosting sp2), and music streaming. I don't know why you are getting errors, but it isn't par and may be your settings. Like I said. Rerun the executable and see if your configuration settings held. This means run it without the /L. Windows tries to replace this file if you are not running it in safe mode, so make sure you did it in safe mode as well.
Quote:
It appears to only modifiy winnt\system32\drivers\TCPIP.sys
Correct. Because that is the only file in the entire OS that controls the rates/limits on tcp/ip connections. There wouldn't be a reason to modify anything else since nothing else touches it.
Quote:
So you can use a 3rd party program written by some kid
Careful there. You trust nmap don't you? And that wasn't started by a 31337 company.
