1. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! If you're new to Tech Support Guy, we highly recommend that you visit our Guide for New Members.

Absolutely massive packet loss all the time.

Discussion in 'Networking' started by Eldon9, Nov 2, 2011.

Thread Status:
Not open for further replies.
Advertisement
  1. Eldon9

    Eldon9 Thread Starter

    Joined:
    Nov 2, 2011
    Messages:
    8
    I've switched over to Comcast recently after having a terrible time with AT&T. I've had comcast guys come out and rewire everything both inside and outside the house. I've switched modems, I've switched routers, (both to and not to what the they recommend for their service), and I've ran the pingtest in safe mode with networking to see if it was me. I am constantly having the same problem all the time.

    I have around 60-90% packet loss at all times. As a gamer, this is a HUGE problem. The breadwinner of the house works from home on an online VPN, so it's an even bigger problem and is far more serious for him.

    [​IMG] is my pingtest.net result.

    Below are my computer specs. I've ran Malwarebytes locally and Eset's online scanner, so I wouldn't really say "Antivirus: None". But you get the point.

    Any help is appreciated.

    Tech Support Guy System Info Utility version 1.0.0.2
    OS Version: Microsoft® Windows Vista™ Ultimate, Service Pack 2, 32 bit
    Processor: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz, x64 Family 6 Model 15 Stepping 11
    Processor Count: 4
    RAM: 3581 Mb
    Graphics Card: ATI Radeon HD 5700 Series, 1024 Mb
    Hard Drives: C: Total - 466600 MB, Free - 72548 MB;
    Motherboard: Gigabyte Technology Co., Ltd., EP35-DS4
    Antivirus: None
     
  2. LagunaGTO

    LagunaGTO Account Closed

    Joined:
    Jan 27, 2011
    Messages:
    139
    This is happening across multiple computers?

    Have you replaced NICs?

    I've seen in the past where if there is a bad NIC on the network, it will take down the network as a whole. Regardless if its partially working or not. What happens when you only have 1 device connected at a time? Try one PC (make sure NOTHING else is on, even shut off cell phones) and run the test. Then test the next, next, next, etc.

    This is very weird that they've replaced all networking parts and this is still happening. Do you have a laptop as one of your PCs? Can you take it somewhere else (friends, McD's) and see how it performs there?
     
  3. Couriant

    Couriant Trusted Advisor

    Joined:
    Mar 26, 2002
    Messages:
    32,233
    First Name:
    James
    Do the ping test in command line (ping yahoo.com -n 100) and post back the stats.
     
  4. LagunaGTO

    LagunaGTO Account Closed

    Joined:
    Jan 27, 2011
    Messages:
    139
    On top of this, do a tracert for us.

    Just do tracert 74.125.225.48. Show us those results as well.
     
  5. Couriant

    Couriant Trusted Advisor

    Joined:
    Mar 26, 2002
    Messages:
    32,233
    First Name:
    James
    I was thinking that too... just to amend this command, type the following:

    tracert 74.125.225.48 > trace.txt
    tracert yahoo.com >> trace.txt
    tracert red.com >> trace.txt & trace.txt
    .

    Now each command may take up to 2-3 mins each and it will look like it's doing nothing. Wait for the prompt for each command. The last one will open up the text file with all of the information that you need to paste here.
     
  6. Eldon9

    Eldon9 Thread Starter

    Joined:
    Nov 2, 2011
    Messages:
    8
    C:\Users\Inhert>ping yahoo.com -n 100

    Pinging yahoo.com [98.137.149.56] with 32 bytes of data:
    Reply from 98.137.149.56: bytes=32 time=86ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=102ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=85ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=99ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=98ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=98ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=102ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=98ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=99ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=154ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=94ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=96ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=98ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=97ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=102ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=99ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=92ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=135ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=135ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=98ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=92ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=89ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=88ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=87ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=85ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=86ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=87ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=86ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=88ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=117ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=118ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=88ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=89ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=87ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=89ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=86ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=89ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=94ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=125ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=94ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=121ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=89ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=116ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=88ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=94ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=85ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=88ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=135ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=158ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=90ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=89ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=86ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=88ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=88ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=87ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=85ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=85ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=87ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=149ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=178ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=86ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=86ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=89ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=88ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=90ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=89ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=89ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=89ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=86ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=136ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=88ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=86ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=89ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=112ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=88ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=85ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=85ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=87ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=113ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=86ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=85ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=86ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=1030ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=104ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=99ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=86ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=90ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=86ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=88ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=92ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=86ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=160ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=88ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=87ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=85ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=85ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=85ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=85ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=95ms TTL=48
    Reply from 98.137.149.56: bytes=32 time=87ms TTL=48

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

    Tracing route to ord08s06-in-f16.1e100.net [74.125.225.48]

    over a maximum of 30 hops:



    1 1 ms <1 ms <1 ms 10.0.0.1

    2 44 ms 29 ms 30 ms c-24-11-248-1.hsd1.in.comcast.net [24.11.248.1]

    3 8 ms 9 ms 8 ms te-7-6-ur04.mishawaka.in.sbend.comcast.net [68.87.235.181]

    4 22 ms 10 ms 10 ms te-3-3-ur03.mishawaka.in.sbend.comcast.net [68.86.184.230]

    5 16 ms 16 ms 16 ms te-1-7-0-5-ar01.area4.il.chicago.comcast.net [68.87.235.17]

    6 14 ms 19 ms 16 ms pos-3-12-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.91.233]

    7 19 ms 17 ms 18 ms pos-1-1-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.86.38]

    8 16 ms 16 ms 16 ms 66-208-233-142-ubr02b-westln01-mi.hfc.comcastbusiness.net [66.208.233.142]

    9 15 ms 16 ms 16 ms 209.85.254.122

    10 16 ms 14 ms 16 ms 209.85.250.28

    11 19 ms 19 ms 17 ms ord08s06-in-f16.1e100.net [74.125.225.48]



    Trace complete.



    Tracing route to yahoo.com [98.137.149.56]

    over a maximum of 30 hops:



    1 <1 ms 1 ms <1 ms 10.0.0.1

    2 38 ms 24 ms 26 ms c-24-11-248-1.hsd1.in.comcast.net [24.11.248.1]

    3 10 ms 10 ms 11 ms te-7-6-ur04.mishawaka.in.sbend.comcast.net [68.87.235.181]

    4 10 ms 9 ms 9 ms te-3-1-ur03.mishawaka.in.sbend.comcast.net [68.87.235.21]

    5 43 ms 46 ms 32 ms te-1-7-0-7-ar01.area4.il.chicago.comcast.net [68.87.235.9]

    6 39 ms 30 ms 36 ms pos-3-9-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.90.45]

    7 48 ms 17 ms 16 ms pos-0-3-0-0-cr01.chicago.il.ibone.comcast.net [68.86.88.21]

    8 18 ms 20 ms 22 ms xe-9-3-0.edge1.Chicago2.Level3.net [4.71.248.21]

    9 17 ms 25 ms 17 ms vlan51.ebr1.Chicago2.Level3.net [4.69.138.158]

    10 45 ms 47 ms 42 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]

    11 43 ms 43 ms 49 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.151.181]

    12 91 ms 82 ms 84 ms ae-3-3.ebr2.SanJose1.Level3.net [4.69.132.57]

    13 101 ms 82 ms 84 ms ae-82-82.csw3.SanJose1.Level3.net [4.69.153.26]

    14 123 ms 84 ms 117 ms ae-33-80.car3.SanJose1.Level3.net [4.69.152.133]

    15 182 ms 84 ms 100 ms YAHOO-INC.car3.SanJose1.Level3.net [4.71.112.14]

    16 86 ms 130 ms 90 ms ae-1-d171.msr2.sp1.yahoo.com [216.115.107.87]

    17 85 ms 86 ms 88 ms et-17-25.fab3-1-gdc.sp2.yahoo.com [98.136.16.27]

    18 86 ms 86 ms 86 ms te-9-1.bas2-1-prd.sp2.yahoo.com [67.195.130.108]

    19 90 ms 85 ms 95 ms ir1.fp.vip.sp2.yahoo.com [98.137.149.56]



    Trace complete.



    Tracing route to red.com [184.106.4.217]

    over a maximum of 30 hops:



    1 <1 ms <1 ms <1 ms 10.0.0.1

    2 23 ms 28 ms 29 ms c-24-11-248-1.hsd1.in.comcast.net [24.11.248.1]

    3 10 ms 9 ms 9 ms te-7-6-ur04.mishawaka.in.sbend.comcast.net [68.87.235.181]

    4 9 ms 9 ms 12 ms te-3-1-ur03.mishawaka.in.sbend.comcast.net [68.87.235.21]

    5 15 ms 15 ms 16 ms te-1-7-0-7-ar01.area4.il.chicago.comcast.net [68.87.235.9]

    6 17 ms 16 ms 16 ms pos-3-7-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.90.53]

    7 17 ms 27 ms 19 ms pos-0-3-0-0-cr01.chicago.il.ibone.comcast.net [68.86.88.21]

    8 17 ms 18 ms 19 ms xe-10-3-0.edge1.Chicago2.Level3.net [4.71.248.9]

    9 20 ms 18 ms 18 ms RACKSPACE-M.edge1.Chicago2.Level3.net [4.71.248.54]

    10 24 ms 23 ms 21 ms coreb.ord1.rackspace.net [184.106.126.134]

    11 18 ms 21 ms 18 ms core1-CoreB.ord1.rackspace.net [184.106.126.129]

    12 19 ms 20 ms 19 ms core1-aggr401a-1.ord1.rackspace.net [173.203.0.233]

    13 18 ms 22 ms 17 ms 184.106.4.217



    Trace complete.



    I have not replaced any of the NICs. I HAVE reseated my own PCI card, and in fact did so tonight. I haven't had any problems since yet, but I've gone a day with only a single disconnection, where other days I'll be dropped 20 times over the course of 8 minutes. So we'll see if it fixed anything, but it really is doubtful.
     
  7. Couriant

    Couriant Trusted Advisor

    Joined:
    Mar 26, 2002
    Messages:
    32,233
    First Name:
    James
    well there doesn't to be some lag in routing. If you just replaced the NIC you may have found your cause. A bad NIC on the network can cause issues for other users.
     
  8. LagunaGTO

    LagunaGTO Account Closed

    Joined:
    Jan 27, 2011
    Messages:
    139
    All of that came back just as it should. There was a spike tracing the route to yahoo.com but that was after the ISP.

    There was this though:
    Can you go to speedtest.net for us and post results?




    EDIT:
    I agree. Hopefully that resolved the issue and it is like I suspected and posted earlier that its a bad NIC on the network.
     
  9. Eldon9

    Eldon9 Thread Starter

    Joined:
    Nov 2, 2011
    Messages:
    8

    [​IMG] is my speedtest.net result. It shows pretty good results obviously. I had only recently discovered pingtest.net, which is the only site raising red flags for my internet.

    My only symptom is that I will randomly get extremely heavy ping spikes (I've gone over 30k latency) and they're usually frequent. If I have one, I'll have 10 over the next hour.

    To clarify, Skype will drop any calls I'm on and most of the time don't reconnect. Any games I have will lag anywhere from 10 to 40 seconds to just straight up dropping me. Sometimes, if it's really bad, the network will disappear off my windows networks, or the connection will be so low I can't reconnect to it, or it'll tell me my adapter isn't made for the network even though I've connected to it a thousand times before.

    I haven't tried turning off all the other computers yet, but as I said, our breadwinner is working on a VPN right now so I'm in no position to for tonight. I can report back in the morning if it turns out that is the issue.
     
  10. LagunaGTO

    LagunaGTO Account Closed

    Joined:
    Jan 27, 2011
    Messages:
    139
    Hopefully your resetting of the NIC fixed it. Possibly a bad connection. Let us know!
     
  11. Couriant

    Couriant Trusted Advisor

    Joined:
    Mar 26, 2002
    Messages:
    32,233
    First Name:
    James
    LagunaGTO > that was only 1 spike... which can be due to a website page load or something... let us know eldon on your results.
     
  12. Eldon9

    Eldon9 Thread Starter

    Joined:
    Nov 2, 2011
    Messages:
    8
    Tried the NIC fix. No good, still d/c'd and still have packet loss. I just have no clue what this could be.
     
  13. LagunaGTO

    LagunaGTO Account Closed

    Joined:
    Jan 27, 2011
    Messages:
    139
    You need to attempt to have every PC off and disconnect the ethernet cords from any PC except one and test it and see if it happens. It's important that even though the PC is off, the wires are disconnected as well.

    If it still causes a problem on that one PC, shut that PC down and pull the cord from it. Then, test another machine.

    Report back with these testings.
     
  14. Eldon9

    Eldon9 Thread Starter

    Joined:
    Nov 2, 2011
    Messages:
    8
    That's what I had done when I last posted. I just tried disconnecting the one pc that's directly connected to the modem, turning off the other pc with a PCI card (my own) after disconnecting it from the wireless network, and using one of the laptops to connect to the network itself to make sure it was neither of the PC's with an NIC. Running the pingtest from the laptop with everything else off and disconnected, I got identical results.

    [​IMG]
     
  15. LagunaGTO

    LagunaGTO Account Closed

    Joined:
    Jan 27, 2011
    Messages:
    139
    This doesn't make any sense. Each one of your PCs is doing it but yet all the wiring has been replaced? There must be interference somewhere or something to do with the ISP. I'd consistently call the ISP and make them fix it.
     
  16. Sponsor

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 733,556 other people just like you!

Loading...
Similar Threads - Absolutely massive packet
  1. chavely
    Replies:
    2
    Views:
    198
Thread Status:
Not open for further replies.

Short URL to this thread: https://techguy.org/1025204

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice