XP SP2 & CableNut

mnosteele52 · Post by **mnosteele52** » Tue Aug 10, 2004 12:25 pm

Please take the time to read about the changes in XP after installing SP2, you will be suprised - HERE.

:2cool:

Curt · Post by **Curt** » Thu Aug 12, 2004 12:35 am

Windows XP Home Service Pack 2, Cablenut, RASPPPoE, and SBC Yahoo! DSL 1500/384:

I have Windows XP Home Service Pack 2 tweaked with Cablenut, the registry tweaks below and RASPPPoE on my SBC Yahoo! 1500/384 DSL connection right now. Web surfing and downloading is VERY fast. (I still plan on using Netscape 7.2.) The MTU is set to 1480 in RASPPPoE and Cablenut has the following settings:

Cablenut Settings:

DefaultReceiveWindow = 192000
DefaultSendWindow = 49152
DisableAddressSharing = 1
InitialLargeBufferCount = 200
InitialMediumBufferCount = 480
InitialSmallBufferCount = 640
LargeBufferSize = 819200
MaxFastTransmit = 64000
MediumBufferSize = 150400
Priority Boost = 0
SmallBufferSize = 12800
TransmitWorker = 32
FastSendDatagramThreshhold = 4096
EnableFastRouteLookup = 1
EnablePMTUDiscovery = 1
IgnorePushBitsOnReceives = 0
GlobalMaxTcpWindowSize = 40320
MaxFreeTcbs = 8000
MaxHashTableSize = 16384
MaxNormLookupMemory = 5000000
SackOpts = 1
SynAttackProtect = 1
Tcp1323Opts = 0
TcpLogLevel = 1
TcpMaxDupAttacks = 3
TcpMaxHalfOpen = 100
TcpMaxHalfOpenRetired = 80
TcpRecvSegmentSize = 1440
TcpSendSegmentSize = 1440
TcpTimedWaitDelay = 30
TcpUseRFC1122UrgentPointer = 0
TcpWindowSize = 40320
MaxConnectionsPer1_0Server = 10
MaxConnectionsPerServer = 8
DefaultTimeToLive = 64
DefaultUserTOSSetting = 0
TcpMaxDataRetransmissions = 6
DefaultTOSValue = 240

Registry Tweaks:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters]
"CacheHashTableBucketSize"=dword:00000001
"CacheHashTableSize"=dword:00000180
"MaxCacheEntryTtlLimit"=dword:0000fa00
"MaxSOACacheEntryTtlLimit"=dword:0000012d
"NegativeCacheTime"=dword:00000000
"NegativeSOACacheTime"=dword:00000000
"NetFailureCacheTime"=dword:00000000

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\ServiceProvider
"DnsPriority"=dword:1
"HostsPriority"=dword:1
"LocalPriority"=dword:1
"NetbtPriority"=dword:1

SpeedGuide.net TCP/IP Analyzer

TCP properties for IP = XX.XX.XXX.XX ()
Browser/OS = Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Notes: Read the Analyzer FAQ if the above is not your IP address.

TCP options string = 020405a00103030201010402
MTU = 1480
MTU is optimized for Windows XP PPoE DSL broadband. If not, consider raising MTU to 1500 for optimal throughput.
MSS = 1440
MSS is optimized for Windows XP PPPoE DSL broadband. If not, consider raising MTU to 1500 for maximum throughput.

Default Receive Window (RWIN) = 192000
RWIN Scaling (RFC1323) = 2 bits (scale factor of 4)
Unscaled Receive Window = 48000

For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
506880 (MSS x 44 * scale factor of 8)
253440 (MSS x 44 * scale factor of 4)
126720 (MSS x 44 * scale factor of 2)
63360 (MSS x 44)
bandwidth * delay product (Note this is not a speed test):

