NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
duffz
Aug 28, 2023Aspirant
Nighthawk C7000V2 - Google TCL TV Connects, but won't get Internet Access, while other Devices will.
I have a Nighthawk C7000v2 - https://www.netgear.com/support/product/c7000v2
Firmware Version 
V1.03.08
Hey Guys,
Maybe someone can help, I am going crazy trying to get my new Google TCL TV to connect to the internet.
Anytime I try to connect the TV to my wifi, or even plug directly into the TV with Ethernet cord, it will connect, but then say "No internet access". At first I thought maybe there was a problem with the TV, but I tried turning my Iphone into a hotspot, and it the TV connected right away with successful internet access.
Since it connected instantly online with my hotspot, I am lead to believe it has something to do with my router? Its very weird to me that it still says "no internet connection" even when being plugged directly in from my router, to the TV.
If I use the TV command "check internet connection" - it comes back as "Router connection successful", then the 2nd step says "internet connection failed".
I am using a Netgear c7000v2 router. I have disabled "Access control", and enabled "Allow guests to see each other and access my local network" as I found on a google post to try. Still nothing. I've changed everything inside of my router that I thought would have an effect on it making the TV get internet access, but nothing.
I have a different Roku TV, an Iphone, Nintendo system, and they all connect to the wifi with no problem. And all of my wired connections connect without issue also. My signal strength is Excellent, and I have good internet.
I really don't understand what could be wrong, but it only makes sense that something inside the routing is not allowing it to connect to the internet. Anyone have some more ideas for me to try with the router?
5 Replies
- FURRYe38Guru - Experienced UserWhat channel configurations are currently set on the router? 
 Any Wifi Neighbors near by? If so, how many?Please post a copy and paste of the modems connection status and event log page. 
 https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-modem-modem-router
 https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-modem-router- duffzAspirantStartup Procedure Procedure Status Comment Acquire Downstream Channel 627000000 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 21 627000000 Hz -3.2 dBmV 37.8 dB 0 0 2 Locked QAM256 1 507000000 Hz -0.4 dBmV 38.8 dB 0 0 3 Locked QAM256 2 513000000 Hz -0.9 dBmV 37.5 dB 0 0 4 Locked QAM256 3 519000000 Hz -0.5 dBmV 37.3 dB 0 0 5 Locked QAM256 4 525000000 Hz -1 dBmV 39.3 dB 0 0 6 Locked QAM256 5 531000000 Hz -0.7 dBmV 38.8 dB 0 0 7 Locked QAM256 6 537000000 Hz -0.5 dBmV 37.2 dB 0 0 8 Locked QAM256 7 543000000 Hz -1.2 dBmV 37.1 dB 0 0 9 Locked QAM256 8 549000000 Hz -1.3 dBmV 35.6 dB 0 0 10 Locked QAM256 9 555000000 Hz -1.7 dBmV 37.5 dB 0 0 11 Locked QAM256 10 561000000 Hz -1.5 dBmV 38.3 dB 0 0 12 Locked QAM256 11 567000000 Hz -2.5 dBmV 38.7 dB 0 0 13 Locked QAM256 12 573000000 Hz -2.7 dBmV 38.6 dB 0 0 14 Locked QAM256 13 579000000 Hz -2.7 dBmV 38.2 dB 0 0 15 Locked QAM256 14 585000000 Hz -2.7 dBmV 38.5 dB 0 0 16 Locked QAM256 15 591000000 Hz -3.2 dBmV 37.3 dB 0 0 17 Locked QAM256 16 597000000 Hz -3.4 dBmV 37.1 dB 0 0 18 Locked QAM256 17 603000000 Hz -2.7 dBmV 37.8 dB 0 0 19 Locked QAM256 18 609000000 Hz -2.8 dBmV 37.4 dB 0 0 20 Locked QAM256 19 615000000 Hz -2.9 dBmV 38 dB 0 0 21 Locked QAM256 20 621000000 Hz -3.5 dBmV 37.2 dB 0 0 22 Locked QAM256 22 633000000 Hz -2.7 dBmV 37.2 dB 0 0 23 Locked QAM256 23 639000000 Hz -3.1 dBmV 37.6 dB 0 0 24 Locked QAM256 24 645000000 Hz -2.8 dBmV 38.2 dB 0 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 5 5120 Ksym/sec 35600000 Hz 45.5 dBmV 2 Locked ATDMA 3 5120 Ksym/sec 22800000 Hz 43.5 dBmV 3 Locked ATDMA 6 2560 Ksym/sec 40400000 Hz 47.8 dBmV 4 Locked ATDMA 2 5120 Ksym/sec 16300000 Hz 42 dBmV 5 Locked ATDMA 4 5120 Ksym/sec 29200000 Hz 44 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 EVENT LOG: 2023-8-28, 14:55:44 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:N/A) - Reason:INTERFERENCE 2023-8-28, 14:52:29 Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:2) - Reason:INTERFERENCE 1970-1-1, 00:00:47 Notice (6) Overriding MDD IP initialization parameters; IP provisioning mode = IPv6 1970-1-1, 00:00:41 Notice (6) WiFi Interface [wl1] set to Channel 48 (Side-Band Channel:N/A) - Reason:INIT 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:39 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:44 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:01:5c:8e:a6:84;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=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2023-8-22, 10:41:28 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:01:5c:8e:a6:84;CM-QOS=1.1;CM-VER=3.0; 1970-1-1, 00:00:46 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:01:5c:8e:a6:84;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:39 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:00:42 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:01:5c:8e:a6:84;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=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2023-8-21, 20:34:17 Critical (3) Resetting the cable modem due to docsDevResetNow 1970-1-1, 00:00:38 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 2023-8-21, 20:23:13 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:01:5c:8e:a6:84;CM-QOS=1.0;CM-VER=3.0; 2023-8-21, 20:23:04 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:01:5c:8e:a6:84;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:02:42 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:02:41 Critical (3) No UCDs Received - Timeout;;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:02:22 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:02:21 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:02:20 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:02:19 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:02:18 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:02:17 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:02:16 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:02:15 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:02:14 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:02:13 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:02:12 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:02:10 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:01:50 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:01:48 Critical (3) No UCDs Received - Timeout;;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:01:31 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:01:19 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:01:18 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:01:09 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:01:08 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:01:07 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 1970-1-1, 00:01:06 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=cc:40:d0:c3:6b:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Thank you for the help. Please let me know if I didn't paste that correctly. WIFI neighbors, there are about 2-3 neighbors that show up with medium strength. I have also tried setting up a guest network to connect to, but it also still has no internet. - FURRYe38Guru - Experienced UserGood paste. Power looks ok. With in specs. I see lots of Criticals in the event log that can point to line issues from the ISP. Any Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP. Indicates a signal issue on the ISP line up to the modem. Have the ISP check the signal and line quality UP to the modem. Be sure the ISP provisions the modem correctly. 
 Be sure there are no coax cable line splitters in the between the modem and ISP service box.
 Be sure your using good quality RG6 coax cable up to the modem.
 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, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.
 Be sure to power OFF the modem for 1 minute then back ON.
 https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Modems/m-p/1530376#M12853
 https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
 https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
 https://highspeed.tips/docsis-events/What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and 40 to 48 channel on 5Ghz. 
 Any Wifi Neighbors near by? If so, how many?