C7000-100NAS randomly drops internet connection

[ezicefield]

Hello,

My C7000-100NAS modem seems to randomly drop it's Comcast connection. This happen on 2.4 ghz, 5 ghz, and wired connections. There is no pattern, however the dropped connection usually lasts 2-5 minutes. When this happens, using the Netgear Genie is useless, it just stalls when trying to connect. Connecting to the IP of the modem works fine to reach the admin page. When the connection drops, the cable connection report on the C7000-100NAS shows the connection is good, 20x4 bonding. Other times, it reports the connection is offline.

I've been on the phone with Comcast, and they are not seeing anything wrong with the line, and no firmware updates are needed or available.

I see there are many reports of this same behavior with this model. The Amazon page is littered with them. I wish I had seen these reports before buying this pricey peice of equipment. I am hoping Netgear has a resolution. Of course the compimentary support period ended like 10 days ago, which is another source of frustration with this product.

Any help would be appreciated. Thanks.

[vkdelta]

Please PM me on this topic.

we are aware of some resets done by the ISP for specific customers.

[RickG53]

Do you have any information about how to stop these annoying interuptions of interrnet access through the C3700 router/modem? Mine has been doing this and I would like to fix it if possible.

Thank you

[vkdelta]

Pls post your Event log and power levels form the GUI here. Let me have a look at it.

[Lurkios]

Having the same issue here. One computer plugged into the router is fine, but 2 or 3 and it starts dropping packets for a few seconds every few minutes. Comcast as well.

Any word on the fix?

[rmacbeth]

I am having the same problem with the C7000 router at one of my accounts it has droped connections with Comcast the past few days and one other issue is when they (the account that this is at) por the router it lost all the config and came up as a new unit.  This should have never happen.  Had to come in and reconfig the C7000 to get them back up on wireless.

Here is my event log:

Time Priority Description
2016-2-20, 16:21:13 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-20, 16:36:22 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-20, 23:23:14 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-20, 23:38:21 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-21, 00:08:33 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:2) - Reason:INTERFERENCE
2016-2-21, 00:23:40 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-21, 00:38:48 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-21, 00:53:56 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-21, 01:09:03 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-21, 01:39:16 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-21, 02:09:28 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:2) - Reason:INTERFERENCE
2016-2-21, 02:39:39 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-21, 05:25:26 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:2) - Reason:INTERFERENCE
2016-2-21, 05:40:34 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-21, 07:26:06 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:2) - Reason:INTERFERENCE
2016-2-21, 07:41:13 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-21, 11:57:25 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:2) - Reason:INTERFERENCE
2016-2-21, 12:12:33 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-21, 12:57:49 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:2) - Reason:INTERFERENCE
2016-2-21, 13:12:55 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-21, 16:58:59 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:2) - Reason:INTERFERENCE
2016-2-21, 17:14:08 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-21, 21:00:12 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:2) - Reason:INTERFERENCE
2016-2-21, 21:15:21 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-21, 21:45:32 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:2) - Reason:INTERFERENCE
2016-2-21, 22:00:40 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-22, 00:16:21 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:2) - Reason:INTERFERENCE
2016-2-22, 00:31:26 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-22, 01:16:42 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:2) - Reason:INTERFERENCE
2016-2-22, 01:31:48 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-22, 03:02:16 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:2) - Reason:INTERFERENCE
2016-2-22, 03:32:28 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-22, 07:33:34 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:2) - Reason:INTERFERENCE
2016-2-22, 07:48:43 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-22, 08:18:55 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:2) - Reason:INTERFERENCE
2016-2-22, 08:49:06 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-22, 09:04:13 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:2) - Reason:INTERFERENCE
2016-2-22, 09:34:26 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-22, 09:49:33 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-2-22, 10:27:23 Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE

