XPSP2 will limit your max. connections/sec *Update*
Posted by: Newsfactory on: 07/21/2004 11:42 PM [ Print | 6 comment(s) ] · 20471 views
Following Mr A's article posted in our Readers News section XPSP2 will limit your max. connections/sec ! Here's a Possible fix thanks to Bink.Nu and Mr A!
This articles from microsoft KB explain how to change the TCP/IP parameters. TCP/IP and NBT Configuration Parameters for Windows XP (Q314053)
This is the key to add to modify the maximum number of simultaneous connections
TcpNumConnections
Key: TcpipParameters
Value Type: REG_DWORD - Number
Valid Range: 0 - 0xfffffe
Default: 0xfffffe
Description: This parameter limits the maximum number of connections that TCP can have open simultaneously.
TCP/IP and NBT configuration parameters for Windows XP - (Q314053)
This articles from microsoft KB explain how to change the TCP/IP parameters. TCP/IP and NBT Configuration Parameters for Windows XP (Q314053)
This is the key to add to modify the maximum number of simultaneous connections
TcpNumConnections
Key: TcpipParameters
Value Type: REG_DWORD - Number
Valid Range: 0 - 0xfffffe
Default: 0xfffffe
Description: This parameter limits the maximum number of connections that TCP can have open simultaneously.
TCP/IP and NBT configuration parameters for Windows XP - (Q314053)
« Windows Server 2003 Service Pack 1 Build 1218 · XPSP2 will limit your max. connections/sec *Update*
· FD Tach 0.9 & Q-Bench »
Comment
|
mooninite Unregistered |
#55254 Posted on: 07/22/2004 12:12 AM
If the default is the maximum you can enter, what else would you want to enter? Is it just me or was this article stupid? No desktop PC will need this feature anyway. |
Comment
|
Chicken Unregistered Posts: 279 Joined: 2002-02-11 |
#55255 Posted on: 07/22/2004 12:41 AM
Yeah the "fix" does not help, setting it to 0 just makes it go back to default too. |
Comment
|
Hysteria Unregistered |
#55256 Posted on: 07/22/2004 01:08 AM
Perhaps the default value was what it was before SP2 changed it. I'm using SP2 RC2 and didn't find the key TCPNUMCONNECTIONS in my registry. I added it and it's at 16777214. Looks like plenty to me  |
Comment
|
jessc Unregistered |
#55257 Posted on: 07/22/2004 04:18 AM
I have put the following into the reg to see what affect it would have, and it seems to have stoppped the error for the moment.. [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters] "TcpNumConnections"=dword:00000020 |
Comment
|
Huigie Unregistered |
#55259 Posted on: 07/22/2004 07:21 AM
If you give a tip, do it properly! |
Comment
|
Chicken Unregistered Posts: 279 Joined: 2002-02-11 |
#55260 Posted on: 07/22/2004 09:29 AM
The KB article says it is not there by default. IT dosn't seem to fix the problem anyway. |
