Helpzor. Packet Loss ??

Discussion in 'Networking and Computer Security' started by doodlehacker, Mar 26, 2010.

  1. doodlehacker

    doodlehacker Geek Trainee

    Likes Received:
    0
    Trophy Points:
    0
    First off specs:

    OS Name Microsoft Windows 7 Professional
    Version 6.1.7600 Build 7600
    Other OS Description Not Available
    OS Manufacturer Microsoft Corporation
    System Name M1ABRAMS
    System Manufacturer Gateway
    System Model FX530
    System Type x64-based PC
    Processor Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz, 2394 Mhz, 4 Core(s), 4 Logical Processor(s)
    BIOS Version/Date Intel Corp. LA97510J.15A.0285.2007.0906.0226, 9/6/2007
    SMBIOS Version 2.3
    Windows Directory C:\Windows
    System Directory C:\Windows\system32
    Boot Device \Device\HarddiskVolume2
    Locale United States
    Hardware Abstraction Layer Version = "6.1.7600.16385"
    User Name M1ABRAMS\Kenny
    Time Zone Eastern Standard Time
    Installed Physical Memory (RAM) 8.00 GB
    Total Physical Memory 8.00 GB
    Available Physical Memory 4.36 GB
    Total Virtual Memory 16.0 GB
    Available Virtual Memory 11.4 GB
    Page File Space 8.00 GB
    Page File C:\pagefile.sys

    Ping Tests

    Pinging Google [209.85.225.147] with 32 bytes of data:
    Reply from 209.85.225.147: bytes=32 time=57ms TTL=45
    Reply from 209.85.225.147: bytes=32 time=54ms TTL=45
    Reply from 209.85.225.147: bytes=32 time=56ms TTL=45
    Reply from 209.85.225.147: bytes=32 time=54ms TTL=45
    Reply from 209.85.225.147: bytes=32 time=59ms TTL=45
    Request timed out.
    Reply from 209.85.225.147: bytes=32 time=55ms TTL=45
    Request timed out.
    Reply from 209.85.225.147: bytes=32 time=65ms TTL=45
    Reply from 209.85.225.147: bytes=32 time=64ms TTL=45

    Ping statistics for 209.85.225.147:
    Packets: Sent = 10, Received = 8, Lost = 2 (20% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 54ms, Maximum = 65ms, Average = 58ms


    Pinging any-fp.wa1.b.yahoo.com [209.191.122.70] with 32 bytes of data:
    Reply from 209.191.122.70: bytes=32 time=36ms TTL=49
    Reply from 209.191.122.70: bytes=32 time=39ms TTL=49
    Reply from 209.191.122.70: bytes=32 time=44ms TTL=49
    Reply from 209.191.122.70: bytes=32 time=40ms TTL=49
    Reply from 209.191.122.70: bytes=32 time=35ms TTL=49
    Reply from 209.191.122.70: bytes=32 time=39ms TTL=49
    Reply from 209.191.122.70: bytes=32 time=50ms TTL=49
    Request timed out.
    Reply from 209.191.122.70: bytes=32 time=49ms TTL=49
    Reply from 209.191.122.70: bytes=32 time=37ms TTL=49

    Ping statistics for 209.191.122.70:
    Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 35ms, Maximum = 50ms, Average = 41ms


    Pinging hardwareforums.com [207.58.155.243] with 32 bytes of data:
    Request timed out.
    Reply from 207.58.155.243: bytes=32 time=38ms TTL=50
    Reply from 207.58.155.243: bytes=32 time=33ms TTL=50
    Request timed out.
    Reply from 207.58.155.243: bytes=32 time=47ms TTL=50
    Request timed out.
    Reply from 207.58.155.243: bytes=32 time=34ms TTL=50
    Reply from 207.58.155.243: bytes=32 time=53ms TTL=50
    Reply from 207.58.155.243: bytes=32 time=40ms TTL=50
    Reply from 207.58.155.243: bytes=32 time=36ms TTL=50

    Ping statistics for 207.58.155.243:
    Packets: Sent = 10, Received = 7, Lost = 3 (30% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 53ms, Average = 40ms


    Tracerts (Start IP is WoW Server IP)

    Tracing route to 63.241.255.218 over a maximum of 30 hops

    1 1 ms 1 ms 1 ms 192.168.1.1
    2 8 ms 7 ms 8 ms 208.60.222.1
    3 12 ms 11 ms 9 ms 65.14.147.157
    4 14 ms 16 ms 16 ms 205.152.122.140
    5 17 ms 15 ms 15 ms 12.83.0.164
    6 16 ms 18 ms 22 ms 12.83.0.187
    7 14 ms 15 ms 13 ms 65.83.238.198
    8 36 ms 45 ms 33 ms cr1.attga.ip.att.net [12.122.141.54]
    9 45 ms 33 ms 38 ms cr2.dlstx.ip.att.net [12.122.28.174]
    10 33 ms 35 ms 38 ms gar23.dlstx.ip.att.net [12.122.138.157]
    11 32 ms 34 ms 35 ms 12-122-254-154.attens.net [12.122.254.154]
    12 34 ms 35 ms 35 ms 63.241.193.22
    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.


    Tracing route to 63.241.255.218 over a maximum of 30 hops

    1 3 ms 3 ms 1 ms 192.168.1.1
    2 11 ms 7 ms 11 ms 208.60.222.1
    3 10 ms 20 ms 16 ms 65.14.147.157
    4 19 ms 26 ms * 205.152.122.140
    5 17 ms * 31 ms 12.83.0.168
    6 14 ms 18 ms 24 ms 12.83.0.187
    7 18 ms 18 ms 16 ms 65.83.238.198
    8 36 ms 34 ms 37 ms cr1.attga.ip.att.net [12.122.141.54]
    9 62 ms 39 ms 36 ms cr2.dlstx.ip.att.net [12.122.28.174]
    10 * * 42 ms gar23.dlstx.ip.att.net [12.122.138.157]
    11 * * 46 ms 12-122-254-154.attens.net [12.122.254.154]
    12 40 ms * 38 ms 63.241.193.22
    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.


    I've used wired and wireless with no fix. And I'm on cable internet 3Gb/s.

    My World of Warcraft will freeze every 30sec for about 5sec+ and after freeze everything happens during that freeze in 1sec max. Makes raiding very difficult. And lately it has gotten worse.

    I have SpeedFan and my components are NOT overheating.
    Computer fans are 70-100% and my GPU fan is 100% always.

    I've heard that it could be a number of problems, but request any more info and you will get it, I need help finding the culprit of this problem.

    ALL drivers are up to-date. And I have 5/5 bars internet connection.

    All ports open for game...and all the normal stuff you can think of mostly of fixing "INTORNETZ PRUBLERMZ". Anything a pc "enthuasist" wouldn't think of...?

    THANKS FOR HELP!
     
  2. Anti-Trend

    Anti-Trend Nonconformist Geek

    Likes Received:
    118
    Trophy Points:
    63
    Please ping your next hop (looks like 192.168.1.1) 100 times or so and post the stats here.
     
  3. doodlehacker

    doodlehacker Geek Trainee

    Likes Received:
    0
    Trophy Points:
    0
    Ping statistics for 192.168.1.1:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 19ms, Average = 1ms
     
  4. Anti-Trend

    Anti-Trend Nonconformist Geek

    Likes Received:
    118
    Trophy Points:
    63
    There is no packet loss when you ping your next hop (cable modem? cheap plastic router thingy?)... this means your PC is not the problem, the packet loss is coming from somewhere between your next hop and the sites you're pinging. What's your next hop?
     
  5. doodlehacker

    doodlehacker Geek Trainee

    Likes Received:
    0
    Trophy Points:
    0
    Pinging 65.14.147.157 with 32 bytes of data:
    Ping statistics for 65.14.147.157:
    Packets: Sent = 100, Received = 93, Lost = 7 (7% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 8ms, Maximum = 23ms, Average = 13ms

    Also did a 50 ping test returning 16% packet loss.

    This seems to be the start of it, let me know if you want any more pings past the 3RD hop. I'm unsure what this ip is and how to fix it...?
     
  6. Anti-Trend

    Anti-Trend Nonconformist Geek

    Likes Received:
    118
    Trophy Points:
    63
    What I mean is what type of device has the IP 192.168.1.1? A cable modem, router, etc?
     
  7. doodlehacker

    doodlehacker Geek Trainee

    Likes Received:
    0
    Trophy Points:
    0
    That is my LinkSys router.

    Which is preceded by a cable modem.
     
  8. Anti-Trend

    Anti-Trend Nonconformist Geek

    Likes Received:
    118
    Trophy Points:
    63
    So it goes something like this, right?

    Computer -> Linksys -> Cable modem -> Internet

    Make sure the WAN interface of your router is not set to half-duplex, be it manually or automatically. A half duplex connection will cause collisions, which necessitate TCP retransmissions, and outright packet loss. Once you've done that, try pinging your public gateway (which from your traceroute appears to be 208.60.222.1, but it's tough to tell for sure just based on that).
     
  9. doodlehacker

    doodlehacker Geek Trainee

    Likes Received:
    0
    Trophy Points:
    0
    And no: Cable Jack in Wall -> Cable Modem -> LinkSys -> Computer (xbox 360, not in use) (laptop, that i know is not using that much bandwidth)-> Internet


    Not sure how to change that setting?

    Settings on Router

    Description of those settings.

    Granted the pics suck @ss, but if you squint you can make out the words.
     
  10. Anti-Trend

    Anti-Trend Nonconformist Geek

    Likes Received:
    118
    Trophy Points:
    63
    Um, you have the location of the internet backwards... but I see what you're trying to say. :p I was just trying to make sure that the router was correctly deployed on your network.

    The images you posted are for wifi, which doesn't really have anything to do with the problem you're seeing. The issue is most likely that the connection between your router and cable modem is only half-duplex, meaning it can only send or receive traffic at once, but not both. If it tries to send and receive traffic at exactly the same time, the result is a collision and dropped packets. Therefore, only full-duplex connections should be used.

    But there's a problem. It seems after looking over your router's whole manual, there doesn't seem to be a way to set or even view the speed and duplex of each port. Ugh, I hate cheap plastic routers. :)

    Perhaps you might try connecting the cable modem directly to your PC and see what speed and duplex you can negotiate with the modem, and whether you're still seeing packet loss at that point. NOTE: If you're running Windows, DO NOT connect directly to the internet without some kind of firewall running. Make sure you have a firewall turned on before you connect directly to your cable modem.
     

Share This Page