NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
C7000v2 keeps loosing connection
Modem keeps loosing connection 3-5 times an hour. The nighthawk app, about every 20 seconds, show the following message "Your cable modem router is not connected or activate". I reset the modem about 4 times today and did a factory reset hoping it would improve. Nothing has worked, some help would be greatly appreciated.
9 Replies
Do you have a screensnip of the cable connections page and the event logs?
Start with removing any amplifiers, signal attenuators, or splitters from the coax.
From there check the line for kinks, damage, moisture in the line.
Check the connectors for improperly made ends, foil touching the copper coax line, bad/old/cheap connectors, or corroded connections. Replace them if you do.
If you can, simply connect the modem right where the coax comes into the home. This prevents wiring in the home from being the issue. And some ISP’s charge if the wiring issue is in the home. So this helps prevent this.The modem is connected directly to the cable that leads outside. I check the cables and there are no wear and tear. They look fine to me.
I get the following code now
WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE
but before the above I would get the following:
No Ranging Response received - T3 time-out;
WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:N/A) - Reason:INIT
WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INIT
SYNC Timing Synchronization failure - Failed to acquire FEC framing;
power logs are as follows from the attachment
attachment
Got the cable connections page but need the event logs. Not just the "logs".
The event logs show the cable connections page issues over a longer period. the cable connections page is just a quick snap shot from when you opened the page.
It looks clear today. You initially had a few requests from the cmts to reset/reboot it on the 7/10 date. "thats the docsdevresetnow" notice.
When it first boots up, its normal to see a couple sync/timing errors but not once its running.