Also here are my power levels:

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 7 693000000 Hz 4.4 dBmV 39.7 dB 19 0
2 Locked QAM256 1 657000000 Hz 3.9 dBmV 39.7 dB 103 0
3 Locked QAM256 2 663000000 Hz 4 dBmV 39.8 dB 90 37
4 Locked QAM256 3 669000000 Hz 4 dBmV 39.7 dB 108 82
5 Locked QAM256 4 675000000 Hz 4.1 dBmV 39.1 dB 124 120
6 Locked QAM256 5 681000000 Hz 4.4 dBmV 39.8 dB 52 0
7 Locked QAM256 6 687000000 Hz 4.5 dBmV 39.7 dB 13 0
8 Locked QAM256 8 699000000 Hz 4 dBmV 39.6 dB 4 0
9 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
10 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
11 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
12 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
13 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
14 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
15 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
16 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
17 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
18 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
19 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
20 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
21 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
22 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
23 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
24 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0

Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 16 5120 Ksym/sec 36400000 Hz 48.5 dBmV
2 Locked ATDMA 17 5120 Ksym/sec 29500000 Hz 49.5 dBmV
3 Locked ATDMA 18 5120 Ksym/sec 22600000 Hz 48.3 dBmV
4 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV

[DarrenM]

Hello Rmacbeth

Is the C7000 connected to a spllter if so try swapping cords from the TV to the modem or try removing the spliter and connecting the modem directly to the wall.

DarrenM

[rmacbeth]

This is a business and there is one splitter at the cable input and it splits off to a cable to the C7000 and a cable to an Arris box for there phone system and a two more cables to two different TV's that are used by customers.  All are needed for the business. Each cable run from the splitter is approx 65 feet copper clad Quad Coaxial RG-6 cables.  Are you saying that there is a problem with the splitter or one of the cable runs or what?

[Lurkios]

Had Comcast out for a look, they said the line is perfectly fine. Replaced the faulty Netgear device with another brand and it's operating perfectly. 2 days later my week old Netgear switch loses a port... I feel like we're slipping.

[DarrenM]

@rmacbeth

It possibly could be a splitter or the cable but they would have to come check those out to make sure.

DarrenM

[rmacbeth]

@DarrenM are you saying this because the event log had "INTERFERENCE" hits ? or was there other items like "power" logs that have you think that this is the problem.   They did not have this problem before I put in the C7000 Please help me understand why you think it is the splitter when they did not have these types of problems with the Netgear gateway that Comcast uses and they had to rent it each month.

Rich

[DarrenM]

I am just saying it could be a factor I have seen splittlers just go bad or cause issues a lot just wanted you to test and see if that is the issue or not.

DarrenM

[Drew2]

Same problem but with Time Warner

Next time you are bumped off-line

Access your router -> select advanced -> select administration -> open event log -> look for SYNC

Unfortunately they haven't been able to solve that issue - at least in my case

[SupaPig]

I have similar problems with my C7000 and it's now getting to the point where I may have to dump this device.  All I want is reliable internet.  I've got Time Warner and I don't think the problem is with them.  I'm a Network Engineer by trade and by no means does that make me "a "Netgear" expert, it does however mean I possess the ability to troubleshoot further and provide additional information.  I've had my fair share of crappy wireless devices along with excellent Enterprise class in Cisco, AeroHive, Juniper, Aruba etc.  I'm about to say "to heck with it" and spend $500-1k on an Enterprise device as I've wasted close to that on Linksys and Netgear devices over the years. 

The C7000 will randomly drop my internet connection for 60 seconds to 5 minutes.  Sometimes, it requires a complete reboot.  Sometimes it wakes up from being half dead and I need to do nothing.  However, the issues are sporatic but obvious and I would guess Netgear would be fully aware of this bug.  One second it will drop ICMP traffic to the internet but the C7000's interface tells me my "Cable Connection" is good and I can ping my LAN interface.  Then, it will stop responding to ICMP on it's LAN (internal RFC1918 address) interface but Internet traffic still passes fine.  For example, as I'm typing this, I can't ping my LAN interface but I can ping 8.8.8.8 without issue.  I just looked again and now my LAN interface responds to ICMP but internet is dead.  A few minutes later without doing anything, both start responding.  Either way, it's virtually impossible to blame Time Warner for this issue when the local LAN interface won't even respond to ICMP (randomly) and internet traffic responds fine.  It's also obviously not a weak wireless signal when I can pass sub 20ms packets to most destinations on the internet but not ping my LAN interface.  Bottom line, the C7000 displays such erradic behaviour it doesn't seem stable or this firmware release needs work.  Time Warners crappy rented "Technicolor", while having weak wireless signal, is at LEAST reliable.

Netgear needs to get on with a stable firmware release or lose customers.  Most people don't know how to properly troubleshoot an issue and for costing $200 plus, they shouldn't need to constantly "troubleshoot" what's becoming pretty evident as a firmware issue.  Word of mouth spreads and it reflects in reviews.

[Drew2]

Word does spread.  The Co I work for has stopped recomending Netgear for home offices.  That only impacts a dozen or so sales at best, but it's a pea shooter across the bow - lol

[dnevozhai]

@SupaPig well said!

Having the same issues.

[SupaPig]

Yeah, mine get worse as time goes on.  It isn't wireless coverage or signal overlap as I'm a Network Engineer by trade and know how to scan and scope interference issues.

As a good test or temp fix, if you want to see if you're having the same problems as I am (which is likely), when you have wireless related issues: FIRST, disconnect from your 5Ghz network either by disabling/re-enabling wireless or connect to your 2.4Ghz network THEN switch back to 5.  Either way, when you disconnect and reconnect from your 5Ghz network, it will (or mine does) connect and work fine for a period of time (10-15 min).  Some longer than others.  On occassion, I just have to power cycle the C7000 altogether. 

I went ahead and took an AeroHive AP which is enterprise class and placed it on a different frequency as the Netgear using the netgear as a local router and the AeroHive as an isolated extension but different network and BAM, the AeroHive works flawlessly as a wireless router while the Netgear (which is in the same room) continues to flake out wirelessly and sometimes as a modem. 

It just can't seem to handle any kind of small error correction.  Instead, it flakes out for all clients on the 5Ghz network without correcting whatever issue it's having until it reinitiates that connection either by disconnecting the client or restarting the C7000.  Pretty bad bug IMO.

[rmacbeth]

@SupaPig It is still happening with this account--- I have wired most of the main computers on Ethernet GB backbone so there are only a few that will use the 5Ghz along with customers will use the 2.4Ghz. Looking at the logs it is doing just like you were talking about. I have been working with Netgear support for approx. 2+ years on my home base system (started out with R700 than R7500 and now R7800) due to many issues with code and hardware. The current one that I am now using R7800 has been more stable but it has it issues that we are still working with. If this account were tasking the 5Ghz they would be complaining more. Since for the most part they are not noticing the errors due to them not using their laptops, etc. on a ongoing basics. They are using them between patients they are working on for updating info about what they are doing with each patient.  This does not let Netgear off the hook to fix the code.

[bcmorrison]

I'm having the same issues as everyone else. Only had this modem/router for 1 week and it is complete crap. Internet is constantly going down and affects both wired and wireless devices. Often have to reboot the router. Has anyone found a resolution? Or a better replacement? I'm on TWC

[DarrenM]

Hello bcmorrison 

Are you able to go into the logs of the C7000 when it drops internet to see what errors are happening?

DarrenM

[Robotaz]

I am currently going through a debacle with Time Warner and a C7000 as well.

Unfortunately, I have very little networking expertise.  I've honestly never needed any.  Everything seemed to be fine and TWC upgraded their system to provide much faster speeds.  Immediately I was getting drops, wild speed variations, etc.

Currently I have a connection, but my upstream LED is blinking.  I expect to have continued dropping until a tech can come out next week.  But, I'm really worried that it's something on my end; namely this C7000.

Here is my log.  Any feedback at all will help me tremendously.

