Have you checked how many connections you have?
Start - Run - cmd
Type in netstat -a This will give you all of your connections (open and
listening)


"Torgeir Bakken (MVP)" wrote:

Eitan Caspi wrote:

Thank you Torgeir,

The text you referred to is similar to the one from the link in the link
followed from the event ID description.

I have also found this "patch", that hacks tcpip.sys, but I don't want to
use it until I read an official statement by MS regarding this issue, and of
course, it is not so safe to use such unknown solution. you can never know
when this "hacked" version will hit you.
This is why I didn't mention it here or provided a link.

I understand MS base reasoning for this issue, but it can't decide for me
what is "normal" in the way I activate my system.
Not all half-open TCP connections are driven from a malicious cause. Maybe I
am network admin scanning my network for threats?

I believe MS should provide a registry value to be added, that will omit
this limitation for users who know what they are doing, and know how to
protect themselves in the first place.
The current state is really not acceptable, and it is defecting XP.
Hi

The official statement from Microsoft at the time being is "Sorry,
there is no way to change this limit, this is by design".

But I would not be very surprised if Microsoft some time in the
future will release a hotfix that makes it possible to adjust the
limit (but I would guess that would be a type of hotfix documented
in a Knowledge Base article and where you need to call Microsoft
to obtain the updated file(s)).


--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx