NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Threather's avatar
Threather
Aspirant
Sep 13, 2017
Solved

Netgear WND4300 Inconsistent pings

Model: WNDR4300

Firmware: v1.0.2.88

OS: Windows 10 

 

I am currently running into an issue where if I connect my PC to my WNDR4300 via ethernet cable or wireless, I have major ping issues.  I am currnetly running versions 1.0.2.88 firmware on the router.  I have confirmed this is not an issue with my PC as I am able to directly connect to my cable modem and I get flawless pings.

 

Below are my test results of pinging straight from my PC to the IP address of the router.  The environment I used to test this was the router plugged directly into a power outlet (to rule out surge protector causing power problems), PC hard wired into the router (results do not differ when WiFi), and a ping to the IP address of the router itself.   

 

Reply from 192.168.1.1: bytes=32 time=295ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=595ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=892ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1190ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=296ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=593ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=889ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1187ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=295ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=593ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
 
Ping statistics for 192.168.1.1:
    Packets: Sent = 253, Received = 253, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1294ms, Average = 330ms
  • Welcome to the community, Threather

     

    What are the devices connected to your network?

    Try to connect one by one and then do a ping test.

    This is to verify if there's a device that's causing this.

    Have you tried reinstalling the firmware? How about factory resetting the unit?

     

3 Replies

  • ElaineM's avatar
    ElaineM
    NETGEAR Employee Retired

    Welcome to the community, Threather

     

    What are the devices connected to your network?

    Try to connect one by one and then do a ping test.

    This is to verify if there's a device that's causing this.

    Have you tried reinstalling the firmware? How about factory resetting the unit?

     

    • Threather's avatar
      Threather
      Aspirant

      My apologies for the late reply, i've been constantly troubleshooting the issue and having to let it run for 3-4 days before i could confirm if it worked or not.  

       

      What are the devices connected to your network?

         Only my Laptop was connected to the router, the router was not even connected to the cable modem

      Try to connect one by one and then do a ping test.

         This occurred from multiple devices when solo connected to the router

       

      Have you tried reinstalling the firmware?

         I updated to the latest firmware, and then I re-flashed the firmware to no avail

      How about factory resetting the unit?

         After 7-days of testing, this has fixed the issue.