TechSpot

Big Fluctuations with Pinging my Default Gateway

By Lawler
Dec 30, 2015
Post New Reply
  1. Hey everyone, so when I was playing a game I noticed I was lagging horribly and at random times my ping would spike up to crazy levels. Just pinging my default gateway right now, it seems to be going from around 30 ms to 200 ms alternating back and forth. I read that this was suppose to be <1 ms, so I am lost on what to do. If you have any suggestions, please let me know. I have a second router set up connected to this one to work as a range extender, but that router was set up correctly to only extend, turning off DHCP assigning and all. Thank you!
     
  2. jobeard

    jobeard TS Ambassador Posts: 9,342   +622

    Let's be sure we're on the same page:
    Code:
    Tracing route to google.com [216.58.219.46] over a maximum of 30 hops:
    
      1    <1 ms    <1 ms    <1 ms  localrouter [192.168.0.1]
      2    11 ms    15 ms    12 ms  cpe-23-242-160-1.socal.res.rr.com [23.242.160.1]                             
      3    11 ms    15 ms    12 ms  tge0-9-0-22.wlvgcabn02h.socal.rr.com [24.30.172.137]
    ...
    ...
    
    My pc is at 192.168.0.5 and the 'default gateway' from the pc point of view is the local router 192.168.0.1
    but the ISP gateway is line 2 at 23.242.160.1

    So your access to your router is fluctuating ---
     
  3. Lawler

    Lawler TS Rookie Topic Starter

    The first part I put in was I think what you were looking for, this seemed normal but I am not sure if I just did it while the network was stable or what-not. The second part shows what I was talking about with the massive fluctuations after a little bit of time.


    Code:
    C:\WINDOWS\system32>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     *        *        *     Request timed out.
      2     *        *        *     Request timed out.
      3     *        *        *     Request timed out.
      4     *        *        *     Request timed out.
      5     *        *        *     Request timed out.
      6     *        *        *     Request timed out.
      7     *        *        *     Request timed out.
      8    21 ms    9 ms     10 ms  google-public-dns-a.google.com [8.8.8.8]
    



    Code:
    C:\WINDOWS\system32>ping 192.168.0.1 -t
    
    Pinging 192.168.0.1 with 32 bytes of data:
    Reply from 192.168.0.1: bytes=32 time=22ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=21ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=21ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=21ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=22ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=21ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=39ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=22ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=39ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=21ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=37ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=21ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=29ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=22ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=22ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=22ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=21ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=22ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=21ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=21ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=278ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=29ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=342ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=21ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=298ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=21ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=243ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=21ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=282ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=22ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=284ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=48ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=312ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=44ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=280ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=81ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=322ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=56ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=259ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=39ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=300ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=39ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=279ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=64ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=297ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=55ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=266ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=41ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=49ms TTL=64
    Reply from 192.168.0.1: bytes=32 time=49ms TTL=64
    
    I am not sure if this is normal activity, but I had a couple of buddies do the same pings and they all came out to stable and only around 5 to 10 MS each ping. Let me know if you have any ideas and if this could be the reason why I see these giant lag spikes.
     
  4. jobeard

    jobeard TS Ambassador Posts: 9,342   +622

    The timeouts from "tracert 8.8.8.8" are due to your ISP settings and can be ignored, as you got to 8.8.8.8 correctly.

    Your result for "ping 192.168.0.1 -t" is deplorable!
    Tell me

    • what av product are you running
    • is the firewall active
    • any other security or malware in use
     
  5. Lawler

    Lawler TS Rookie Topic Starter

    Running Bitdefender Internet Security 2015
    Firewall is on
    No other security programs
     
  6. Lawler

    Lawler TS Rookie Topic Starter

    Bump
     
  7. jobeard

    jobeard TS Ambassador Posts: 9,342   +622

    Login as admin or runas /user:administrator cmd (give pwd) and then enter


    ipconfig /flushdns

    nbtstat -R

    netsh int reset all

    netsh int ip reset

    netsh winsock reset

    Reboot
     
  8. Lawler

    Lawler TS Rookie Topic Starter

    Netsh int reset all came back as command not found, did the rest and rebooted. Looks like no change so far but I will give an update later when I get back. Thank you for all the help again, I really appreciate it.
     
  9. Lawler

    Lawler TS Rookie Topic Starter

    So I actually found a fix for it, but I am not sure exactly how it fixed it. Now my ping to 192.168.0.1 is always <1ms. The fix I did was in this video if you are interested.Thank you for your help jobeard, you are awesome!

     
  10. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    For future reference, to elevate Powershell without need for password:
    start-process powershell -verb runAs
     

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...