BETTER...TCP Optimizer or Cablenut?

[Slumpey]

Just want to know which is better for getting the best connection?

My Broadband provider is ADELPHIA POWERLINK with:

3000 down/ 128 up

(My Operating system is Windows XP Professional)


TCP/IP ANALYZER RESULTS:

TCP options string = 020405b4
MTU = 1500
MTU is fully optimized for broadband.
MSS = 1460
Maximum useful data in each packet = 1460, which equals MSS.

Default Receive Window (RWIN) = 17520
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 17520

RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS:
513920 (MSS x 44 * scale factor of 8)
256960 (MSS x 44 * scale factor of 4)
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)
bandwidth * delay product:

Your RcvWindow limits you to: 700.8 kbps (87.6 KBytes/s) @ 200ms
Your RcvWindow limits you to: 280.32 kbps (35.04 KBytes/s) @ 500ms
Consider increasing your RWIN value to optimize TCP/IP for broadband.
MTU Discovery (RFC1191) = OFF
Time to live left = 117 hops

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



Can you please provide me with the best configurations?

[mccoffee]

Cablenut

[mccoffee]

Please keep everything on one message/site. That and here is ur settings. I'm not trying to be a jerk you don't have to push me my giving me pms/posting messages everywhere. Try the following

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

[Slumpey]

NEW Tcp Analyzer test:

TCP options string = 020405b401010402
MTU = 1500
MTU is fully optimized for broadband.
MSS = 1460
Maximum useful data in each packet = 1460, which equals MSS.

Default Receive Window (RWIN) = 65535
RWIN Scaling (RFC1323) = 0 bits
Unscaled Receive Window = 65535

Note: Under Windows 9x, if you have RWIN set to any other value, and the Analyzer reports 65535 you might need to install the MS Vtcp386 fix.
For optimum performance, consider changing RWIN to a multiple of MSS.
Other values for RWIN that might work well with your current MTU/MSS:
513920 (MSS x 44 * scale factor of 8)
256960 (MSS x 44 * scale factor of 4)
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)
bandwidth * delay product:

Your RcvWindow limits you to: 2621.4 kbps (327.675 KBytes/s) @ 200ms
Your RcvWindow limits you to: 1048.56 kbps (131.07 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = OFF
Time to live left = 53 hops

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

Precedence (priority) = 100 (flash override)
Delay = 1 (low delay)
Throughput = 1 (high throughput)
Reliability = 0 (normal reliability)
Cost = 1 (low cost)


Thanks for the help...CORRECT?
Does my Netgear MR814v2 router have anything to do with these settings?

[mnosteele52]

You need to set Tcp1323Opts to 1.

:cool:

[Slumpey]

After applying new configuration from previous post to TCP Analyzer:

TCP options string = 020405b40103030101010402
MTU = 1500
MTU is fully optimized for broadband.
MSS = 1460
Maximum useful data in each packet = 1460, which equals MSS.

Default Receive Window (RWIN) = 75920
RWIN Scaling (RFC1323) = 1 bits
Unscaled Receive Window = 37960
RWIN is not fully optimized (even though it is a comparatively large number). The unscaled RWIN value is lower than it should be, which can affect your connection to some servers. Also, RWIN being close above 65535 does not justify the header overhead of scaling. You might want to use one of our recommended RWIN values below.

RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS:
513920 (MSS x 44 * scale factor of 8)
256960 (MSS x 44 * scale factor of 4)
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)
bandwidth * delay product:

Your RcvWindow limits you to: 3036.8 kbps (379.6 KBytes/s) @ 200ms
Your RcvWindow limits you to: 1214.72 kbps (151.84 KBytes/s) @ 500ms
MTU Discovery (RFC1191) = OFF
Time to live left = 53 hops

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

Precedence (priority) = 100 (flash override)
Delay = 1 (low delay)
Throughput = 1 (high throughput)
Reliability = 0 (normal reliability)
Cost = 1 (low cost)


My Connection:
Adelphia Powerlink (Cable modem)

Connection Caps:
3000 down / 128 up

