Results 1 to 20 of 20

Thread: The tweaks are not working for me

  1. #1
    Junior Member
    Join Date
    Jan 2007
    Posts
    24

    Unhappy The tweaks are not working for me

    These are my settings but the values are different in the registry. I changed but still these values come. My MTU is 1492 but here it says it is 1400 and RWIN is 130560 but here it is something different. What should I do?

    SpeedGuide.net TCP Analyzer Results
    Tested on: 01.12.2007 11:48
    IP address: 59.92.xxx.xxx

    TCP options string: 0204055001010402
    MSS: 1360
    MTU: 1400
    TCP Window: 17680 (multiple of MSS)
    RWIN Scaling: 0
    Unscaled RWIN : 17680
    Reccomended RWINs: 65280, 130560, 261120, 522240
    BDP limit (200ms): 707kbps (88KBytes/s)
    BDP limit (500ms): 283kbps (35KBytes/s)
    MTU Discovery: ON
    TTL: 48
    Timestamps: OFF
    SACKs: ON
    IP ToS: 00000000 (0)

  2. #2
    Elite Member trogers's Avatar
    Join Date
    Jan 2005
    Location
    Bangkok, Thailand
    Posts
    12,323
    What speed are you supposed to get? Are you using a router?

    Do this test and post the reports under the 'Statistics' and 'More Details' buttons:

    http://miranda.ctd.anl.gov:7123/

  3. #3
    Junior Member
    Join Date
    Jan 2007
    Posts
    24
    TCP/Web100 Network Diagnostic Tool v5.3.4e
    click START to begin
    Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
    running 10s outbound test (client to server) . . . . . 272.68Kb/s
    running 10s inbound test (server to client) . . . . . . 414.11kb/s
    Your PC is connected to a Cable/DSL modem
    Information: The receive buffer should be 122445.0 Kbytes to maximize throughput

    click START to re-test

  4. #4
    Junior Member
    Join Date
    Jan 2007
    Posts
    24
    Test Results:

    TCP/Web100 Network Diagnostic Tool v5.3.4e
    click START to begin
    Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
    running 10s outbound test (client to server) . . . . . 272.68Kb/s
    running 10s inbound test (server to client) . . . . . . 414.11kb/s
    Your PC is connected to a Cable/DSL modem
    Information: The receive buffer should be 122445.0 Kbytes to maximize throughput

    click START to re-test

    Statistics:

    WEB100 Enabled Statistics:
    Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
    running 10s outbound test (client to server) . . . . . 272.68Kb/s
    running 10s inbound test (server to client) . . . . . . 414.11kb/s

    ------ Client System Details ------
    OS data: Name = Windows XP, Architecture = x86, Version = 5.1
    Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_10

    ------ Web100 Detailed Analysis ------
    Cable modem/DSL/T1 link found.
    Link set to Full Duplex mode
    No network congestion discovered.
    Good network cable(s) found
    Normal duplex operation found.

    Web100 reports the Round trip time = 326.52 msec; the Packet size = 1360 Bytes; and
    No packet loss was observed.
    This connection is receiver limited 89.97% of the time.
    Increasing the the client's receive buffer (17.0 KB) will improve performance
    This connection is network limited 10.0% of the time.

    Web100 reports TCP negotiated the optional Performance Settings to:
    RFC 2018 Selective Acknowledgment: ON
    RFC 896 Nagle Algorithm: ON
    RFC 3168 Explicit Congestion Notification: OFF
    RFC 1323 Time Stamping: OFF
    RFC 1323 Window Scaling: OFF
    Information: Network Middlebox is modifying MSS variable
    Server IP addresses are preserved End-to-End
    Information: Network Address Translation (NAT) box is modifying the Client's IP address
    Server says [59.92.183.191] but Client says [192.168.xx.xx]

    More Details:

    WEB100 Kernel Variables:
    Client: localhost/127.0.0.1
    AckPktsIn: 368
    AckPktsOut: 0
    BytesRetrans: 0
    CongAvoid: 0
    CongestionOverCount: 0
    CongestionSignals: 0
    CountRTT: 368
    CurCwnd: 19040
    CurMSS: 1360
    CurRTO: 550
    CurRwinRcvd: 17680
    CurRwinSent: 5840
    CurSsthresh: 2147483647
    DSACKDups: 0
    DataBytesIn: 0
    DataBytesOut: 518160
    DataPktsIn: 0
    DataPktsOut: 381
    DupAcksIn: 0
    ECNEnabled: 0
    FastRetran: 0
    MaxCwnd: 19040
    MaxMSS: 1360
    MaxRTO: 960
    MaxRTT: 450
    MaxRwinRcvd: 17680
    MaxRwinSent: 5840
    MaxSsthresh: 0
    MinMSS: 1360
    MinRTO: 540
    MinRTT: 310
    MinRwinRcvd: 17680
    MinRwinSent: 5840
    NagleEnabled: 1
    OtherReductions: 0
    PktsIn: 368
    PktsOut: 381
    PktsRetrans: 0
    X_Rcvbuf: 107520
    RcvWinScale: 7
    SACKEnabled: 3
    SACKsRcvd: 0
    SendStall: 0
    SlowStart: 12
    SampleRTT: 320
    SmoothedRTT: 320
    X_Sndbuf: 107520
    SndWinScale: 0
    SndLimTimeRwin: 9037511
    SndLimTimeCwnd: 1004357
    SndLimTimeSender: 3041
    SndLimTransRwin: 1
    SndLimTransCwnd: 1
    SndLimTransSender: 1
    SndLimBytesRwin: 485520
    SndLimBytesCwnd: 32640
    SndLimBytesSender: 0
    SubsequentTimeouts: 0
    SumRTT: 120160
    Timeouts: 0
    TimestampsEnabled: 0
    WinScaleRcvd: 0
    WinScaleSent: 7
    DupAcksOut: 0
    StartTimeUsec: 449422
    Duration: 10047083
    c2sData: 2
    c2sAck: 2
    s2cData: 2
    s2cAck: 2
    half_duplex: 0
    link: 100
    congestion: 0
    bad_cable: 0
    mismatch: 0
    spd: 0.00
    bw: 31.78
    loss: 0.000001000
    avgrtt: 326.52
    waitsec: 0.00
    timesec: 10.00
    order: 0.0000
    rwintime: 0.8997
    sendtime: 0.0003
    cwndtime: 0.1000
    rwin: 0.1349
    swin: 0.8203
    cwin: 0.1453
    rttsec: 0.326522
    Sndbuf: 107520
    aspd: 0.00000

    Checking for mismatch on uplink
    (speed > 50 [0>50], (xmitspeed < 5) [0.27<5]
    (rwintime > .9) [0.89>.9], (loss < .01) [1.0E<.01]
    Checking for excessive errors condition
    (loss/sec > .15) [1.0E>.15], (cwndtime > .6) [0.1>.6],
    (loss < .01) [1.0E<.01], (MaxSsthresh > 0) [0>0]
    Checking for 10 Mbps link
    (speed < 9.5) [0<9.5], (speed > 3.0) [0>3.0]
    (xmitspeed < 9.5) [0.27<9.5] (loss < .01) [1.0E<.01], (mylink > 0) [3.0>0]
    Checking for Wireless link
    (sendtime = 0) [3.0E=0], (speed < 5) [0<5]
    (Estimate > 50 [31.78>50], (Rwintime > 90) [0.89>.90]
    (RwinTrans/CwndTrans = 1) [1/1=1], (mylink > 0) [3.0>0]
    Checking for DSL/Cable Modem link
    (speed < 2) [0<2], (SndLimTransSender = 0) [1=0]
    (SendTime = 0) [3.0E-4=0], (mylink > 0) [3.0>0]
    Checking for half-duplex condition
    (rwintime > .95) [0.89>.95], (RwinTrans/sec > 30) [0.1>30],
    (SenderTrans/sec > 30) [0.1>30], OR (mylink <= 10) [3.0<=10]
    Checking for congestion
    (cwndtime > .02) [0.1>.02], (mismatch = 0) [0=0]
    (MaxSsthresh > 0) [0>0]

    estimate = 31.78 based on packet size = 10Kbits, RTT = 326.52msec, and loss = 1.0E-6
    The theoretical network limit is 31.78 Mbps
    The NDT server has a 105.0 KByte buffer which limits the throughput to 2.51 Mbps
    Your PC/Workstation has a 17.0 KByte buffer which limits the throughput to 0.41 Mbps
    The network based flow control limits the throughput to 0.44 Mbps

    Client Data reports link is 'T1', Client Acks report link is 'T1'
    Server Data reports link is 'T1', Server Acks report link is 'T1'
    Last edited by djdansays; 01-12-07 at 11:46 PM.

  5. #5
    Junior Member
    Join Date
    Jan 2007
    Posts
    24
    Should I try Dr. TCP? Is it safe? I am sorry I am not used to it.

  6. #6
    Elite Member trogers's Avatar
    Join Date
    Jan 2005
    Location
    Bangkok, Thailand
    Posts
    12,323
    Quote Originally Posted by djdansays View Post
    Test Results:

    TCP/Web100 Network Diagnostic Tool v5.3.4e
    click START to begin
    Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
    running 10s outbound test (client to server) . . . . . 272.68Kb/s
    running 10s inbound test (server to client) . . . . . . 414.11kb/s
    Your PC is connected to a Cable/DSL modem
    Information: The receive buffer should be 122445.0 Kbytes to maximize throughput

    click START to re-test

    Statistics:

    WEB100 Enabled Statistics:
    Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
    running 10s outbound test (client to server) . . . . . 272.68Kb/s
    running 10s inbound test (server to client) . . . . . . 414.11kb/s

    ------ Client System Details ------
    OS data: Name = Windows XP, Architecture = x86, Version = 5.1
    Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_10

    ------ Web100 Detailed Analysis ------
    Cable modem/DSL/T1 link found.
    Link set to Full Duplex mode
    No network congestion discovered.
    Good network cable(s) found
    Normal duplex operation found.

    Web100 reports the Round trip time = 326.52 msec; the Packet size = 1360 Bytes; and
    No packet loss was observed.
    This connection is receiver limited 89.97% of the time.
    Increasing the the client's receive buffer (17.0 KB) will improve performance
    This connection is network limited 10.0% of the time.

    Web100 reports TCP negotiated the optional Performance Settings to:
    RFC 2018 Selective Acknowledgment: ON
    RFC 896 Nagle Algorithm: ON
    RFC 3168 Explicit Congestion Notification: OFF
    RFC 1323 Time Stamping: OFF
    RFC 1323 Window Scaling: OFF
    Information: Network Middlebox is modifying MSS variable
    Server IP addresses are preserved End-to-End
    Information: Network Address Translation (NAT) box is modifying the Client's IP address
    Server says [59.92.xxx.xxx] but Client says [192.168.1.100]

    More Details:

    WEB100 Kernel Variables:
    Client: localhost/127.0.0.1
    AckPktsIn: 368
    AckPktsOut: 0
    BytesRetrans: 0
    CongAvoid: 0
    CongestionOverCount: 0
    CongestionSignals: 0
    CountRTT: 368
    CurCwnd: 19040
    CurMSS: 1360
    CurRTO: 550
    CurRwinRcvd: 17680
    CurRwinSent: 5840
    CurSsthresh: 2147483647
    DSACKDups: 0
    DataBytesIn: 0
    DataBytesOut: 518160
    DataPktsIn: 0
    DataPktsOut: 381
    DupAcksIn: 0
    ECNEnabled: 0
    FastRetran: 0
    MaxCwnd: 19040
    MaxMSS: 1360
    MaxRTO: 960
    MaxRTT: 450
    MaxRwinRcvd: 17680
    MaxRwinSent: 5840
    MaxSsthresh: 0
    MinMSS: 1360
    MinRTO: 540
    MinRTT: 310
    MinRwinRcvd: 17680
    MinRwinSent: 5840
    NagleEnabled: 1
    OtherReductions: 0
    PktsIn: 368
    PktsOut: 381
    PktsRetrans: 0
    X_Rcvbuf: 107520
    RcvWinScale: 7
    SACKEnabled: 3
    SACKsRcvd: 0
    SendStall: 0
    SlowStart: 12
    SampleRTT: 320
    SmoothedRTT: 320
    X_Sndbuf: 107520
    SndWinScale: 0
    SndLimTimeRwin: 9037511
    SndLimTimeCwnd: 1004357
    SndLimTimeSender: 3041
    SndLimTransRwin: 1
    SndLimTransCwnd: 1
    SndLimTransSender: 1
    SndLimBytesRwin: 485520
    SndLimBytesCwnd: 32640
    SndLimBytesSender: 0
    SubsequentTimeouts: 0
    SumRTT: 120160
    Timeouts: 0
    TimestampsEnabled: 0
    WinScaleRcvd: 0
    WinScaleSent: 7
    DupAcksOut: 0
    StartTimeUsec: 449422
    Duration: 10047083
    c2sData: 2
    c2sAck: 2
    s2cData: 2
    s2cAck: 2
    half_duplex: 0
    link: 100
    congestion: 0
    bad_cable: 0
    mismatch: 0
    spd: 0.00
    bw: 31.78
    loss: 0.000001000
    avgrtt: 326.52
    waitsec: 0.00
    timesec: 10.00
    order: 0.0000
    rwintime: 0.8997
    sendtime: 0.0003
    cwndtime: 0.1000
    rwin: 0.1349
    swin: 0.8203
    cwin: 0.1453
    rttsec: 0.326522
    Sndbuf: 107520
    aspd: 0.00000

    Checking for mismatch on uplink
    (speed > 50 [0>50], (xmitspeed < 5) [0.27<5]
    (rwintime > .9) [0.89>.9], (loss < .01) [1.0E<.01]
    Checking for excessive errors condition
    (loss/sec > .15) [1.0E>.15], (cwndtime > .6) [0.1>.6],
    (loss < .01) [1.0E<.01], (MaxSsthresh > 0) [0>0]
    Checking for 10 Mbps link
    (speed < 9.5) [0<9.5], (speed > 3.0) [0>3.0]
    (xmitspeed < 9.5) [0.27<9.5] (loss < .01) [1.0E<.01], (mylink > 0) [3.0>0]
    Checking for Wireless link
    (sendtime = 0) [3.0E=0], (speed < 5) [0<5]
    (Estimate > 50 [31.78>50], (Rwintime > 90) [0.89>.90]
    (RwinTrans/CwndTrans = 1) [1/1=1], (mylink > 0) [3.0>0]
    Checking for DSL/Cable Modem link
    (speed < 2) [0<2], (SndLimTransSender = 0) [1=0]
    (SendTime = 0) [3.0E-4=0], (mylink > 0) [3.0>0]
    Checking for half-duplex condition
    (rwintime > .95) [0.89>.95], (RwinTrans/sec > 30) [0.1>30],
    (SenderTrans/sec > 30) [0.1>30], OR (mylink <= 10) [3.0<=10]
    Checking for congestion
    (cwndtime > .02) [0.1>.02], (mismatch = 0) [0=0]
    (MaxSsthresh > 0) [0>0]

    estimate = 31.78 based on packet size = 10Kbits, RTT = 326.52msec, and loss = 1.0E-6
    The theoretical network limit is 31.78 Mbps
    The NDT server has a 105.0 KByte buffer which limits the throughput to 2.51 Mbps
    Your PC/Workstation has a 17.0 KByte buffer which limits the throughput to 0.41 Mbps
    The network based flow control limits the throughput to 0.44 Mbps

    Client Data reports link is 'T1', Client Acks report link is 'T1'
    Server Data reports link is 'T1', Server Acks report link is 'T1'
    The TCP Optimizer is better than Dr.TCP.

    The above test reports shows some unusual results.

    Your Send RWIN is also lower than usual. Your MSS is limited by either your router or your ISP.

    Use the TCP Optimizer to reset your registry to Windows default setting. Click 'File' and choose the option. Reboot comp to take effect and post a new TCP Analyzer result.

  7. #7
    Junior Member
    Join Date
    Jan 2007
    Posts
    24
    Thanks a lot. Atleast my download speed has gone up to 742kbps.
    Well I tried TCP optimizer and it worked but not fully. My MTU and MSS are still the same. My recieve buffer is small which they say is limiting the speed. Mine is a 2Mbps connection. Could you tell me how to change the Receive buffer? My Receive Window is 65535 so that part is good. I don't know why the Window scaling and Timestamps are off though I turned it ON. These are my test results:

    TCP/Web100 Network Diagnostic Tool v5.3.4e
    click START to begin
    Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
    running 10s outbound test (client to server) . . . . . 240.96Kb/s
    running 10s inbound test (server to client) . . . . . . 742.33kb/s
    Your PC is connected to a Cable/DSL modem
    Information: The receive buffer should be 239778.75 Kbytes to maximize throughput

    click START to re-test

    Statistics:
    WEB100 Enabled Statistics:
    Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
    running 10s outbound test (client to server) . . . . . 240.96Kb/s
    running 10s inbound test (server to client) . . . . . . 742.33kb/s

    ------ Client System Details ------
    OS data: Name = Windows XP, Architecture = x86, Version = 5.1
    Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_10

    ------ Web100 Detailed Analysis ------
    Cable modem/DSL/T1 link found.
    Link set to Full Duplex mode
    No network congestion discovered.
    Good network cable(s) found
    Normal duplex operation found.

    Web100 reports the Round trip time = 639.41 msec; the Packet size = 1360 Bytes; and
    No packet loss - but packets arrived out-of-order 0.32% of the time
    This connection is receiver limited 79.61% of the time.
    Increasing the the client's receive buffer (63.0 KB) will improve performance
    This connection is network limited 20.36% of the time.

    Web100 reports TCP negotiated the optional Performance Settings to:
    RFC 2018 Selective Acknowledgment: ON
    RFC 896 Nagle Algorithm: ON
    RFC 3168 Explicit Congestion Notification: OFF
    RFC 1323 Time Stamping: OFF
    RFC 1323 Window Scaling: OFF
    Information: Network Middlebox is modifying MSS variable
    Server IP addresses are preserved End-to-End
    Information: Network Address Translation (NAT) box is modifying the Client's IP address
    Server says [59.92.183.191] but Client says [192.168.xx.x]

    More Details:

    WEB100 Kernel Variables:
    Client: localhost/127.0.0.1
    AckPktsIn: 631
    AckPktsOut: 0
    BytesRetrans: 0
    CongAvoid: 0
    CongestionOverCount: 0
    CongestionSignals: 0
    CountRTT: 629
    CurCwnd: 66640
    CurMSS: 1360
    CurRTO: 970
    CurRwinRcvd: 65535
    CurRwinSent: 5840
    CurSsthresh: 2147483647
    DSACKDups: 0
    DataBytesIn: 0
    DataBytesOut: 923440
    DataPktsIn: 0
    DataPktsOut: 679
    DupAcksIn: 2
    ECNEnabled: 0
    FastRetran: 0
    MaxCwnd: 66640
    MaxMSS: 1360
    MaxRTO: 1750
    MaxRTT: 980
    MaxRwinRcvd: 65535
    MaxRwinSent: 5840
    MaxSsthresh: 0
    MinMSS: 1360
    MinRTO: 770
    MinRTT: 350
    MinRwinRcvd: 62815
    MinRwinSent: 5840
    NagleEnabled: 1
    OtherReductions: 0
    PktsIn: 631
    PktsOut: 679
    PktsRetrans: 0
    X_Rcvbuf: 107520
    RcvWinScale: 7
    SACKEnabled: 3
    SACKsRcvd: 0
    SendStall: 0
    SlowStart: 47
    SampleRTT: 520
    SmoothedRTT: 540
    X_Sndbuf: 107520
    SndWinScale: 0
    SndLimTimeRwin: 8055570
    SndLimTimeCwnd: 2060123
    SndLimTimeSender: 3015
    SndLimTransRwin: 1
    SndLimTransCwnd: 1
    SndLimTransSender: 1
    SndLimBytesRwin: 795600
    SndLimBytesCwnd: 127840
    SndLimBytesSender: 0
    SubsequentTimeouts: 0
    SumRTT: 402190
    Timeouts: 0
    TimestampsEnabled: 0
    WinScaleRcvd: 0
    WinScaleSent: 7
    DupAcksOut: 0
    StartTimeUsec: 583715
    Duration: 10120617
    c2sData: 2
    c2sAck: 2
    s2cData: 3
    s2cAck: 3
    half_duplex: 0
    link: 100
    congestion: 0
    bad_cable: 0
    mismatch: 0
    spd: 0.00
    bw: 16.23
    loss: 0.000001000
    avgrtt: 639.41
    waitsec: 0.00
    timesec: 10.00
    order: 0.0032
    rwintime: 0.7961
    sendtime: 0.0003
    cwndtime: 0.2036
    rwin: 0.5000
    swin: 0.8203
    cwin: 0.5084
    rttsec: 0.639412
    Sndbuf: 107520
    aspd: 0.00000

    Checking for mismatch on uplink
    (speed > 50 [0>50], (xmitspeed < 5) [0.24<5]
    (rwintime > .9) [0.79>.9], (loss < .01) [1.0E<.01]
    Checking for excessive errors condition
    (loss/sec > .15) [1.0E>.15], (cwndtime > .6) [0.20>.6],
    (loss < .01) [1.0E<.01], (MaxSsthresh > 0) [0>0]
    Checking for 10 Mbps link
    (speed < 9.5) [0<9.5], (speed > 3.0) [0>3.0]
    (xmitspeed < 9.5) [0.24<9.5] (loss < .01) [1.0E<.01], (mylink > 0) [3.0>0]
    Checking for Wireless link
    (sendtime = 0) [3.0E=0], (speed < 5) [0<5]
    (Estimate > 50 [16.23>50], (Rwintime > 90) [0.79>.90]
    (RwinTrans/CwndTrans = 1) [1/1=1], (mylink > 0) [3.0>0]
    Checking for DSL/Cable Modem link
    (speed < 2) [0<2], (SndLimTransSender = 0) [1=0]
    (SendTime = 0) [3.0E-4=0], (mylink > 0) [3.0>0]
    Checking for half-duplex condition
    (rwintime > .95) [0.79>.95], (RwinTrans/sec > 30) [0.1>30],
    (SenderTrans/sec > 30) [0.1>30], OR (mylink <= 10) [3.0<=10]
    Checking for congestion
    (cwndtime > .02) [0.20>.02], (mismatch = 0) [0=0]
    (MaxSsthresh > 0) [0>0]

    estimate = 16.23 based on packet size = 10Kbits, RTT = 639.41msec, and loss = 1.0E-6
    The theoretical network limit is 16.23 Mbps
    The NDT server has a 105.0 KByte buffer which limits the throughput to 1.28 Mbps
    Your PC/Workstation has a 63.0 KByte buffer which limits the throughput to 0.78 Mbps
    The network based flow control limits the throughput to 0.79 Mbps

    Client Data reports link is 'T1', Client Acks report link is 'T1'
    Server Data reports link is 'Ethernet', Server Acks report link is 'Ethernet'

  8. #8
    Elite Member trogers's Avatar
    Join Date
    Jan 2005
    Location
    Bangkok, Thailand
    Posts
    12,323
    Window Scaling will be turned on only when RWIN > 65535. In Windows default setting RWIN is only 65535. Timestamp should be turned off to reduce packet overheads.

    Use the following with TCP Optimizer:

    General Settings tab:
    Custom settings - check
    Modify All Network Adapters - check
    network adapter selection - your NIC
    MTU - 1400
    TTL - 64
    TCP Receive Window - 130560
    MTU Discovery - Yes
    Black Hole Detect - No
    Selective Acks - Yes
    Max Duplicate ACKs - 2
    TCP 1323 Options:
    Windows Scaling - checked
    Timestamps - uncheck

    Advanced Settings tab:
    Max Connections per Server - 10
    Max Connections per 1.0 Server - 20
    LocalPriority - 1
    Host Priority - 1
    DNSPriority - 1
    NetbtPriority - 1
    Lan Browsing speedup - optimized
    QoS: NonBestEffortLimit - 0
    ToS: DisableUserTOSSetting - 0
    ToS: DefaultTOSValue - 136
    MaxNegativeCacheTtl - 0
    NetFailureCacheTime - 0
    NegativeSOACache Time - 0
    LAN Request Buffer Size - 32768
    Then select "Apply Changes" and reboot to take effect

    Test your speed at this link using the recommended test server:

    www.speedtest.net

  9. #9
    Junior Member
    Join Date
    Jan 2007
    Posts
    24
    These are my new values. But what ever I do MTU is not changing. DSL reports say that some software of router is limiting my MTU. I checked my Router but it has 1492 as MTU but after the test it says it is just 1400. Which software could do this? What do they mean when they say that my receive buffer should be 709383.75 Kbytes? And mine is 272Kbytes. How do I change them?
    Test results:
    TCP/Web100 Network Diagnostic Tool v5.3.4e
    click START to begin
    Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
    running 10s outbound test (client to server) . . . . . 276.28Kb/s
    running 10s inbound test (server to client) . . . . . . 830.12kb/s
    Your PC is connected to a Cable/DSL modem
    Information: The receive buffer should be 709383.75 Kbytes to maximize throughput

    click START to re-test

    Statistics:
    WEB100 Enabled Statistics:
    Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
    running 10s outbound test (client to server) . . . . . 276.28Kb/s
    running 10s inbound test (server to client) . . . . . . 830.12kb/s

    ------ Client System Details ------
    OS data: Name = Windows XP, Architecture = x86, Version = 5.1
    Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_10

    ------ Web100 Detailed Analysis ------
    Cable modem/DSL/T1 link found.
    Link set to Full Duplex mode
    No network congestion discovered.
    Good network cable(s) found
    Normal duplex operation found.

    Web100 reports the Round trip time = 1891.69 msec; the Packet size = 1360 Bytes; and
    No packet loss - but packets arrived out-of-order 0.18% of the time
    This connection is receiver limited 43.23% of the time.
    Increasing the the client's receive buffer (272.0 KB) will improve performance
    This connection is network limited 56.74% of the time.

    Web100 reports TCP negotiated the optional Performance Settings to:
    RFC 2018 Selective Acknowledgment: ON
    RFC 896 Nagle Algorithm: ON
    RFC 3168 Explicit Congestion Notification: OFF
    RFC 1323 Time Stamping: OFF
    RFC 1323 Window Scaling: ON
    Information: Network Middlebox is modifying MSS variable
    Server IP addresses are preserved End-to-End
    Information: Network Address Translation (NAT) box is modifying the Client's IP address
    Server says [59.92.193.215] but Client says [192.168.xx.xx]

    More details:
    WEB100 Kernel Variables:
    Client: localhost/127.0.0.1
    AckPktsIn: 551
    AckPktsOut: 0
    BytesRetrans: 0
    CongAvoid: 0
    CongestionOverCount: 0
    CongestionSignals: 0
    CountRTT: 551
    CurCwnd: 278800
    CurMSS: 1360
    CurRTO: 3290
    CurRwinRcvd: 278784
    CurRwinSent: 5840
    CurSsthresh: 2147483647
    DSACKDups: 0
    DataBytesIn: 0
    DataBytesOut: 1028160
    DataPktsIn: 0
    DataPktsOut: 756
    DupAcksIn: 1
    ECNEnabled: 0
    FastRetran: 0
    MaxCwnd: 278800
    MaxMSS: 1360
    MaxRTO: 3400
    MaxRTT: 2620
    MaxRwinRcvd: 278784
    MaxRwinSent: 5840
    MaxSsthresh: 0
    MinMSS: 1360
    MinRTO: 1060
    MinRTT: 460
    MinRwinRcvd: 34848
    MinRwinSent: 5840
    NagleEnabled: 1
    OtherReductions: 0
    PktsIn: 553
    PktsOut: 757
    PktsRetrans: 0
    X_Rcvbuf: 107520
    RcvWinScale: 7
    SACKEnabled: 3
    SACKsRcvd: 0
    SendStall: 0
    SlowStart: 203
    SampleRTT: 2460
    SmoothedRTT: 2500
    X_Sndbuf: 107520
    SndWinScale: 3
    SndLimTimeRwin: 4328600
    SndLimTimeCwnd: 5682088
    SndLimTimeSender: 3396
    SndLimTransRwin: 1
    SndLimTransCwnd: 1
    SndLimTransSender: 1
    SndLimBytesRwin: 477360
    SndLimBytesCwnd: 552160
    SndLimBytesSender: 0
    SubsequentTimeouts: 0
    SumRTT: 1042320
    Timeouts: 0
    TimestampsEnabled: 0
    WinScaleRcvd: 3
    WinScaleSent: 7
    DupAcksOut: 0
    StartTimeUsec: 735275
    Duration: 10013198
    c2sData: 2
    c2sAck: 2
    s2cData: 3
    s2cAck: 3
    half_duplex: 0
    link: 100
    congestion: 0
    bad_cable: 0
    mismatch: 0
    spd: 0.00
    bw: 5.49
    loss: 0.000001000
    avgrtt: 1891.69
    waitsec: 0.00
    timesec: 10.00
    order: 0.0018
    rwintime: 0.4323
    sendtime: 0.0003
    cwndtime: 0.5674
    rwin: 2.1270
    swin: 64.0000
    cwin: 2.1271
    rttsec: 1.891688
    Sndbuf: 8388608
    aspd: 0.00000

    Checking for mismatch on uplink
    (speed > 50 [0>50], (xmitspeed < 5) [0.27<5]
    (rwintime > .9) [0.43>.9], (loss < .01) [1.0E<.01]
    Checking for excessive errors condition
    (loss/sec > .15) [1.0E>.15], (cwndtime > .6) [0.56>.6],
    (loss < .01) [1.0E<.01], (MaxSsthresh > 0) [0>0]
    Checking for 10 Mbps link
    (speed < 9.5) [0<9.5], (speed > 3.0) [0>3.0]
    (xmitspeed < 9.5) [0.27<9.5] (loss < .01) [1.0E<.01], (mylink > 0) [3.0>0]
    Checking for Wireless link
    (sendtime = 0) [3.0E=0], (speed < 5) [0<5]
    (Estimate > 50 [5.49>50], (Rwintime > 90) [0.43>.90]
    (RwinTrans/CwndTrans = 1) [1/1=1], (mylink > 0) [3.0>0]
    Checking for DSL/Cable Modem link
    (speed < 2) [0<2], (SndLimTransSender = 0) [1=0]
    (SendTime = 0) [3.0E-4=0], (mylink > 0) [3.0>0]
    Checking for half-duplex condition
    (rwintime > .95) [0.43>.95], (RwinTrans/sec > 30) [0.1>30],
    (SenderTrans/sec > 30) [0.1>30], OR (mylink <= 10) [3.0<=10]
    Checking for congestion
    (cwndtime > .02) [0.56>.02], (mismatch = 0) [0=0]
    (MaxSsthresh > 0) [0>0]

    estimate = 5.49 based on packet size = 10Kbits, RTT = 1891.69msec, and loss = 1.0E-6
    The theoretical network limit is 5.49 Mbps
    The NDT server has a 8192.0 KByte buffer which limits the throughput to 33.83 Mbps
    Your PC/Workstation has a 272.0 KByte buffer which limits the throughput to 1.12 Mbps
    The network based flow control limits the throughput to 1.12 Mbps

    Client Data reports link is 'T1', Client Acks report link is 'T1'
    Server Data reports link is 'Ethernet', Server Acks report link is 'Ethernet'

  10. #10
    Elite Member trogers's Avatar
    Join Date
    Jan 2005
    Location
    Bangkok, Thailand
    Posts
    12,323
    Your signal round trip time is too high at 1892ms. Increasing buffer will only increase the time much more.

    Do a tracert to www.yahoo.com and post. We can check if there is problem with your signal quality.

    Your ISP may be limiting MTU to 1400.

  11. #11
    Junior Member
    Join Date
    Jan 2007
    Posts
    24
    I don't think it is the ISP who is limiting because one of my friend who has the same connection (BSNL-2Mbps) has an MTU of 1456 and another person in this forum has 1480. But my friend also had the problem of Network Middlebox modifying the MSS variable.
    Increasing the buffer certainly increased the round trip time but also increased the download speed. So how should I make a trade-off between them.
    Anyway these are the results

    Date Inc. URL Average time [sec] Action
    2007.1.15 17:29 Internal parts are included www.yahoo.com 1.0 sec RE execute this measurement Details
    2007.1.15 17:35 Internal parts are included www.yahoo.com 2.0 sec RE execute this measurement Details
    2007.1.15 17:36 Internal parts are included www.yahoo.com 1.0 sec RE execute this measurement Details
    2007.1.15 17:36 Internal parts are included www.yahoo.com 1.0 sec RE execute this measurement Details

  12. #12
    Elite Member trogers's Avatar
    Join Date
    Jan 2005
    Location
    Bangkok, Thailand
    Posts
    12,323
    High round trip time is usually cause by problem in signal device or a bad connection line. A tracert may show where high ping times are occurring.

    To do a tracert, click 'Start' and then 'Run'. Type "cmd" into the box and click 'ok'.

    A DOS black screen will appear. Type after the C:\>

    tracert www.yahoo.com

    and press enter key

    When test is completed, move mouse cusor to the DOS black screen, click right and choose 'select all'.

    Move mouse cursor to the Quick Reply box of this forum, click right and 'paste'.

  13. #13
    Junior Member
    Join Date
    Jan 2007
    Posts
    24
    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\Danny John>cd\

    C:\>tracert www.yahoo.com

    Tracing route to www.yahoo-ht2.akadns.net [69.147.114.210]
    over a maximum of 30 hops:

    1 * * * Request timed out.
    2 36 ms 34 ms 55 ms 59.92.128.1
    3 * * * Request timed out.
    4 63 ms 62 ms 76 ms 218.248.255.9
    5 61 ms 61 ms 62 ms 218.248.255.22
    6 320 ms 310 ms 321 ms 202.54.185.250
    7 544 ms 551 ms 552 ms 59.163.16.146.static.vsnl.net.in [59.163.16.146]

    8 586 ms 589 ms 582 ms 219.64.229.1.mpls-vpn-ny.static.vsnl.net.in [219
    .64.229.1]
    9 564 ms 575 ms 544 ms ge-0-0-9.p815.pat2.dce.yahoo.com [216.115.98.109
    ]
    10 * * * Request timed out.
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 * * * Request timed out.
    20 * * * Request timed out.
    21 * * * Request timed out.
    22 * * * Request timed out.
    23 * * * Request timed out.
    24 * * * Request timed out.
    25 * * * Request timed out.
    26 * * * Request timed out.
    27 * * * Request timed out.
    28 * * * Request timed out.
    29 * * * Request timed out.
    30 * * * Request timed out.

    Trace complete.

    C:\>tracert www.yahoo.com

    Tracing route to www.yahoo-ht2.akadns.net [69.147.114.210]
    over a maximum of 30 hops:

    1 * * * Request timed out.
    2 35 ms 35 ms 69 ms 59.92.128.1
    3 * * * Request timed out.
    4 63 ms 66 ms 62 ms 218.248.255.9
    5 67 ms 62 ms 62 ms 218.248.255.22
    6 248 ms 238 ms 237 ms 202.54.185.250
    7 476 ms 481 ms 474 ms 59.163.16.146.static.vsnl.net.in [59.163.16.146]

    8 474 ms 477 ms 520 ms 219.64.229.1.mpls-vpn-ny.static.vsnl.net.in [219
    .64.229.1]
    9 454 ms 490 ms 466 ms ge-2-0-9.p559.pat2.dce.yahoo.com [216.115.97.19]

    10 * * * Request timed out.
    11 * * * Request timed out.
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * * * Request timed out.
    15 * * * Request timed out.
    16 * * * Request timed out.
    17 * * * Request timed out.
    18 * * * Request timed out.
    19 * * * Request timed out.
    20 * * * Request timed out.
    21 * * * Request timed out.
    22 * * * Request timed out.
    23 * * * Request timed out.
    24 * * * Request timed out.
    25 * * * Request timed out.
    26 * * * Request timed out.
    27 * * * Request timed out.
    28 * * * Request timed out.
    29 * * * Request timed out.
    30 * * * Request timed out.

    Trace complete.

    C:\>

  14. #14
    Elite Member trogers's Avatar
    Join Date
    Jan 2005
    Location
    Bangkok, Thailand
    Posts
    12,323
    Quote Originally Posted by djdansays View Post
    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\Danny John>cd\

    C:\>tracert www.yahoo.com

    Tracing route to www.yahoo-ht2.akadns.net [69.147.114.210]
    over a maximum of 30 hops:

    1 * * * Request timed out.
    2 36 ms 34 ms 55 ms 59.92.xxx.xxx
    3 * * * Request timed out.
    4 63 ms 62 ms 76 ms 218.248.255.9
    5 61 ms 61 ms 62 ms 218.248.255.22

    Tracing route to www.yahoo-ht2.akadns.net [69.147.114.210]
    over a maximum of 30 hops:

    1 * * * Request timed out.
    2 35 ms 35 ms 69 ms 59.92.128.1
    3 * * * Request timed out.
    4 63 ms 66 ms 62 ms 218.248.255.9
    5 67 ms 62 ms 62 ms 218.248.255.22
    Are you using a router?

  15. #15
    Junior Member
    Join Date
    Jan 2007
    Posts
    24
    Yes I am using a modem/router.
    It is Quidway WA1003A series from Huawei.

  16. #16
    Elite Member trogers's Avatar
    Join Date
    Jan 2005
    Location
    Bangkok, Thailand
    Posts
    12,323
    Quote Originally Posted by djdansays View Post
    Yes I am using a modem/router.
    It is Quidway WA1003A series from Huawei.
    This is a wireless router. I suspect signal interference is causing the timed out in hop 1. Connect your comp to the router by a cable and do your tracert to confirm. If tracert shws no interference, do some speedtests.

  17. #17
    Junior Member
    Join Date
    Jan 2007
    Posts
    24
    Well I am sorry I could not connect to the router using a cable because when I tried doing that it said that it is not windows XP tested and do I want to take a risk and install it. Then when I took the risk the installation failed. So I can never connect to the net using USB or Ethernet. Only Wireless works fine.

  18. #18
    Elite Member trogers's Avatar
    Join Date
    Jan 2005
    Location
    Bangkok, Thailand
    Posts
    12,323
    Quote Originally Posted by djdansays View Post
    Well I am sorry I could not connect to the router using a cable because when I tried doing that it said that it is not windows XP tested and do I want to take a risk and install it. Then when I took the risk the installation failed. So I can never connect to the net using USB or Ethernet. Only Wireless works fine.
    Does that mean that you access web admin of your router only through wireless and make changes?

  19. #19
    Junior Member
    Join Date
    Jan 2007
    Posts
    24
    Yes I only use wireless.
    I have ZoneAlarm as my Firewall. Is this the one which is limiting my MTU to 1400?

  20. #20
    Junior Member
    Join Date
    Jan 2007
    Posts
    24
    Thanks a lot Trogers. I got rid of the problem. The TCP/IP setting was not set properly. I just followed the instructions in the the topic titled "Tips on Tweaking-Please read". Finally I got out of it. I hope all those who cannot change their MTU values could be facing this problem. So I suggest all of you to go through it and make necessary changes. Thanks again Trogers and Speedguide.net
    Thanks a lot

Similar Threads

  1. Tweaks Causing Timeouts on Netgear FWG114P, Win2K, WinXP - What's Happening?
    By singularity2006 in forum Broadband Tweaks Help
    Replies: 14
    Last Post: 03-10-09, 02:58 AM
  2. Only one computer working with router
    By Gandyisgod in forum Wireless Networks & Routers
    Replies: 4
    Last Post: 01-10-06, 02:57 PM
  3. Audigy 2 ZS w/headset not working
    By Chacotako in forum Hardware & Overclocking
    Replies: 10
    Last Post: 04-04-05, 01:15 PM
  4. Need Help, New To Cable Tweaks.
    By Jaeden09 in forum Broadband Tweaks Help
    Replies: 8
    Last Post: 02-22-05, 06:04 AM
  5. Comcast network not working with WCG200
    By BigDaddyPhysics in forum General Broadband Forum
    Replies: 2
    Last Post: 01-28-05, 10:25 AM

Bookmarks

Posting Permissions

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