Your RcvWindow limits you to: 7680 kbps (960 KBytes/s) @ 200ms
Your RcvWindow limits you to: 3072 kbps (384 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = ON
Time to live left = 55 hops

TTL value is ok.
Timestamps (RFC1323) = OFF
Selective Acknowledgements (RFC2018) = ON
IP type of service field (RFC1349) = 11100000

Precedence (priority) = 000 (routine)
Delay = 0 (normal delay)
Throughput = 0 (normal throughput)
Reliability = 1 (high reliability)
Cost = 1 (low cost)

mnosteele52 · Post by **mnosteele52** » Thu Aug 12, 2004 7:57 am

See what I am referring to? The values in CableNut DefaultReceiveWindow which is an AFD registry parameter is what the TCP/IP Analyzer shows for your RWIN.

earthmofo · Post by **earthmofo** » Thu Aug 12, 2004 11:08 am

Should the value of DefaultReceiveWindow be calculated the same way (download caps in Kbytes * 1024) or should it be the value of RWIN?

mnosteele52 · Post by **mnosteele52** » Thu Aug 12, 2004 11:37 am

earthmofo wrote:Should the value of DefaultReceiveWindow be calculated the same way (download caps in Kbytes * 1024) or should it be the value of RWIN?

Hey Earthmofo, yes use the same values as always. We are still looking into these changes that SP2 makes, for Cox try these:

DefaultReceiveWindow = 512000
DefaultSendWindow = 65536
DisableAddressSharing = 1
InitialLargeBufferCount = 200
InitialMediumBufferCount = 480
InitialSmallBufferCount = 640
LargeBufferSize = 819200
MaxFastTransmit = 64000
MediumBufferSize = 150400
PriorityBoost = 0
SmallBufferSize = 12800
TransmitWorker = 32
FastSendDatagramThreshold = 1024
EnableFastRouteLookup = 1
EnablePMTUDiscovery = 1
IgnorePushBitsOnReceive = 0
GlobalMaxTcpWindowSize = 64240
MaxFreeTcbs = 8000
MaxHashTableSize = 16384
MaxNormLookupMemory = 5000000
SackOpts = 1
SynAttackProtect = 1
Tcp1323Opts = 0
TcpLogLevel = 1
TcpMaxDupAcks = 2
TcpMaxHalfOpen = 100
TcpMaxHalfRetried = 80
TcpRecvSegmentSize = 1460
TcpSendSegmentSize = 1460
TcpTimedWaitDelay = 30
TcpUseRFC1122UrgentPointer = 0
TcpWindowSize = 64240
MaxConnectionsPer1_0Server = 20
MaxConnectionsPerServer = 10
DefaultTTL = 64
DisableUserTOSSetting = 0
TcpMaxDataRetransmissions = 6
DefaultTOSValue = 240

earthmofo · Post by **earthmofo** » Thu Aug 12, 2004 1:15 pm

Thanks Steele! Pretty much the same Cablenut settings that I have. I'm a little more aggressive with my buffers though. With 1 gig of ram I can afford the resource hit

Have you found any articles on the SP2 TCP/IP implementation yet? I could use a little light reading.

mnosteele52 · Post by **mnosteele52** » Thu Aug 12, 2004 1:20 pm

Try reading Microsoft Windows Server 2003 TCP/IP Implementation Details, I believe it's the same as XPSP2 but they haven't released any detailed information on the direct changes in SP2.

Post by **Philip** » Wed Aug 18, 2004 11:29 am

I am sorry to disagree but Cablenut is NOT the only program that can tweak XP SP2 and Win 2k3.

The TCP Optimizer works perfectly fine with them. It's true that it modifies TCP/IP rather than AFD, however it looks into all 3 locations for the correct RWIN value, and it adjusts it accordingly. A simple test on an untweaked Win2k3 server machine can prove it, I'm not going to go into any more details.

The TCP Optimizer is fully capable of tweaking all current Windows OSes.

Cypher · Post by **Cypher** » Wed Aug 18, 2004 1:33 pm

I'm not sure what the deal is but my connection seems to work better untweaked.

This has only been the case since SP2.

Post by **Philip** » Wed Aug 18, 2004 2:38 pm

Cypher_138 wrote:I'm not sure what the deal is but my connection seems to work better untweaked. This has only been the case since SP2.

What program did you use ?

Cypher · Post by **Cypher** » Wed Aug 18, 2004 3:39 pm

Philip wrote:What program did you use ?

I've tried CN than TCP Opt. I initialy had the new firewall enabled but I disabled that since I have a Nexland router. I also turned IPSEC off in XP for the same reason. I'm not sure if it's a conflict with the user.js script I'm using with Firefox or the router. It's only after updating to SP2 that it's faster untweaked for some reason.

dannjr · Post by **dannjr** » Thu Aug 19, 2004 1:57 am

Excuse the Ramblings of a Nut case!

Not sure I want to touch on this Since theres Tons of info flying all over and my eye's are starting to hurt from all the reading since XP SP2 and 2003 Server.

Ive been running 2003 SB Server since its been out.. I didnt even notice the change till "Mno" pointed out XP-SP2

Philip your 100% right the Optimizer works fine to some degree and Cablenut works to some degree.. We could go back and forth on this alll day or have another long discussion on Rwin Sizes And we both "know how" that works

At least we know 2 programs work

We pobably dont have a lot of time to do this.. At least I dont right now...
My personal settings in DSL.... I dont use all the settings in Cablenut.. It just seems to be the thing to do for awhile.. I get 100% on both my DSL connections not 90% anyone that needs to take a ride to see it first hand is more than welcome If the Wife lets you in the door

TcpWindowSize is still a Valid setting.. Its how Winsock has been re-DUN..

In theory as I see it.. Its meant to cover against virri, the way that parts have been re-worked. About 3 files have been seriously reworked for networking Registry settings are still valid for setup.. Not to mention that Iv ran into a SP2 that when the firewall was disabled, wouldnt fully disable till I went into the advance settings. ANd also changed the IP of that system.

Iv also noticed that some Sniffers wont pickup the Options and in some cases wont pickup info at all. So a Giant Thumbs up to SG and Philip on the Analyzer test still being able to work WinPcap.exe wont work under a good amount of the newest updates..

Now as far as some of the claims out there and Iv seen this in a couple of other places that tweaking slowed it up.. ITs because the people tweaking are using mostly defaults from the tweaking programs even if they think they went complicated.. The Optimizer has its defaults just like Cnut.. Theres more to tweaking the final results than just one way. If I told you and I have 6 boxs in Cnut blank in all the machines I tweak you might say why....

I spend allot of time arguing with ISPs getting lines conditioned which isnt cheap for the ISP. I got 200 feet takin out of one of my loops recently.. I also clean all the connections into a home or office and replace them allot of the time. Not to mention that I get a Good POTs splitter or use a single filter till it can be replaced.... AND more

As for this thread.. When the AFD was discovered to be part of the IP detect. It looks like its the thing to look at more. Not weather one is better than the other at this point.

But again, this is the Ramblings of a Nut..

Lets not make it a one is better than the other thing, on either Cnut or SG After all to me its about learning... "But I could be wrong. It could be a size thing"....

Nut AKA dannjr, 499 LB Gorilla

Post by **Philip** » Thu Aug 19, 2004 12:26 pm

Thanks for the post and the good words, dannjr, I fully agree. It should be about colaboration, helping and providing the information to people, I've always tried to be fair in doing so.

The Analyzer disassembles actual packets from the TCP handshake that hit our server to look up the headers, maybe that's why it's one of the few tools out there that are OS independent.

I know that the Cablenut program is a great tool and looks up a number of values other programs don't and I fully realise the amount of time it takes to develop and support. The only thing that bugged me was the claim that it's the only program that can tweak Win2k3 and XP SP2, and I'm glad you took the time to clarify that the Optimizer works as intended as well.

As far as exact values... We're always trying, and we've all agreed one should test and use what works best for them, defaults aren't always the best

Best,

Ph.

HatchbackDrv3r · Post by **HatchbackDrv3r** » Mon Aug 23, 2004 7:00 am

Yeah I like to know where everyone got the new service pack...if they can post a link to where I can download it that would be great. Thank you

mccoffee · Post by **mccoffee** » Mon Aug 23, 2004 7:30 am

http://www.microsoft.com/downloads/details.aspx?FamilyId=049C9DBE-3B8E-4F30-8245-9E368D3CDB5A&displaylang=en

SG Broadband Community

XP SP2 & CableNut

XP SP2 & CableNut

????xp Sp2