XPSP2 will limit your max. connections/sec
Posted by: [NT] on: 07/20/2004 02:29 PM [ Print | 3 comment(s) ] · 27997 views
Hi
Just found this in my event-log after starting emule:
"EventID 4226
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts"
This is what I get from a M$-Guy when i asked him why XPSP2 slows down programs like emule which open many connections to different destinations:
"Thanks very much for responding. This new feature is one of the stack's
"springboards", security features designed to proactively reduce the
future threat from attacks like blaster and Sasser that typically spread
by opening connections to random addresses. In fact, if this feature had
already been deployed, Sasser would have taken much longer to spread.
It's not likely to help stop the spread of spam unless spammers are
trying to reach open email relays in the same way, by opening
connections on smtp ports of random IP addresses.
This is new with XP SP2 and we're trying to get it right so that it does
not interfere with normal system operation or performance of normal,
legitimate applications, but does slow the spread of viral code. New
connection attempts over the limit for half-open connections get queued
and worked off at a certain (limited rate)."
If anyone knows how to switch it off please leave a comment...
Just found this in my event-log after starting emule:
"EventID 4226
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts"
This is what I get from a M$-Guy when i asked him why XPSP2 slows down programs like emule which open many connections to different destinations:
"Thanks very much for responding. This new feature is one of the stack's
"springboards", security features designed to proactively reduce the
future threat from attacks like blaster and Sasser that typically spread
by opening connections to random addresses. In fact, if this feature had
already been deployed, Sasser would have taken much longer to spread.
It's not likely to help stop the spread of spam unless spammers are
trying to reach open email relays in the same way, by opening
connections on smtp ports of random IP addresses.
This is new with XP SP2 and we're trying to get it right so that it does
not interfere with normal system operation or performance of normal,
legitimate applications, but does slow the spread of viral code. New
connection attempts over the limit for half-open connections get queued
and worked off at a certain (limited rate)."
If anyone knows how to switch it off please leave a comment...
« YMPEG 1.2 · XPSP2 will limit your max. connections/sec
· OpenGL Extension Viewer 2.10 »
Comment
|
LvlLord Unregistered |
#55395 Posted on: 07/27/2004 06:29 PM
Hi everybody! After almost everybody know, that the TcpNumConnections-Fix does not work, I've created yesterday a fix for that. It can be found under h**p://mitglied.lycos.de/lvllord Please post this to other forums, too. It's hard for me to do it alone *g* Greetz! LvlLord |
Comment
|
ZigZag Unregistered |
#55839 Posted on: 08/11/2004 01:31 AM
You can try downloading the following patch: ed2k://|file|Windows.XP.SP2.(Service.Pack.2)-10.Connections.Limit.Patch.zip|35778|cd3d3ee52661d23888383ac03626cf71| |
Comment
|
ZigZag Unregistered |
#55847 Posted on: 08/11/2004 04:03 PM
You can also try applying the following patch: Windows.XP.SP2.(Service.Pack.2)-10.Connections.Limit.Patch.zip 
|
