Devices losing connection with c6300 repeatedly

Question

Devices lose internet. Restart device and gets reconnected. Constant ping shows sporadic higher return times hundreds ms. Clears up then has a regular spike.
We have about 20 devices on. Connect via cat5 and no issues.

Afkinch · Answer

Equipment: Netgear C6300Computer: HP LaptopConnection:&nbsp; Wireless connectionEthernet: Shows no issues when I connect to it.Problem: Computer responds terribly slow at intermittent times.Troubleshooting conducted:Ran a continuous ping to gateway 192.168.0.1 and received round trips that bounce from 3ms to 300ms sporadically.&nbsp;&nbsp;ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUnCorrectables1LockedQAM 2561507000000 Hz0.2 dBmV40.3 dB5802LockedQAM 2562513000000 Hz0.2 dBmV40.3 dB5603LockedQAM 2563519000000 Hz0.2 dBmV38.9 dB3404LockedQAM 2564525000000 Hz0.0 dBmV40.3 dB2905LockedQAM 2565531000000 Hz0.0 dBmV38.9 dB2906LockedQAM 2566537000000 Hz0.0 dBmV38.9 dB2807LockedQAM 2567543000000 Hz0.0 dBmV38.9 dB4008LockedQAM 2568549000000 Hz-0.2 dBmV38.9 dB53149LockedQAM 2569555000000 Hz-0.2 dBmV38.9 dB531910LockedQAM 25610561000000 Hz-0.2 dBmV38.6 dB1023011LockedQAM 25611567000000 Hz-0.2 dBmV38.6 dB586112LockedQAM 25612573000000 Hz0.0 dBmV38.9 dB883213LockedQAM 25613579000000 Hz0.0 dBmV38.9 dB64414LockedQAM 25614585000000 Hz0.5 dBmV38.9 dB55015LockedQAM 25615591000000 Hz0.2 dBmV38.9 dB65016LockedQAM 25616597000000 Hz0.2 dBmV38.6 dB3920&nbsp;Upstream Bonded ChannelsChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower1LockedATDMA15120 Ksym/sec17300000 Hz44.5 dBmV2LockedATDMA25120 Ksym/sec23700000 Hz45.3 dBmV3LockedATDMA35120 Ksym/sec30100000 Hz45.0 dBmV4LockedATDMA45120 Ksym/sec36500000 Hz45.8 dBmV&nbsp;&nbsp;

FURRYe38 · Answer

What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.Any Wifi Neighbors near by? If so, how many?

Afkinch · Answer

Changed my 2.4 GHhz to channel 9, I show about 30 Access points, but there is only 4 on Channel 9; already set to manual. 5GHz has been changed as well. I have been monitoring the channels and changing when their busy.

This problem has only recently started in the past 3 or 4 weeks. Before that I did not have a problem. Nothing recently has changed on my network. The Netgear C6300 is 3 or 4 years old.

Was looking to see if the Netgear C6300 was at its EOL, but unable to determine that the Netgear website.

FURRYe38 · Answer

Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz. Channel 9 is not a primary channel to use.&nbsp;ALso try turning down the power output on the radios from 100% to 75 or 50% to see if this helps any since you have other wifi nieghbors near by.&nbsp;Under Advanced Tab/Advanced Settings/Wireless Settings

Afkinch · Answer

I reduced the power and changed the 2.4GHz settings to 6 and at first I thought the problem was solved. Yesterday was much better...could still see a hit about everhy 30 secs. Thought I would just watch it another day or so, but then everything went bad...here are the info I captured:&nbsp;HP LaptopNetgear C6300Here is the continous ping to my gateway...Reply from 192.168.0.1: bytes=32 time=483ms TTL=64Reply from 192.168.0.1: bytes=32 time=532ms TTL=64Reply from 192.168.0.1: bytes=32 time=777ms TTL=64Reply from 192.168.0.1: bytes=32 time=505ms TTL=64Reply from 192.168.0.1: bytes=32 time=1381ms TTL=64Reply from 192.168.0.1: bytes=32 time=606ms TTL=64Reply from 192.168.0.1: bytes=32 time=202ms TTL=64Reply from 192.168.0.1: bytes=32 time=690ms TTL=64Reply from 192.168.0.1: bytes=32 time=701ms TTL=64Reply from 192.168.0.1: bytes=32 time=561ms TTL=64Reply from 192.168.0.1: bytes=32 time=504ms TTL=64Reply from 192.168.0.1: bytes=32 time=377ms TTL=64Reply from 192.168.0.1: bytes=32 time=427ms TTL=64Reply from 192.168.0.1: bytes=32 time=381ms TTL=64Reply from 192.168.0.1: bytes=32 time=428ms TTL=64Reply from 192.168.0.1: bytes=32 time=1086ms TTL=64Reply from 192.168.0.1: bytes=32 time=1076ms TTL=64Reply from 192.168.0.1: bytes=32 time=1487ms TTL=64Reply from 192.168.0.1: bytes=32 time=807ms TTL=64Reply from 192.168.0.1: bytes=32 time=18ms TTL=64Reply from 192.168.0.1: bytes=32 time=1188ms TTL=64Reply from 192.168.0.1: bytes=32 time=79ms TTL=64Reply from 192.168.0.1: bytes=32 time=79ms TTL=64Reply from 192.168.0.1: bytes=32 time=209ms TTL=64Reply from 192.168.0.1: bytes=32 time=94ms TTL=64Reply from 192.168.0.1: bytes=32 time=158ms TTL=64Reply from 192.168.0.1: bytes=32 time=180ms TTL=64Reply from 192.168.0.1: bytes=32 time=360ms TTL=64Reply from 192.168.0.1: bytes=32 time=229ms TTL=64Reply from 192.168.0.1: bytes=32 time=318ms TTL=64Reply from 192.168.0.1: bytes=32 time=187ms TTL=64Reply from 192.168.0.1: bytes=32 time=37ms TTL=64Reply from 192.168.0.1: bytes=32 time=59ms TTL=64Reply from 192.168.0.1: bytes=32 time=231ms TTL=64Reply from 192.168.0.1: bytes=32 time=366ms TTL=64Reply from 192.168.0.1: bytes=32 time=143ms TTL=64Reply from 192.168.0.1: bytes=32 time=210ms TTL=64Reply from 192.168.0.1: bytes=32 time=279ms TTL=64Reply from 192.168.0.1: bytes=32 time=240ms TTL=64Reply from 192.168.0.1: bytes=32 time=320ms TTL=64Reply from 192.168.0.1: bytes=32 time=102ms TTL=64Reply from 192.168.0.1: bytes=32 time=197ms TTL=64Reply from 192.168.0.1: bytes=32 time=78ms TTL=64Reply from 192.168.0.1: bytes=32 time=496ms TTL=64Reply from 192.168.0.1: bytes=32 time=434ms TTL=64Reply from 192.168.0.1: bytes=32 time=432ms TTL=64Reply from 192.168.0.1: bytes=32 time=829ms TTL=64Reply from 192.168.0.1: bytes=32 time=423ms TTL=64Reply from 192.168.0.1: bytes=32 time=517ms TTL=64Reply from 192.168.0.1: bytes=32 time=220ms TTL=64Reply from 192.168.0.1: bytes=32 time=313ms TTL=64Reply from 192.168.0.1: bytes=32 time=1032ms TTL=64Reply from 192.168.0.1: bytes=32 time=739ms TTL=64Here are the C6300 Cable Connection&nbsp;&lt;tabindex=-1&gt;tartup Procedure&lt;/tabindex=-1&gt;ProcedureStatusCommentAcquire Downstream Channel507000000 HzLockedConnectivity StateOkOperationalBoot StateOkOperationalSecurityEnabledBPI+IP Provisioning ModeHonor MDDhonorMdd(4)Downstream Bonded ChannelsChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUnCorrectables1LockedQAM 2561507000000 Hz0.0 dBmV40.3 dB2902LockedQAM 2562513000000 Hz-0.2 dBmV40.3 dB003LockedQAM 2563519000000 Hz-0.2 dBmV38.9 dB004LockedQAM 2564525000000 Hz-0.4 dBmV40.3 dB005LockedQAM 2565531000000 Hz-0.5 dBmV38.9 dB006LockedQAM 2566537000000 Hz-0.5 dBmV38.9 dB007LockedQAM 2567543000000 Hz-0.7 dBmV38.9 dB008LockedQAM 2568549000000 Hz-0.7 dBmV38.9 dB009LockedQAM 2569555000000 Hz-0.7 dBmV38.9 dB0010LockedQAM 25610561000000 Hz-0.7 dBmV38.9 dB0011LockedQAM 25611567000000 Hz-0.7 dBmV38.9 dB0012LockedQAM 25612573000000 Hz-0.5 dBmV38.6 dB0013LockedQAM 25613579000000 Hz-0.5 dBmV38.9 dB0014LockedQAM 25614585000000 Hz0.0 dBmV38.6 dB0015LockedQAM 25615591000000 Hz-0.2 dBmV38.6 dB0016LockedQAM 25616597000000 Hz0.0 dBmV38.6 dB00Upstream Bonded ChannelsChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower1LockedATDMA15120 Ksym/sec17300000 Hz44.5 dBmV2LockedATDMA25120 Ksym/sec23700000 Hz45.3 dBmV3LockedATDMA35120 Ksym/sec30100000 Hz45.3 dBmV4LockedATDMA45120 Ksym/sec36500000 Hz45.8 dBmVCurrent System Time: Thu Apr 16 08:46:51 2020System Up Time: 00:17:20&nbsp;&nbsp;&nbsp;

Forum Discussion

Devices losing connection with c6300 repeatedly

6 Replies