Operating System:
Windows XP Pro

[mnosteele52]

The analyzer is just a tool to check your current TCP/IP settings, ignore the rest. Your settings look great, how is your speed?

:cool:

[Philip]

First, let me start by saying both mccofee and mnosteele52 have been around for a long time helping people tweak and we all value their advice.

I do disagree with a couple of statements in this thread and here is why:

Originally posted by mccoffee
Cablenut

Not necessarily... The TCP Optimizer covers the most important settings, while Cablenut goes into more detail and even some questionable settings IMHO. Of course that's just my opinion, and I'm a "related" party. Still, let's have the courtesy of not naming one "better" than the other.


Originally posted by mnosteele52
The analyzer is just a tool to check your current TCP/IP settings, ignore the rest. Your settings look great, how is your speed?

All the recommendations of the Analyzer are there for a reason. I presume your comment is in relation to the following note that I can fully explain and justify: "RWIN is not fully optimized (even though it is a comparatively large number). The unscaled RWIN value is lower than it should be, which can affect your connection to some servers. Also, RWIN being close above 65535 does not justify the header overhead of scaling. You might want to use one of our recommended RWIN values below."

Let's consider the following:
1. TCP Window scaling adds TCP Options to the header of each packets, and it does increase it by a few bytes. Increasing the header at the expense of payload causes a slight performance hit.

2. Large RWIN values help transfer speed, especially when higher latency is involved.

3. RWIN values over 2^16 (65535) are achieved by multiplying the unscaled RWIN by some multiple (RFC1323). Example: 64240 x 2 = 128480, 37960 x 2 = 75920.

4. There are still some servers that don't support RFC1323 and therefore Window scaling.

With all this said... You have to keep the unscaled RWIN value in mind as well, not only the scaled RWIN... A higher unscaled RWIN is better, (especially in the case where you have already determined that the RWIN should be larger than 2^16).

In other words, a RWIN of 128480 (unscaled 64240) yields a higher unscaled RWIN than 75920 (unscaled 37960)... And as the Analyzer reccomendation states, the comparatively small RWIN increase frm 65535 to 75920 does not necessarily justify the overhead of enabling RFC1323 scaling.

[mnosteele52]

Hey Philip how have you been?:D

What I'm refering to is this part:

Your RcvWindow limits you to: 3036.8 kbps (379.6 KBytes/s) @ 200ms
Your RcvWindow limits you to: 1214.72 kbps (151.84 KBytes/s) @ 500ms

The reason being because there is not enough explanation about it and nobody understands it, then they worry when they change their RWIN and see it change.

Noboby seems to understand that your RWIN is based on each individuals caps and latency, there is no "one size fits all" value for your RWIN, everyone MUST find their optimum value in order to fully maximize their bandwidth.

When someone is given the information above in the TCP/IP Analyzer they don't seem to understand it really means nothing to them unless they know what their actual maximum anticipated latency is. They just see the information and think "oh no I'm limited to XXXX kilobits per second" without taking the time to understand what it actually means.

The TCP/IP Analyzer is an invaluable tool but I think there needs to be a little more information on what each section is telling you. I understand it and so do you, but all of the new tweakers get confused by it.

:cool:

[Philip]

You're probably right, there should be more info added to the Analyzer FAQ http://www.speedguide.net/faq_in.php?category=98 or an entire separate article... I'll see what I can do, I'm open to suggestons.

[Andrzej]

:D may I sugest
IMVHO
in sections...there needs to be a little more information... vvvvv.good
...more info added to the Analyzer FAQ... v.good
...entire separate article... will be better
:2cool: but all above will be the best
clear explanations of SG TCP/IP Analyzer are desperately needed

[Slumpey]

First off thanks to everyone so far! I ran a few bandwidth speed tests with the configurations from my previous post (the one with "RWIN is not fully optimized...") ...

D.C.'s Speakeasy Speedtest:

348.1 KB/sec down / 115 kbps down

L.A.'s Speakesy Speedtest:

315.4 KB/sec down / 115 kbps down

ftp://ftp1.optonline.net/pub/test64

