Results 1 to 8 of 8

Thread: 2900ms ping....

  1. #1
    Junior Member
    Join Date
    Feb 2008
    Posts
    4

    2900ms ping....

    Hi, on the 4mb virgin connection. Used to getting 30ms up to 100ms, but now getting a 2900ms ping when i test on speednet servers. I've noticed web pages take longer to load, online gaming is lagging etc.

    I've tried safe mode XP so it's not any background programs. I've done virus, spyware checks as well. Reinstalled network drivers, reset modem and router. Renewed dhcp etc im running out of ideas!

    I think it's the modems fault being old SB4100 i think it may be dying. Heres some info from the status page.. feel free to ask for more info on my system.

    Frequency 331000000 Hz Locked
    Signal to Noise Ratio 36 dB
    Power Level 4 dBmV
    Channel ID 3
    Frequency 34000000 Hz Ranged
    Power Level 39 dBmV

    I don't want to call tech support (25p a min!) so if any of you can help me out i'd appreciate it.

    Thanks

  2. #2
    Second Most EVIL YARDofSTUF's Avatar
    Join Date
    Nov 2000
    Location
    USA
    Posts
    69,982
    Well calling your ISP may be the best option in the end.

    Post a tcp analyzer report and do a couple tracerts to like yahoo and msn or something.

  3. #3
    Junior Member
    Join Date
    Feb 2008
    Posts
    4
    TCP options string = 020405b40103030201010402
    MTU = 1500
    MTU is fully optimized for broadband.
    MSS = 1460
    Maximum useful data in each packet = 1460, which equals MSS.
    Default TCP Receive Window (RWIN) = 256960
    RWIN Scaling (RFC1323) = 2 bits (scale factor of 4)
    Unscaled TCP Receive Window = 64240

    RWIN is a multiple of MSS
    Other RWIN values 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) <-- current value
    128480 (MSS x 44 * scale factor of 2)
    64240 (MSS x 44)
    bandwidth * delay product (Note this is not a speed test):

    Your TCP Window limits you to: 10278 kbps (1285 KBytes/s) @ 200ms
    Your TCP Window limits you to: 4111 kbps (514 KBytes/s) @ 500ms
    MTU Discovery (RFC1191) = ON
    Time to live left = 46 hops
    TTL value is ok.
    Timestamps (RFC1323) = OFF
    Selective Acknowledgements (RFC2018) = ON
    IP type of service field (RFC1349) = 00000000 (0)

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\Adam>tracert google.com

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

    1 <1 ms <1 ms <1 ms 192.168.0.1
    2 * 9 ms 10 ms 10.39.128.1
    3 12 ms 31 ms 29 ms 80.195.192.67
    4 43 ms 167 ms 24 ms pc-62-30-243-49-bn.blueyonder.co.uk [62.30.243.4
    9]
    5 12 ms 12 ms 27 ms bre-bb-a-ge-200-0.inet.ntl.com [195.182.178.109]

    6 16 ms 15 ms 15 ms 212.43.162.218
    7 15 ms 17 ms 14 ms tele-ic-1-as0-0.inet.ntl.com [62.253.184.2]
    8 30 ms 26 ms 23 ms 212.250.14.66
    9 77 ms 24 ms 30 ms 209.85.252.40
    10 68 ms 116 ms 131 ms 64.233.175.213
    11 122 ms 108 ms 118 ms 209.85.252.166
    12 109 ms 169 ms 114 ms 72.14.238.138
    13 124 ms 128 ms 138 ms 216.239.47.1
    14 132 ms 127 ms 143 ms 216.239.49.222
    15 119 ms * * jc-in-f99.google.com [64.233.187.99]
    16 117 ms * 139 ms jc-in-f99.google.com [64.233.187.99]

    Trace complete.

    C:\Documents and Settings\Adam>tracert msn.com

    Tracing route to msn.com [207.68.172.246]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.0.1
    2 * 11 ms 9 ms 10.39.128.1
    3 27 ms 11 ms 12 ms 80.195.192.67
    4 12 ms 11 ms 12 ms pc-62-30-243-49-bn.blueyonder.co.uk [62.30.243.4
    9]
    5 20 ms 23 ms 23 ms bre-bb-a-ge-200-0.inet.ntl.com [195.182.178.109]

    6 13 ms 15 ms 16 ms 212.43.162.218
    7 * 32 ms 19 ms tele-ic-1-as0-0.inet.ntl.com [62.253.184.2]
    8 15 ms 16 ms 18 ms 193.159.225.237
    9 170 ms 190 ms 192 ms 217.239.40.62
    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.

    -----


    Ping doesn't look too bad but.......http://www.speedtest.net/result/234029932.png

  4. #4
    Packet loss eh? try
    ping 192.168.100.1 -n 100

    and see what shows up there.


    if 0% then try

    ping 10.39.128.1 -n 100

    This will test your connection to your modem, then to the first hop on your cable plant.

  5. #5
    Elite Member trogers's Avatar
    Join Date
    Jan 2005
    Location
    Bangkok, Thailand
    Posts
    12,323
    Tracerts show packet losses at the modem in hop 2. You may be right that your modem is getting old.
    "Contentment is not the fulfillment of what you want, but is the realisation of how much you already have" - anon

  6. #6
    Junior Member
    Join Date
    Feb 2008
    Posts
    4
    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\Adam>ping 192.168.100.1 -n 100

    Pinging 192.168.100.1 with 32 bytes of data:

    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=5ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=2ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=3ms TTL=63
    Request timed out.
    Reply from 192.168.100.1: bytes=32 time=9ms TTL=63

    Ping statistics for 192.168.100.1:
    Packets: Sent = 100, Received = 50, Lost = 50 (50% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 9ms, Average = 3ms

    C:\Documents and Settings\Adam>ping 10.39.128.1 -n 100

    Pinging 10.39.128.1 with 32 bytes of data:

    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 10.39.128.1: Destination net unreachable.
    Request timed out.
    Reply from 10.39.128.1: Destination net unreachable.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 10.39.128.1: Destination net unreachable.
    Request timed out.
    Reply from 10.39.128.1: Destination net unreachable.
    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.
    Reply from 10.39.128.1: Destination net unreachable.
    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.
    Reply from 10.39.128.1: Destination net unreachable.
    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.
    Reply from 10.39.128.1: Destination net unreachable.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 10.39.128.1: Destination net unreachable.
    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.
    Reply from 10.39.128.1: Destination net unreachable.
    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.39.128.1:
    Packets: Sent = 100, Received = 9, Lost = 91 (91% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms


  7. #7
    Regular Member 100 010 00's Avatar
    Join Date
    Jun 2006
    Location
    Between the legs
    Posts
    196
    electric interference
    There is no patch for stupidity

  8. #8
    Quote Originally Posted by atmlord View Post
    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    C:\Documents and Settings\Adam>ping 192.168.100.1 -n 100

    Pinging 192.168.100.1 with 32 bytes of data:



    Ping statistics for 192.168.100.1:
    Packets: Sent = 100, Received = 50, Lost = 50 (50% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 9ms, Average = 3ms

    C:\Documents and Settings\Adam>ping 10.39.128.1 -n 100

    Pinging 10.39.128.1 with 32 bytes of data:


    Ping statistics for 10.39.128.1:
    Packets: Sent = 100, Received = 9, Lost = 91 (91% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms


    uh yeah, you definitely have a problem on your side. 50% packet loss for just pinging the modem? Are you using a router or going straight to your modem? If using a router, take it out and run run the tests going straight to the modem, otherwise, it's either your ethernet card in the computer, the ethernet cable, or the modem.

Similar Threads

  1. High PING Problem
    By deapsea in forum General Broadband Forum
    Replies: 19
    Last Post: 02-14-08, 03:18 AM
  2. High Ping Issue
    By pparker in forum General Broadband Forum
    Replies: 31
    Last Post: 06-13-07, 01:12 AM
  3. ?'s about upload and ping times
    By Sylina in forum General Broadband Forum
    Replies: 0
    Last Post: 05-12-07, 02:07 PM
  4. Help! High Ping Times
    By FaZe in forum General Broadband Forum
    Replies: 12
    Last Post: 05-05-07, 09:10 PM
  5. ping computer name
    By NightShyamalan in forum Networking Forum
    Replies: 3
    Last Post: 04-25-05, 06:29 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
  •