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

Forum Discussion

theilluminati23's avatar
theilluminati23
Follower
Dec 17, 2019

C7800 Cable connection problem

I woke up one day and had no internet.  ISP tech support has been less than helpful.  Here is the event log. Firmware is 3.01.43. Any help is appreciated. 

 

TimePriorityDescription
2019-12-17, 05:58:19Error (4)Auth Reject - Permanent Authorization Failure;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Notice (6)TLV-11 - unrecognized OID;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Error (4)Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Error (4)Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Error (4)Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Error (4)Missing BP Configuration Setting TLV Type: 17.4;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Error (4)Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Error (4)Missing BP Configuration Setting TLV Type: 17.2;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Error (4)Missing BP Configuration Setting TLV Type: 17.1;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Warning (5)DHCP WARNING - Non-critical field invalid in response ;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:12Notice (6)Honoring MDD; IP provisioning mode = IPv42019-12-17, 05:58:09Critical (3)No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:02Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:33Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:33Critical (3)SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:32Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:32Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:20Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:20Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:20Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:20Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:19Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:19Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:19Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:19Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:18Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:18Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:18Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:18Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:18Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:18Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:17Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:17Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:17Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:17Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:16Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:16Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:15Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1; 
Help Center Show/Hide Help Center

HTTP/1.1 302 Redirect Server: micro_httpd Cache-Control: no-cache Date: Thu, 01 Jan 1970 10:35:39 GMT Location: http://192.168.0.1/EventLog.asp Content-Type: text/html Connection: close X-Frame-Options: SAMEORIGIN X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block Content-Security-Policy: script-src 'self' 'unsafe-eval' 'unsafe-inline' Referrer-Policy: origin-when-crossorigin Set-Cookie: Secure; H

2 Replies

  • michaelkenward's avatar
    michaelkenward
    Guru - Experienced User
    Dec 19, 2019

    You might get better and quicker replies, and find other answers, over in the appropriate section for your device:

    Cable Modems & Routers

    No need to repost there, unless you want to – that will just clutter up the place with duplicated messages – but you might find advice related to your hardware.

    I have asked the Netgear moderator to move your message.

     

     

  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User
    Feb 14, 2020

    Have the ISP check the signal and line quality UP to the modem. 
    Be sure there are not 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. 

    theilluminati23 wrote:

    I woke up one day and had no internet.  ISP tech support has been less than helpful.  Here is the event log. Firmware is 3.01.43. Any help is appreciated. 

     

    TimePriorityDescription
    2019-12-17, 05:58:19Error (4)Auth Reject - Permanent Authorization Failure;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Notice (6)TLV-11 - unrecognized OID;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Error (4)Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Error (4)Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Error (4)Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Error (4)Missing BP Configuration Setting TLV Type: 17.4;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Error (4)Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Error (4)Missing BP Configuration Setting TLV Type: 17.2;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Error (4)Missing BP Configuration Setting TLV Type: 17.1;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:17Warning (5)DHCP WARNING - Non-critical field invalid in response ;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:12Notice (6)Honoring MDD; IP provisioning mode = IPv42019-12-17, 05:58:09Critical (3)No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:58:02Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:33Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:33Critical (3)SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:32Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:32Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:20Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:20Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:20Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:20Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:19Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:19Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:19Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:19Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:18Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:18Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:18Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:18Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:18Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:18Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:17Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:17Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:17Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:17Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:16Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:16Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1;2019-12-17, 05:57:15Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:94:ed:40:6d:00;CMTS-MAC=00:01:5c:88:a4:57;CM-QOS=1.1;CM-VER=3.1; 
    Help Center Show/Hide Help Center

    HTTP/1.1 302 Redirect Server: micro_httpd Cache-Control: no-cache Date: Thu, 01 Jan 1970 10:35:39 GMT Location: http://192.168.0.1/EventLog.asp Content-Type: text/html Connection: close X-Frame-Options: SAMEORIGIN X-Content-Type-Options: nosniff X-XSS-Protection: 1; mode=block Content-Security-Policy: script-src 'self' 'unsafe-eval' 'unsafe-inline' Referrer-Policy: origin-when-crossorigin Set-Cookie: Secure; H