310 KB/sec down

[mnosteele52]

Philip something kind of like this older post of mine, but even more details and information would be great.

Originally posted by mnosteele52
Since so many people don't seem to understand what the TCP/IP Anaylyzer is I thought it would be appropriate to post this again.


REMEMBER THIS IS NOT A SPEED TEST OF ANY KIND, IT ONLY SHOWS YOUR CURRENT TCP/IP SETTINGS - THAT IS ALL.

SpeedGuide.net TCP/IP Analyzer
TCP properties for IP = XXXXXXXX - This is your Internet Protocol address
Browser/OS = Mozilla/2.02 - This tells you information about your browser
Note: Read the FAQ if the above is not your IP address.

TCP options string = 020405b401010402

MTU = 1500 - This is your current MTU
MTU is fully optimized for broadband.

MSS = 1460 - This is your current MSS which is always 40 less than your MTU
Maximum useful data in each packet = 1460, which equals MSS.

Default Receive Window (RWIN) = 51100 - This is the most important setting that effects your speed, this is what we tell you to change most often
RWIN Scaling (RFC1323) = 0 bits - This is the Windows Scaling box that shoud be set to 1 if your RWIN is 65535 or higher or set to 0 if it is lower
Unscaled Receive Window = 51100 - This is your RWIN if Windows Scaling was not enabled
RWIN is a multiple of MSS
Other values for RWIN that might work well with your current MTU/MSS: - These are only suggested values that might work for a typical broadband connection
513920 (MSS x 44 * scale factor of 8)
256960 (MSS x 44 * scale factor of 4)
128480 (MSS x 44 * scale factor of 2)
64240 (MSS x 44)

bandwidth * delay product:
Your RcvWindow limits you to: 2044 kbps (255.5 KBytes/s) @ 200ms - IF your latency was 200ms then your current RWIN would limit your speed to this
Your RcvWindow limits you to: 817.6 kbps (102.2 KBytes/s) @ 500ms - IF your latency was 500ms then your current RWIN would limit your speed to this
*This information DOES NOT mean that is your current speed

MTU Discovery (RFC1191) = ON - This is your current setting for PMTUDiscovery, it should always be enabled

Time to live left = 51 hops - This is just your current Time To Live
TTL value is ok.

Timestamps (RFC1323) = OFF - This is your current setting for Timestamps, it should always be disabled

Selective Acknowledgements (RFC2018) = ON - This is your current setting for SackOpts, it should always be on

IP type of service field (RFC1349)= 00000000 - This is you current setting for Type Of Service (TOS) it will differ depending on the settings you use for TOS


:D :cool:

[Andrzej]

:D last version (actual since 08/14/2003) SG Analyzer result page
IMO is good
OK - vvv.easy to read & coppy
OK - links, too short definitions so not easy to follow
OK - links - paches
OK - automatic "comments" (my be exclamation link)

IMO more comments just on result page
probably will be vvvvvv.boring
& explanations of TCP/IP results willbe worse

my be:
1. link to copy result & open new thread on the FORUM
with
option to copy on new post in previous own thread

2. from definitions additional link(s) to appripriate:
forum thread, commments, advice(s)
too many interesting subjects were dispersed eg stuckMTU; TOS ect

3. from definitions or even better from special editorial article link(s) to recomended:
article(s); reading(s); books ect

4. not for shure but
moove (fixed,colosed) great advices
from top SG Tweaking Forum
(vvvvvv.sorry but actualy too many to read in one sesion)
to links on result page as closed thead

or rewrite to articles - but not recomended
IMVHO power of mentined THE advices are:
the AUTHORE(s)
numbers of readings (as a simplet recomendations)
but also easy modyfication by authore (up-to date)
OTOH :) also as I remember, once upon a time,
I cannot memorise details,
a advice tempotary had disapeared (gone) on vacation for refreshment, hopefuly was came back after 2 weeks.

5 field(s) to write down info or check on
about actal: connection, latency, hdw, OS ect

above suggestions
for easiest use & activity on forums
from educational reason
but also remember about easiest use in future advices