As of Windows XP SP2, MS decided to "protect" us from malicious attacks by
hard limiting in TCPIP.sys the max number of connections per second.
(By hard I mean inside the code of TCPIP.sys and not in the registry)
That brought up Internet connection slowdown in machines running file
sharing programs and others because that limit was easily reached.
The infamous error could be read in Event Log as:
EventID 4226: TCP/IP has reached the security limit imposed on the number of
concurrent TCP connect attempts
There was a workaround which worked nicely in Windows x86 and x64 that could
be downloaded here:
[url]http://www.lvllord.de/?lang=en&url=tools&PHPSESSID=10b1cfc2015dde37f49db76073ef9a01[/url]
That program is not effective in Vista.
Does anybody know a workaround to this?
Carlos

Hi Carlos,

No workarounds that I know of. It's hard coded that way to keep people from
using it as a server OS.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
[url]http://mvp.support.microsoft.com/[/url]
Windows help - [url]www.rickrogers.org[/url]

"Carlos" <Carlos@discussions.microsoft.com> wrote in message
news:E922104E-85A3-416B-A01E-C49747A6DB57@microsoft.com...[color=blue]
> As of Windows XP SP2, MS decided to "protect" us from malicious attacks by
> hard limiting in TCPIP.sys the max number of connections per second.
> (By hard I mean inside the code of TCPIP.sys and not in the registry)
> That brought up Internet connection slowdown in machines running file
> sharing programs and others because that limit was easily reached.
> The infamous error could be read in Event Log as:
> EventID 4226: TCP/IP has reached the security limit imposed on the number
> of
> concurrent TCP connect attempts
> There was a workaround which worked nicely in Windows x86 and x64 that
> could
> be downloaded here:
> [url]http://www.lvllord.de/?lang=en&url=tools&PHPSESSID=10b1cfc2015dde37f49db76073ef9a01[/url]
> That program is not effective in Vista.
> Does anybody know a workaround to this?
> Carlos
>[/color]