Time Priority Description 2016-5-29, 21:32:32 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:41 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:42 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:46 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:46 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:49 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:50 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:50 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:51 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:52 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:52 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:54 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:32:54 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:37:18 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:37:31 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:37:32 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:37:46 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:38 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:45 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:40:36 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:37 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:43 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 21:47:47 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.1;CM-VER=3.0; 1970-1-1, 00:00:38 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:41 Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INIT 1970-1-1, 00:00:41 Notice (6) WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:N/A) - Reason:INIT 1970-1-1, 00:00:46 Notice (6) Overriding MDD IP initialization parameters; IP provisioning mode = IPv6 1970-1-1, 00:00:56 Warning (5) ToD request sent - No Response received;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:57 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.1;CM-VER=3.0; 1970-1-1, 00:00:57 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.1;CM-VER=3.0; 2016-5-29, 22:32:46 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 22:32:53 Notice (6) Overriding MDD IP initialization parameters; IP provisioning mode = IPv6 2016-5-29, 22:33:07 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.1;CM-VER=3.0; 2016-5-29, 22:33:07 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.1;CM-VER=3.0; 2016-5-29, 22:33:13 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 22:33:18 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.0;CM-VER=3.0; 2016-5-29, 22:33:22 Notice (6) Overriding MDD IP initialization parameters; IP provisioning mode = IPv6 2016-5-29, 22:33:32 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.1;CM-VER=3.0; 2016-5-29, 22:33:32 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.1;CM-VER=3.0; 2016-5-29, 22:35:05 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:f4:30:08;CMTS-MAC=00:01:5c:64:5a:53;CM-QOS=1.1;CM-VER=3.0;

Procedure Status Comment Acquire Downstream Channel 729000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enabled BPI+ IP Provisioning Mode IPv6 Only ipv6Only(1)

Downstream Bonded Channels

Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 15 729000000 Hz -0.1 dBmV 41 dB 0 0 2 Locked QAM256 1 645000000 Hz -0.1 dBmV 39 dB 0 0 3 Locked QAM256 2 651000000 Hz -0.6 dBmV 39 dB 0 0 4 Locked QAM256 3 657000000 Hz -1.3 dBmV 39.6 dB 0 0 5 Locked QAM256 4 663000000 Hz -2.1 dBmV 39.6 dB 0 0 6 Locked QAM256 12 669000000 Hz -1.7 dBmV 39.1 dB 0 0 7 Locked QAM256 5 675000000 Hz -1.9 dBmV 38.5 dB 0 0 8 Locked QAM256 6 681000000 Hz -1.3 dBmV 39.9 dB 0 0 9 Locked QAM256 7 687000000 Hz -0.4 dBmV 40.1 dB 0 0 10 Locked QAM256 8 693000000 Hz -0.3 dBmV 39.9 dB 0 0 11 Locked QAM256 9 699000000 Hz -0.5 dBmV 40.2 dB 0 0 12 Locked QAM256 10 705000000 Hz -0.6 dBmV 40.4 dB 0 0 13 Locked QAM256 11 711000000 Hz -0.9 dBmV 40.4 dB 0 0 14 Locked QAM256 13 717000000 Hz -0.7 dBmV 40.4 dB 0 0 15 Locked QAM256 14 723000000 Hz -0.3 dBmV 40.7 dB 0 0 16 Locked QAM256 16 735000000 Hz 0.3 dBmV 40.5 dB 0 0 17 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 18 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 19 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 20 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 21 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 22 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 23 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 24 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0

Upstream Bonded Channels (Partial Service)

Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 14 5120 Ksym/sec 24200000 Hz 52 dBmV 2 Not Locked Unknown 13 0 Ksym/sec 19400000 Hz 0.0 dBmV 3 Locked ATDMA 15 5120 Ksym/sec 30600000 Hz 51.9 dBmV 4 Locked TDMA 16 2560 Ksym/sec 37000000 Hz 52 dBmV 5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV

Help CenterShow/Hide Help

[bcmorrison]

TWC came back out and replaced every connector on the wires coming into the house and it seems to have resolved the issues. They said the signal levels coming into the house were too high and had to put a splitter on the cable even though I only have the 1 device for coax.

[mbrandonlee]

I'm having the same issues with the same model on TWC. They're going to have a tech come in to look at the line and everything, but the signal is within spec. I'm having the SYNC issues in my logs as well.

I'm wondering what other routers to consider that are compatible and comparable in features and power.

Here are my logs: https://dl.dropboxusercontent.com/u/10373192/Screen%20Shot%202016-06-14%20at%209.26.48%20PM.png

https://dl.dropboxusercontent.com/u/10373192/Screen%20Shot%202016-06-14%20at%209.27.05%20PM.png

[DC_UK]

Getting the same issues; is there a fix for this now? Does anyone know the latest firmware #

[Drew2]

Nothing but crickets from Netgear on the Sync problem