Jump to content

TCP/IP has reached the security limit imposed XP SP2


Trix

Recommended Posts

Posted

I still get this TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts. Error showing up quite a bit in XP SP2.

Posted

Patching windows itself shouldn't be a solution, many argue against patching it, for it is indeed a smart thing to have, it is debateable though. Just wondering what setting can calm this.

Posted

You can reduce the setting "net.max_halfopen" a bit to get rid of that error-log, but that would make µTorrent connect to peers a little slower if I've gotten it right.

Posted

It's just saying you've maxed out your half-open TCP connections and it is placing all the extras in a queue to be processed later (I believe it's 10 per sec unpatched).

It's not really an error message so much as just informing you what's happening. The reason behind the limit is to slow down worm/malware propogation although, to my knowledge, this hasn't been proven to have a positive effect. It's more of a minor nuisance to P2P and BitTorrent. Patching is typically unnecessary, but if the nagging eventlog gets to you, it's easy enough to patch.

Posted

I patched and set my max TCP/IP per sec from 10 to 1500 and then halfopen to 12 and it works great I never get the error anymore

If you think 1500 is too high on SP1 the limit was 65000.

Posted

All I know is ppl using any p2p app from SP1 to SP2 noticed the difference in speeds and/or connections when SP2 came out. Alot ppl cant be wrong.

Posted
All I know is ppl using any p2p app from SP1 to SP2 noticed the difference in speeds and/or connections when SP2 came out. Alot ppl cant be wrong.

It's possible.

*cough* Bush Administration *cough*

Posted

1500 is still too high, the point of reducing it was to help stop the spread of worms and whatnot... What the hell do you need 1500 for? To connect to 100 peers in 50 msec? 100 is way more than enough, especially since you shouldn't be using more than 150 peers/torrent anyway ;p

Posted

Hmm... I guess I could patch. It just seems like a strange solution, very debatable, I mention patching to someone "You are stupid, Microsoft did it for a reason." or "SP1's limit was higher, so SP2 can be a bit higher, you won't affect anything."

Posted

Is there any reason why avast! finds a Trojan in the lvllord's patch? The one I downloaded a week ago and the one I just got from that link. :|

Someone tell me that is just a false positive, someone who sounds like they know what they are talking about! :P

Inac

Posted
Is there any reason why avast! finds a Trojan in the lvllord's patch? The one I downloaded a week ago and the one I just got from that link. :|

Someone tell me that is just a false positive, someone who sounds like they know what they are talking about! :P

Inac

its a false positive. Avast most likely check if the tcpip.sys is modified,

which it is when you use lvllords patch.

They possibly added that incase of future worms/viruses tries to modify the tcpip.sys.

Posted
Is there any reason why avast! finds a Trojan in the lvllord's patch? The one I downloaded a week ago and the one I just got from that link. :|

Someone tell me that is just a false positive, someone who sounds like they know what they are talking about! :P

Inac

I agree, it is a false positive - nevertheless, getting avast to leave the file alone is a pain.

Download 'XP-Antispy' - http://www.xp-antispy.org/

It uses the same code (with permission) to increase the connection limit.

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...