Results 1 to 11 of 11

Thread: Significant loss in speed recently

  1. #1
    Junior Member
    Join Date
    Jun 2011
    Posts
    6

    Significant loss in speed recently

    My typical speeds are as follows;
    D: 21mb/s
    U: 0.5mb/s

    But recently they have dropped to 2 & 0.3mb/s respectively.



    Here are my stats from MLab

    --------------------------------------------------------------------------------

    Your system: Windows 7 version 6.1
    Java version: 1.6.0_20 (x86)

    TCP receive window: 1240832 current, 1575424 maximum
    6.98812E-4 packets lost during test
    Round trip time: 120 msec (minimum), 575 msec (maximum), 305.31 msec (average)
    Jitter: 455 msec
    0 seconds spend waiting following a timeout
    TCP time-out counter: 608
    108 selective acknowledgement packets received

    No duplex mismatch condition was detected.
    The test did not detect a cable fault.
    Network congestion may be limiting the connection.
    No network addess translation appliance was detected.

    0.9388% of the time was not spent in a receiver limited or sender limited state.
    84.46000000000001% of the time the connection is limited by the client machine's receive buffer.
    Optimal receive buffer: 1613234176 bytes
    Bottleneck link: Cable/DSL modem
    0 duplicate ACKs set

    --------------------------------------------------------------------------

    WEB100 Kernel Variables:
    Client: localhost/127.0.0.1
    CurMSS: 1382
    X_Rcvbuf: 87380
    X_Sndbuf: 258912
    AckPktsIn: 673
    AckPktsOut: 0
    BytesRetrans: 4146
    CongAvoid: 360
    CongestionOverCount: 0
    CongestionSignals: 1
    CountRTT: 501
    CurCwnd: 77392
    CurRTO: 608
    CurRwinRcvd: 1240832
    CurRwinSent: 5888
    CurSsthresh: 67718
    DSACKDups: 0
    DataBytesIn: 0
    DataBytesOut: 2003026
    DataPktsIn: 0
    DataPktsOut: 1431
    upAcksIn: 169
    ECNEnabled: 0
    FastRetran: 1
    MaxCwnd: 136818
    MaxMSS: 1382
    MaxRTO: 811
    MaxRTT: 575
    MaxRwinRcvd: 1575424
    MaxRwinSent: 5888
    MaxSsthresh: 67718
    MinMSS: 1382
    MinRTO: 479
    MinRTT: 120
    MinRwinRcvd: 66304
    MinRwinSent: 5840
    NagleEnabled: 1
    OtherReductions: 1
    PktsIn: 673
    PktsOut: 1431
    PktsRetrans: 3
    RcvWinScale: 7
    SACKEnabled: 3
    SACKsRcvd: 108
    SendStall: 0
    SlowStart: 139
    SampleRTT: 428
    SmoothedRTT: 358
    SndWinScale: 8
    SndLimTimeRwin: 66002
    SndLimTimeCwnd: 9569598
    SndLimTimeSender: 558358
    SndLimTransRwin: 1
    SndLimTransCwnd: 13
    SndLimTransSender: 12
    SndLimBytesRwin: 2804
    SndLimBytesCwnd: 1959996
    SndLimBytesSender: 40226
    SubsequentTimeouts: 0
    SumRTT: 152960
    Timeouts: 0
    TimestampsEnabled: 0
    WinScaleRcvd: 8
    WinScaleSent: 7
    DupAcksOut: 0
    StartTimeUsec: 878458
    Duration: 10195052
    c2sData: 2
    c2sAck: 2
    s2cData: 8
    s2cAck: 3
    half_duplex: 0
    link: 0
    congestion: 1
    bad_cable: 0
    mismatch: 0
    spd: 1.57
    bw: 1.31
    loss: 0.000698812
    avgrtt: 305.31
    waitsec: 0.00
    timesec: 10.00
    order: 0.2511
    rwintime: 0.0065
    sendtime: 0.0548
    cwndtime: 0.9388
    rwin: 12.0195
    swin: 1.9753
    cwin: 1.0438
    rttsec: 0.305309
    Sndbuf: 258912
    aspd: 0.00000
    CWND-Limited: 51.92
    minCWNDpeak: 11056
    maxCWNDpeak: 136818
    CWNDpeaks: 1

    The theoretical network limit is 1.31 Mbps
    The NDT server has a 126.0 KByte buffer which limits the throughput to 6.46 Mbps
    Your PC/Workstation has a 1538.0 KByte buffer which limits the throughput to 39.36 Mbps
    The network based flow control limits the throughput to 3.41 Mbps


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


    This has been driving me nuts. Please help!

  2. #2
    Regular Member Road Runner's Avatar
    Join Date
    Jan 2003
    Location
    Brooklyn, NY
    Posts
    314
    Who is your provider? And what speeds are you paying for?
    I can assume that 21mb/s / 0.5mb/s is 21 Mbps / 500 Kbps, correct?
    Judging from the information you've posted.. you have some high latency on your line.

    Do you have a router in the mix; and if so, have you directly connected to the modem to eliminate the router as your issue?

    Open the Command Prompt application; type in command: tracert google.com; then copy / paste your results here. The tracert will show where your pings spike high at, and whether it's within your control, your ISP, or the actual "Internet Cloud" (peering networks).

  3. #3
    Junior Member
    Join Date
    Jun 2011
    Posts
    6
    My provider is Rogers. I'm paying for 10mbps download and 500kbps upload. Was about to upgrade but doesn't make sense until I can get this fixed.

    Your assumptions on the speeds are correct. What are you seeing that is calling out latency?

    A router is in the mix.. oddly enough when I connect directly to the modem I get 96% packet loss and can't even run the tests. Figuring it was a modem issue I exchanged it. Had good speeds with the new one (as posted) for a few days and then they dropped again??? Was it unusual to see speeds that much higher than the bandwidth you are paying for?

    Here are the results for the test.

    --------------------------------------------------------------------------------------------------------------------------------

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\Corey>tracert google.com

    Tracing route to google.com [74.125.91.106]
    over a maximum of 30 hops:

    1 8 ms 10 ms 17 ms 192.168.1.1
    2 23 ms 27 ms 22 ms 10.45.208.1
    3 24 ms 31 ms 25 ms 67.231.220.169
    4 31 ms 21 ms 20 ms 69.63.248.181
    5 147 ms 30 ms 20 ms 69.63.251.142
    6 24 ms 21 ms 115 ms 72.14.216.14
    7 26 ms 20 ms 29 ms 216.239.47.114
    8 60 ms 99 ms 104 ms 216.239.46.170
    9 134 ms 101 ms 208 ms 72.14.239.93
    10 122 ms 202 ms 204 ms 209.85.248.75
    11 136 ms 100 ms 101 ms 209.85.254.237
    12 123 ms 103 ms 97 ms 209.85.240.57
    13 107 ms 123 ms 61 ms qy-in-f106.1e100.net [74.125.91.106]

    Trace complete.

    -------------------------------------------------------------------------------------------------------------------------------------

    I will connect directly to the modem tomorrow morning and rerun the test. I will post those results then.

    Thanks Road Runner!

  4. #4
    Regular Member Road Runner's Avatar
    Join Date
    Jan 2003
    Location
    Brooklyn, NY
    Posts
    314
    Ah, Rogers- an Canadian ISP.

    As for high latency, I saw it the beginning of your MLab stats:

    Round trip time: 120 msec (minimum), 575 msec (maximum), 305.31 msec (average)
    Jitter: 455 msec


    Well whatever is going on, it seems to be within your home for the most part, according to your tracert at least. The latency to your first hop - your router - is pretty, as it should be hovering between 1-3ms; the same with Roger's edge router (the CMTS) at hop #2 - 10.45.208.1 -- it should show no more than 3-6ms, at most.

    I suspect packet loss of some sort, but I think you should run your tests directly connected to the modem to rule out the router.

    How are your cable modem signal levels? Most modems have an internal page at http://192.168.100.1 - if you can access that then try snooping around for the signal levels page which shouldn't be hard to identify. For signals you need to post the downstream, upstream, and signal-to-noise ratio (SNR) numbers. If your signal levels are poor, in which we'll find out, then it can definitely cause packet loss resulting in speed degradation.

    Use this same CMD application again; type in command: ping -n 30 10.45.208.1
    This will ping your CMTS (local node / edge router) 30 times and report back any packet loss in transmissions.

    Remember when you're running tests to make sure there's no background apps utilizing your bandwidth.

  5. #5
    Junior Member
    Join Date
    Jun 2011
    Posts
    6
    Sorry for the delay!

    Okay - so here is the update. When I connect directly to the modem and enter tracert google.com I get a message saying tracert google.com cannot be found or located or something. I also have zero access to the internet when connect directly to the modem. I reset everything (modem, router) and still could only get access to the internet when connected to my router.

    However, this "reboot" seemed to have restored my speeds?? (I had tried this before with zero success).

    Concerns: When i run - command: ping -n 30 10.45.208.1 - I get 100% loss. The stats below, although run within minutes of each other, seem to return conflicting data which has left me very confused. Help appreciated!

    Below are some of the stats I ran today.

    --------------
    SIGNAL
    --------------
    Downstream Value
    Frequency 615000000 Hz
    Signal To Noise Ratio 38.6 dB
    Power Level -2.3 dBmV
    The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading

    Upstream Value
    Channel ID 2
    Frequency 25296000 Hz
    Power 51.7 dBmV

    ---------------
    Speedtest.net
    ---------------
    Ping 13ms
    Download 13.2mbps
    Upload 0.51mbps

    ----------------
    Pingtest.net
    ----------------
    Packet Loss 0%
    Ping 29ms
    Jitter 11ms
    Line Quality A

    ----------------
    NDT http://nitro.ucsc.edu/
    ----------------
    WEB100 Enabled Statistics:
    Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
    checking for firewalls . . . . . . . . . . . . . . . . . . . Done
    running 10s outbound test (client-to-server [C2S]) . . . . . 492.0kb/s
    running 10s inbound test (server-to-client [S2C]) . . . . . . 4.23Mb/s

    ------ Client System Details ------
    OS data: Name = Windows 7, Architecture = x86, Version = 6.1
    Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_20

    ------ 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 = 172.28 msec; the Packet size = 1382 Bytes; and
    There were 13 packets retransmitted, 270 duplicate acks received, and 187 SACK blocks received
    The connection was idle 0 seconds (0%) of the time
    S2C throughput test: Packet queuing detected: 0.00%
    This connection is receiver limited 7.24% of the time.
    This connection is network limited 92.42% 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

    Server 'nitro.ucsc.edu' is not behind a firewall. [Connection to the ephemeral port was successful]
    Client is probably behind a firewall. [Connection to the ephemeral port failed]
    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

    WEB100 Kernel Variables:
    Client: localhost/127.0.0.1
    CurMSS: 1382
    X_Rcvbuf: 103424
    X_Sndbuf: 103424
    AckPktsIn: 940
    AckPktsOut: 0
    BytesRetrans: 17966
    CongAvoid: 328
    CongestionOverCount: 0
    CongestionSignals: 1
    CountRTT: 657
    CurCwnd: 135436
    CurRTO: 340
    CurRwinRcvd: 261196
    CurRwinSent: 16304
    CurSsthresh: 129908
    DSACKDups: 0
    DataBytesIn: 0
    DataBytesOut: 5268184
    DataPktsIn: 0
    DataPktsOut: 3812
    DupAcksIn: 270
    ECNEnabled: 0
    FastRetran: 1
    MaxCwnd: 261198
    MaxMSS: 1382
    MaxRTO: 580
    MaxRTT: 400
    MaxRwinRcvd: 261196
    MaxRwinSent: 16304
    MaxSsthresh: 129908
    MinMSS: 1382
    MinRTO: 340
    MinRTT: 100
    MinRwinRcvd: 4146
    MinRwinSent: 16304
    NagleEnabled: 1
    OtherReductions: 2
    PktsIn: 940
    PktsOut: 3812
    PktsRetrans: 13
    RcvWinScale: 7
    SACKEnabled: 3
    SACKsRcvd: 187
    SendStall: 0
    SlowStart: 273
    SampleRTT: 110
    SmoothedRTT: 110
    SndWinScale: 2
    SndLimTimeRwin: 727675
    SndLimTimeCwnd: 9288153
    SndLimTimeSender: 34185
    SndLimTransRwin: 2
    SndLimTransCwnd: 3
    SndLimTransSender: 1
    SndLimBytesRwin: 449150
    SndLimBytesCwnd: 4819034
    SndLimBytesSender: 0
    SubsequentTimeouts: 0
    SumRTT: 113190
    Timeouts: 0
    TimestampsEnabled: 0
    WinScaleRcvd: 2
    WinScaleSent: 7
    DupAcksOut: 0
    StartTimeUsec: 485417
    Duration: 10052087
    c2sData: 2
    c2sAck: 2
    s2cData: 8
    s2cAck: 3
    half_duplex: 0
    link: 0
    congestion: 0
    bad_cable: 0
    mismatch: 0
    spd: 4.19
    bw: 3.78
    loss: 0.000262329
    avgrtt: 172.28
    waitsec: 0.00
    timesec: 10.00
    order: 0.2872
    rwintime: 0.0724
    sendtime: 0.0034
    cwndtime: 0.9242
    rwin: 1.9928
    swin: 0.7891
    cwin: 1.9928
    rttsec: 0.172283
    Sndbuf: 103424
    aspd: 0.00000
    CWND-Limited: 109.96
    minCWNDpeak: 17966
    maxCWNDpeak: 261198
    CWNDpeaks: 2

    The theoretical network limit is 3.78 Mbps
    The NDT server has a 50.0 KByte buffer which limits the throughput to 4.58 Mbps
    Your PC/Workstation has a 255.0 KByte buffer which limits the throughput to 11.56 Mbps
    The network based flow control limits the throughput to 11.56 Mbps

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

    -------------------------------------------------
    NDT http://www.measurementlabe.net/run-ndt
    -------------------------------------------------
    Your system: Windows 7 version 6.1
    Java version: 1.6.0_20 (x86)

    TCP receive window: 261196 current, 261196 maximum
    1.1212E-4 packets lost during test
    Round trip time: 62 msec (minimum), 243 msec (maximum), 121.34 msec (average)
    Jitter: 181 msec
    0 seconds spend waiting following a timeout
    TCP time-out counter: 304
    187 selective acknowledgement packets received

    No duplex mismatch condition was detected.
    The test did not detect a cable fault.
    No network congestion was detected.
    No network addess translation appliance was detected.

    0.6637% of the time was not spent in a receiver limited or sender limited state.
    33.300000000000004% of the time the connection is limited by the client machine's receive buffer.
    Optimal receive buffer: 267464704 bytes
    Bottleneck link: Cable/DSL modem
    0 duplicate ACKs set

    WEB100 Kernel Variables:
    Client: localhost/127.0.0.1
    CurMSS: 1382
    X_Rcvbuf: 87380
    X_Sndbuf: 679644
    AckPktsIn: 1798
    AckPktsOut: 0
    BytesRetrans: 37314
    CongAvoid: 584
    CongestionOverCount: 0
    CongestionSignals: 1
    CountRTT: 1445
    CurCwnd: 138200
    CurRTO: 304
    CurRwinRcvd: 261196
    CurRwinSent: 5888
    CurSsthresh: 129908
    DSACKDups: 0
    DataBytesIn: 0
    DataBytesOut: 12499694
    DataPktsIn: 0
    DataPktsOut: 8919
    DupAcksIn: 325
    ECNEnabled: 0
    FastRetran: 1
    MaxCwnd: 261198
    MaxMSS: 1382
    MaxRTO: 478
    MaxRTT: 243
    MaxRwinRcvd: 261196
    MaxRwinSent: 5888
    MaxSsthresh: 129908
    MinMSS: 1382
    MinRTO: 271
    MinRTT: 62
    MinRwinRcvd: 16584
    MinRwinSent: 5840
    NagleEnabled: 1
    OtherReductions: 2
    PktsIn: 1798
    PktsOut: 8919
    PktsRetrans: 27
    RcvWinScale: 7
    SACKEnabled: 3
    SACKsRcvd: 187
    SendStall: 0
    SlowStart: 271
    SampleRTT: 104
    SmoothedRTT: 101
    SndWinScale: 2
    SndLimTimeRwin: 3375700
    SndLimTimeCwnd: 6728378
    SndLimTimeSender: 33277
    SndLimTransRwin: 4
    SndLimTransCwnd: 21
    SndLimTransSender: 17
    SndLimBytesRwin: 5401906
    SndLimBytesCwnd: 6836152
    SndLimBytesSender: 261636
    SubsequentTimeouts: 0
    SumRTT: 175333
    Timeouts: 0
    TimestampsEnabled: 0
    WinScaleRcvd: 2
    WinScaleSent: 7
    DupAcksOut: 0
    StartTimeUsec: 860643
    Duration: 10139044
    c2sData: 2
    c2sAck: 2
    s2cData: 8
    s2cAck: 4
    half_duplex: 0
    link: 0
    congestion: 0
    bad_cable: 0
    mismatch: 0
    spd: 9.86
    bw: 8.21
    loss: 0.000112120
    avgrtt: 121.34
    waitsec: 0.00
    timesec: 10.00
    order: 0.1808
    rwintime: 0.3330
    sendtime: 0.0033
    cwndtime: 0.6637
    rwin: 1.9928
    swin: 5.1853
    cwin: 1.9928
    rttsec: 0.121338
    Sndbuf: 679644
    aspd: 0.00000
    CWND-Limited: 93.28
    minCWNDpeak: 22112
    maxCWNDpeak: 261198
    CWNDpeaks: 2

    The theoretical network limit is 8.21 Mbps
    The NDT server has a 331.0 KByte buffer which limits the throughput to 42.73 Mbps
    Your PC/Workstation has a 255.0 KByte buffer which limits the throughput to 16.42 Mbps
    The network based flow control limits the throughput to 16.42 Mbps

    Client Data reports link is 'T1', Client Acks report link is 'T1'
    Server Data reports link is 'OC-48', Server Acks report link is 'T3'

    -------------------------------
    command: tracert google.ca
    command: tracert google.com
    -------------------------------
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    tracert google.ca

    Tracing route to google.ca [74.125.93.106]
    over a maximum of 30 hops:

    1 1 ms 1 ms 1 ms 192.168.1.1
    2 12 ms 8 ms 9 ms 10.45.208.1
    3 12 ms 9 ms 9 ms 67.231.220.169
    4 12 ms 10 ms 11 ms 69.63.250.21
    5 12 ms 10 ms 9 ms 69.63.250.93
    6 13 ms 11 ms 11 ms 72.14.216.14
    7 15 ms 23 ms 12 ms 209.85.255.232
    8 128 ms 101 ms 101 ms 209.85.255.235
    9 127 ms 59 ms 41 ms 209.85.249.11
    10 68 ms 101 ms 101 ms 209.85.248.73
    11 128 ms 111 ms 91 ms 209.85.254.233
    12 107 ms 101 ms 101 ms 216.239.47.34
    13 96 ms 133 ms 111 ms qw-in-f106.1e100.net [74.125.93.106]

    Trace complete.
    tracert google.com

    Tracing route to google.com [74.125.93.106]
    over a maximum of 30 hops:

    1 1 ms 1 ms 1 ms 192.168.1.1
    2 23 ms 10 ms 25 ms 10.45.208.1
    3 11 ms 11 ms 13 ms 67.231.220.169
    4 11 ms 11 ms 9 ms 69.63.250.21
    5 12 ms 11 ms 14 ms 69.63.250.93
    6 12 ms 11 ms 11 ms 72.14.216.14
    7 14 ms 20 ms 15 ms 209.85.255.232
    8 140 ms 102 ms 101 ms 209.85.255.235
    9 128 ms 101 ms 34 ms 209.85.249.11
    10 129 ms 101 ms 101 ms 209.85.248.73
    11 120 ms 203 ms 68 ms 209.85.254.235
    12 136 ms 111 ms 84 ms 216.239.47.34
    13 85 ms 135 ms 76 ms qw-in-f106.1e100.net [74.125.93.106]

    Trace complete.

    ----------------------------------
    command: ping -n 30 10.45.208.1
    ----------------------------------
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    ping -n 30 10.45.208.1

    Pinging 10.45.208.1 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.

    Ping statistics for 10.45.208.1:
    Packets: Sent = 30, Received = 0, Lost = 30 (100% loss),

  6. #6
    Regular Member Road Runner's Avatar
    Join Date
    Jan 2003
    Location
    Brooklyn, NY
    Posts
    314
    I'm still bothered with the latency between you and 10.45.208.1, but cannot pinpoint since it seems it's not responding to ICMP requests in your ping stats.

    Also, anytime you switch network devices from the modem it needs to be rebooted- this is because it remembers the last MAC address it synced with, which - in your case - was the router. This goes for all network devices - routers, hubs, etc. - a reboot is always needed so it can "forget" the last device and "learn" the new MAC address.

    Have you reconnected your router back the mix?

    Try pinging your modem using the command: ping -t 30 192.168.100.1
    Post your results here. However if there's no packet loss and your latency is about 1-3ms, then I'd say it's probably with Rogers and you should contact them immediately regarding your speed degradation next time as there's no signs as it's within your control.

  7. #7
    Junior Member
    Join Date
    Jun 2011
    Posts
    6
    Here are the results from the command: ping-n 30 192.168.100.1

    No packet loss, however the latecy is still a little high. I posted two tests that were run back to back as there is the occasional spike in latency... not quite sure what would cause that. Thoughts?

    Yes, my router is back in the mix.

    ---------------------------------------------------------------------
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    ping -n 30 192.168.100.1

    Pinging 192.168.100.1 with 32 bytes of data:
    Reply from 192.168.100.1: bytes=32 time=19ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=20ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=43ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=64ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=87ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=7ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=7ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=8ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63

    Ping statistics for 192.168.100.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 87ms, Average = 12ms

    --------------------------------------------------
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    ping -n 30 192.168.100.1

    Pinging 192.168.100.1 with 32 bytes of data:
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=7ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=5ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=8ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=7ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=5ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=10ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=9ms TTL=63
    Reply from 192.168.100.1: bytes=32 time=6ms TTL=63

    Ping statistics for 192.168.100.1:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 10ms, Average = 6ms

  8. #8
    Elite Member trogers's Avatar
    Join Date
    Jan 2005
    Location
    Bangkok, Thailand
    Posts
    12,323
    Quote Originally Posted by CoreyP View Post
    Tracing route to google.com [74.125.91.106]
    over a maximum of 30 hops:

    1 8 ms 10 ms 17 ms 192.168.1.1
    Normal ping times at the router in hop 1 should be

    1 <1ms <1ms <1ms when the comp is connected to the router with ethernet cable

    and

    1 1ms 1ms 1ms when connected through wireless.

    My guess is that there is interference over the wireless medium, eg. from cordless phone operating in the 2.4 GHz band, or power saving lamp, etc. If not, the wireless adapter card may need a driver update.
    "Contentment is not the fulfillment of what you want, but is the realisation of how much you already have" - anon

  9. #9
    Junior Member
    Join Date
    Jun 2011
    Posts
    6
    My cordless is Dect 6.0 so that should not cause any interference... i think!?!

    I updated the wireless adapter card driver and still no improvements in speed... in fact it's slowly started to slow again and is now back down to speeds of 4.6mbps download and 0.51mbps upload with a ping of 21ms according to speedtest.net.

  10. #10
    Elite Member trogers's Avatar
    Join Date
    Jan 2005
    Location
    Bangkok, Thailand
    Posts
    12,323
    Quote Originally Posted by CoreyP View Post
    My cordless is Dect 6.0 so that should not cause any interference... i think!?!

    I updated the wireless adapter card driver and still no improvements in speed... in fact it's slowly started to slow again and is now back down to speeds of 4.6mbps download and 0.51mbps upload with a ping of 21ms according to speedtest.net.
    Check the speed through an ethernet connection to isolate the problem as one of wireless.
    "Contentment is not the fulfillment of what you want, but is the realisation of how much you already have" - anon

  11. #11
    Junior Member
    Join Date
    Jun 2011
    Posts
    6
    Okay... so here is the update. Since nothing seemed to be working, I unistalled my network adapter card (Note: I did NOT delete the driver files). I then re-installed and speeds are back to what they should be, both through direct connect and router. Don't know why this worked, but it did.

    BIG thank you to Road Runner and Trogers for the help. Much appreciated to the both of you!

    Cheers,
    Corey

Similar Threads

  1. pls help dsl loss speed
    By Lambo in forum General Broadband Forum
    Replies: 0
    Last Post: 04-06-11, 01:45 AM
  2. Speed loss
    By commast in forum Wireless Networks & Routers
    Replies: 5
    Last Post: 03-15-07, 06:31 PM
  3. Recently Reformatted, Wanna Speed Things Up Again
    By TraJiK in forum Broadband Tweaks Help
    Replies: 10
    Last Post: 05-24-04, 06:09 PM
  4. speed loss
    By TyranT in forum General Broadband Forum
    Replies: 5
    Last Post: 07-17-03, 03:08 PM
  5. Replies: 18
    Last Post: 02-10-03, 07:02 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
  •