Results 1 to 2 of 2

Thread: Why does Analyzer show no Rwin Scaling, but Optimizer does?

  1. #1
    Join Date
    May 2006
    Minneapolis, MN

    Why does Analyzer show no Rwin Scaling, but Optimizer does?

    No real problem. Get 1325 down and 825 up except during Qwest slow down period (11:30AM-11:30PM local).
    Just wondering why Analyzer shows TCP Window 64240 with no Rwin Scaling. Optimizer shows Current settings TCP Window 128480 with Rwin Scaling on.
    That other place shows TCP Window = 128480 ( They test some things not done here).

    My set up.

    Compaq Presario SR2180Nx
    Vista Home Premium
    Intel Pentium D CPU (Dual Core)
    RAM 3062 MB
    Intel PRO/100 VE Network Connection
    connected to Actiontec GT701-WG by Ethernet
    ISP Qwest 1500/1000

    netsh interface tcp global settings are:
    Receive Side Scaling = enabled
    Chimney Offload = enabled
    Autotuning = Disabled
    Congestion Control Provider = ctcp
    ECN Capability = disabled

    Don't ask me why these netsh settings work, but Autotuning = normal only gets about 800kbps and I get about 50-100 kbps more down with ctcp. Have tested all 5 Autotunig settings with Congestion Control at ctcp and off at Nitro.UCSC.

    ---------------------------------------------------------------- TCP Analyzer Results
    Tested on: 01.25.2008 01:52
    IP address:

    TCP options string: 020405b401010402
    MSS: 1460
    MTU: 1500
    TCP Window: 64240 (multiple of MSS)
    RWIN Scaling: 0
    Unscaled RWIN : 64240
    Reccomended RWINs: 64240, 128480, 256960, 513920
    BDP limit (200ms): 2570kbps (321KBytes/s)
    BDP limit (500ms): 1028kbps (128KBytes/s)
    MTU Discovery: ON
    TTL: 49
    Timestamps: OFF
    SACKs: ON
    IP ToS: 00000000 (0)

    Optimizer Current Settings:

    Connection Speed = 1500
    MTU = 1500
    PPoE = Off
    TCP Receive Window = 128480
    MTU Discovery = Yes
    Black Hole Detect = No
    Selective Acks = Yes
    Max Duplicate Acks = 2
    TTL = 64
    TCP Windows Scaling = check
    TCP Time Stamps = no check
    Max Connections Per Server = 5
    Max Connections Per1_0 Server = 5
    Local Priority = 1
    Host Priority = 1
    Dns Priorty = 1
    NETbt Priority = 1
    QoS: Non Best Effort = 0
    TOS: Disable User TOS Setting = 0
    TOS Default Value = 80
    Max Negative Chache Ttl = 0
    Net Failure Chache Time = 0
    Negative SOA Chache Time = 0
    LAN Browser Speedup = Optimized
    LAN Request Buffer = 32768

  2. #2
    Elite Member trogers's Avatar
    Join Date
    Jan 2005
    Bangkok, Thailand
    If you are using Vista auto-tuning, basic unscaled Rwin is set at 256.

    In XP, scaling only kicks in when Rwin is set higher than 65535. You can use TCP Optimizer to set your Rwin to 65536 and the Analyzer will show scaling.
    "Contentment is not the fulfillment of what you want, but is the realisation of how much you already have" - anon

Similar Threads

  1. TCP/IP Analyzer RWIN sometimes wrong.
    By johnhc in forum Broadband Tweaks Help
    Replies: 6
    Last Post: 07-25-07, 02:14 PM
  2. Flight 93 footage thats rarely seen
    By thepieman in forum General Discussion Board
    Replies: 199
    Last Post: 04-08-07, 08:04 PM
  3. bug (or not) with tcp/ip analyser
    By piranha in forum Broadband Tweaks Help
    Replies: 53
    Last Post: 04-19-06, 07:32 AM
  4. TCP Optimizer issue
    By malaac in forum Broadband Tweaks Help
    Replies: 2
    Last Post: 01-12-06, 09:34 AM
  5. nforce4 LAN controller doesnt show up in TCP Optimizer
    By dodgecharger in forum General Broadband Forum
    Replies: 1
    Last Post: 07-04-05, 10:49 PM


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts