1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Intermittent packet loss on wired with low ping.

Discussion in 'Network questions and troubleshooting' started by blobweird, Jan 25, 2019.

  1. blobweird

    blobweird New Member

    Messages:
    4
    Likes Received:
    0
    GPU:
    EVGA GTX 1070
    First post here. I'm at my wits end here. I don't want to have a tech come to find out it was something I could've solved all along. But it's driving me crazy. Every time I think it's gone for good, it comes back and is relentless (every 30 mins.)

    Seems to be no issues on the other devices in the home that are on wifi. Moved here 6 weeks ago and had no issue till 3 days ago. Since that time there have been no hardware changes, updates, router changes or anything.

    Things I have tried:

    - Replaced ethernet cable with better quality
    - Reset router to factory settings
    - Disabled uPnP on router
    - Extended the DHCP lease renewal time for this PC
    - Set the DHCP lease to static

    Here is what tracert looks like normally for me:

    C:\Users\Space>tracert 8.8.8.8

    Tracing route to google-public-dns-a.google.com [8.8.8.8]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms FIOS_Quantum_Gateway.fios-router.home [192.168.1.1]
    2 1 ms 1 ms <1 ms google-public-dns-a.google.com [8.8.8.8]

    Trace complete.

    Here is what it looks like while experiencing packet loss:

    C:\Users\Space>tracert 8.8.8.8

    Tracing route to google-public-dns-a.google.com [8.8.8.8]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms FIOS_Quantum_Gateway.fios-router.home [192.168.1.1]
    2 * * * Request timed out.
    3 * * * Request timed out.
    4 * * * Request timed out.
    5 * * * Request timed out.
    6 * * 6 ms 0.et-9-3-0.GW7.EWR6.ALTER.NET [140.222.233.41]
    7 6 ms 6 ms 6 ms 209.85.149.32
    8 * * * Request timed out.
    9 7 ms 6 ms 7 ms 108.170.226.206
    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 * 8 ms 8 ms google-public-dns-a.google.com [8.8.8.8]

    Trace complete.


    Any help would be appreciated!
     
  2. Steppzor

    Steppzor Master Guru

    Messages:
    780
    Likes Received:
    41
    GPU:
    MSI 1080 Ti GamingX
    A "Request timed out" in tracert is not neccessary a error, it's just the different nodes are not configured to accept ping requests (ICMP). You reached you destination so the connection is there.

    You should probably do a ping 8.8.8.8 -t to see if the connection drops.
     
  3. Steppzor

    Steppzor Master Guru

    Messages:
    780
    Likes Received:
    41
    GPU:
    MSI 1080 Ti GamingX
    I also doubt that this is your regular trace to google. There is no way that the next hop from you router is googles DNS server.
     
  4. blobweird

    blobweird New Member

    Messages:
    4
    Likes Received:
    0
    GPU:
    EVGA GTX 1070
    Hmm well it only seems to do it during packet loss. The loss was first noticed while gaming. Net graph on CS:GO said 77% loss. No choke, no fps drop, ping stayed low. Then when I tried to tracert during those times, I got the above, any other time it ran smooth. Only 2 hops though which I was told is a bit odd for it to only show 2 hops. Next time I get loss I can run that to see what I get though and will post back here with results.
     

  5. blobweird

    blobweird New Member

    Messages:
    4
    Likes Received:
    0
    GPU:
    EVGA GTX 1070
    That is what verizon told me also. Chat rep said I must have changed DNS settings in my router. Yet I did a factory reset and that is what I get for tracert 8.8.8.8

    Edit: She said there should be a timeout by default every time I tracert to google. Yet I only get timeouts during loss.
     
  6. Steppzor

    Steppzor Master Guru

    Messages:
    780
    Likes Received:
    41
    GPU:
    MSI 1080 Ti GamingX
    As you said, other devices connected to the same router don't have this problem. I think you should troubleshoot your computer.
    Is the computer connected through switch, wallsockets, plc etc.. to the router?
     
  7. blobweird

    blobweird New Member

    Messages:
    4
    Likes Received:
    0
    GPU:
    EVGA GTX 1070
    I'd be lying if I told you I knew. Not the most tech savvy. I run an Ethernet cable direct to router.
     
  8. SweenJM

    SweenJM Member Guru

    Messages:
    180
    Likes Received:
    52
    GPU:
    Sapphire 590x nitro
    I agree with Steppzor. If it is not happening with other devices, problem is probably your comp. Testing again from another computer hooked up on same cable, same port on router, same network config will tell you if its your comp or something else.
     
  9. Agent-A01

    Agent-A01 Ancient Guru

    Messages:
    11,332
    Likes Received:
    852
    GPU:
    1080Ti H20
    What modem do you have?

    Modems with puma can have random packet loss
     
  10. sykozis

    sykozis Ancient Guru

    Messages:
    20,812
    Likes Received:
    488
    GPU:
    XFX RX 470
    His tracert shows a FiOS Quantum Gateway. He says he has Verizon, so it should be a G1100 Gateway/Router produced by Actiontec, for Verizon. There are other variants of the same router produced by Actiontec for other FiOS providers. I can't seem to find any detailed tech specs on the model though. Worse case, he had the older Actiontec MI424, which had weird issues as well....
     

  11. 386SX

    386SX Master Guru

    Messages:
    314
    Likes Received:
    315
    GPU:
    RX64 Red Devil
    tracert is nice to see the path the packets take, but try PATHPING to get more info.

    PATHPING gets you more "ping-relevant" infos during path discovery.

    Try setting up a "ping -t HOSTNAME/IP" to some internal server / gateway you have, for example your router.
    While endlessly pinging, set another "ping -t" to 8.8.8.8 or some other external host. Let both pings run.
    When you notice a sudden drop in one of the two cmd windows, check if the second window looses its connection, too.
    If you loose the router / internal server, the fault is in your LAN or on your router (depending on what you pinged).
    If you loose the 8.8.8.8 connection (or external host), either your router or the ISP's network has some issue.

    Steps to check:
    Install other router
    Use other port (router AND computer)
    Use other RJ-45 cable to connect computer and router.
    (most work probably) DIsconnect all other devices except this one computer and your router. Then try everything from above, again.

    Best luck in finding this issue.
     

Share This Page