NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CBR750 losing connection
Two weeks ago my cable line was cut. Comcast came out and fixed on a Sunday, also redid part of the line back to pole. Everything worked great for a few days. On Thursday, Comcast went down for a ...
Please post a copy and paste of the modems event log page.
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-modem-router
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.
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?article=24311
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
They didn't do a good enough job of fixing the line.
Your power levels are all over the place, you have errors in the line, and your upstream is way out of spec.
They need to come out and check their work.
Have the ISP check the signal and line quality UP to the modem. Be sure the ISP provisions the modem correctly.
They checked after the repair and said it was good. Comcast today can see my modem
Be sure there are no coax cable line splitters in the between the modem and ISP service box. None
Be sure your using good quality RG6 coax cable up to the modem. yes
Be sure to power OFF the modem for 1 minute then back ON. done repeatedlyEvent log was blank
Logs:
[DHCP IP: (192.168.1.12)] to MAC address 34:3E:A4:1E:95:69, Thursday, Sep 22,2022 11:06:54
[DHCP IP: (192.168.1.12)] to MAC address 34:3E:A4:1E:95:69, Thursday, Sep 22,2022 11:06:32
[DHCP IP: (192.168.1.24)] to MAC address 50:51:A9:8E:37:47, Thursday, Sep 22,2022 11:06:27
[Admin login] from source 192.168.1.33, Thursday, Sep 22,2022 11:05:32
[DHCP IP: (192.168.1.22)] to MAC address 34:7E:5C:15:75:6E, Thursday, Sep 22,2022 11:05:32
[DHCP IP: (192.168.1.46)] to MAC address 94:9F:3E:43:D9:50, Thursday, Sep 22,2022 11:05:31
[DHCP IP: (192.168.1.34)] to MAC address 7E:8B:5D:DC:DF:D3, Thursday, Sep 22,2022 11:04:56
[Internet connected] IP address: 73.107.37.164, Thursday, Sep 22,2022 11:04:28
[Internet disconnected] Thursday, Sep 22,2022 11:04:27
[DHCP IP: (192.168.1.24)] to MAC address 50:51:A9:8E:37:47, Thursday, Sep 22,2022 11:04:23
[DHCP IP: (192.168.1.25)] to MAC address 94:9F:3E:61:9D:E8, Thursday, Sep 22,2022 11:04:15
[DHCP IP: (192.168.1.17)] to MAC address 94:9F:3E:A3:3E:1E, Thursday, Sep 22,2022 11:03:17
[DHCP IP: (192.168.1.15)] to MAC address 94:9F:3E:83:16:24, Thursday, Sep 22,2022 11:03:16
[DHCP IP: (192.168.1.45)] to MAC address 34:7E:5C:72:23:E3, Thursday, Sep 22,2022 11:03:15
[DHCP IP: (192.168.1.6)] to MAC address 78:28:CA:1F:97:28, Thursday, Sep 22,2022 11:03:14
[DHCP IP: (192.168.1.5)] to MAC address 78:28:CA:1F:96:40, Thursday, Sep 22,2022 11:03:14
[DHCP IP: (192.168.1.34)] to MAC address 7E:8B:5D:DC:DF:D3, Thursday, Sep 22,2022 11:02:41
[DHCP IP: (192.168.1.24)] to MAC address 50:51:A9:8E:37:47, Thursday, Sep 22,2022 11:01:57
[DHCP IP: (192.168.1.12)] to MAC address 34:3E:A4:1E:95:69, Thursday, Sep 22,2022 11:00:10
[DHCP IP: (192.168.1.24)] to MAC address 50:51:A9:8E:37:47, Thursday, Sep 22,2022 11:00:00
[DHCP IP: (192.168.1.21)] to MAC address 34:86:5D:30:FA:24, Thursday, Sep 22,2022 10:59:15
[DHCP IP: (192.168.1.24)] to MAC address 50:51:A9:8E:37:47, Thursday, Sep 22,2022 10:57:46
[DHCP IP: (192.168.1.12)] to MAC address 34:3E:A4:1E:95:69, Thursday, Sep 22,2022 10:56:32
[DHCP IP: (192.168.1.24)] to MAC address 50:51:A9:8E:37:47, Thursday, Sep 22,2022 10:55:23
[DHCP IP: (192.168.1.34)] to MAC address 7E:8B:5D:DC:DF:D3, Thursday, Sep 22,2022 10:54:09
[DHCP IP: (192.168.1.24)] to MAC address 50:51:A9:8E:37:47, Thursday, Sep 22,2022 10:53:01
[DHCP IP: (192.168.1.12)] to MAC address 34:3E:A4:1E:95:69, Thursday, Sep 22,2022 10:52:36What FW version is loaded on the CBR and RBS?
Can you enable email logging? https://community.netgear.com/t5/Orbi-WiFi-6-AX-and-WiFi-6E-AXE/Enable-Email-Logging-and-Router-Reboots/m-p/2231485/highlight/true#M34055
imePriorityDescriptionSep 22 2022 10:20:55Critical (3)Config File Rejected due to Invalid or Unexpected TLV 11Sep 22 2022 10:20:55Critical (3)Config File Rejected due to Invalid or Unexpected TLV 11Sep 22 2022 10:20:55Critical (3)Config File Rejected due to Invalid or Unexpected TLV 11Sep 22 2022 10:20:55Critical (3)Config File Rejected due to Invalid or Unexpected TLV 11Sep 22 2022 10:20:55Critical (3)Config File Rejected due to Invalid or Unexpected TLV 11Sep 22 2022 10:20:55Critical (3)Config File Rejected due to Invalid or Unexpected TLV 11Sep 22 2022 10:20:55Critical (3)Config File Rejected due to Invalid or Unexpected TLV 11Sep 22 2022 10:20:55Critical (3)Config File Rejected due to Invalid or Unexpected TLV 11Sep 22 2022 10:20:55Critical (3)Config File Rejected due to Invalid or Unexpected TLV 11Sep 22 2022 10:20:56Warning (5)RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRWSep 22 2022 10:20:59Critical (3)No Ranging Response received - T3 time-outSep 22 2022 10:21:02Critical (3)SYNC Timing Synchronization failure - Loss of SyncSep 22 2022 10:21:03Critical (3)No Ranging Response received - T3 time-outSep 22 2022 10:21:03Critical (3)SYNC Timing Synchronization failure - Loss of SyncSep 22 2022 10:21:04Critical (3)No Ranging Response received - T3 time-outSep 22 2022 10:21:04Critical (3)SYNC Timing Synchronization failure - Loss of SyncSep 22 2022 10:21:06Critical (3)No Ranging Response received - T3 time-outSep 22 2022 10:21:08Critical (3)SYNC Timing Synchronization failure - Loss of SyncSep 22 2022 10:21:09Critical (3)No Ranging Response received - T3 time-outSep 22 2022 10:21:10Warning (5)Lost MDD TimeoutSep 22 2022 10:21:10Critical (3)No Ranging Response received - T3 time-outSep 22 2022 10:21:11Critical (3)SYNC Timing Synchronization failure - Loss of SyncSep 22 2022 10:21:12Critical (3)No Ranging Response received - T3 time-outSep 22 2022 10:21:12Critical (3)SYNC Timing Synchronization failure - Loss of SyncSep 22 2022 10:21:13Critical (3)No Ranging Response received - T3 time-outSep 22 2022 10:21:15Warning (5)Lost MDD TimeoutSep 22 2022 10:21:16Critical (3)No Ranging Response received - T3 time-outSep 22 2022 10:21:17Critical (3)SYNC Timing Synchronization failure - Loss of SyncSep 22 2022 10:21:19Critical (3)No Ranging Response received - T3 time-outSep 22 2022 10:21:20Critical (3)SYNC Timing Synchronization failure - Loss of SyncSep 22 2022 10:21:22Critical (3)No Ranging Response received - T3 time-outSep 22 2022 10:21:26Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time outSep 22 2022 10:21:27Critical (3)No Ranging Response received - T3 time-outSep 22 2022 10:21:29Critical (3)SYNC Timing Synchronization failure - Loss of SyncSep 22 2022 10:21:30Critical (3)No Ranging Response received - T3 time-outSep 22 2022 10:21:33Critical (3)SYNC Timing Synchronization failure - Loss of SyncSep 22 2022 10:21:55Warning (5)Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expiredSep 22 2022 10:21:55Warning (5)TCS Partial ServiceSep 22 2022 10:21:56Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time outSep 22 2022 10:22:11Critical (3)No Ranging Response received - T3 time-outSep 22 2022 10:44:07Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Sep 22 2022 10:44:07Notice (6)TLV-11 - unrecognized OIDSep 22 2022 10:44:07Critical (3)Config File Rejected due to Invalid or Unexpected TLV 11Sep 22 2022 10:44:11Warning (5)RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRWSep 22 2022 10:45:08Warning (5)Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expiredSep 22 2022 10:45:08Warning (5)TCS Partial ServiceSep 22 2022 10:45:14Alert (2)CM Certificate ErrorSep 22 2022 10:54:51Critical (3)No Ranging Response received - T3 time-out
You have lots of T3 Criticals that the ISP should review and help resolve.
Please enable the email logging to see if this changes the behavior any as well.
Firmware Version
V4.6.5.8_2.0.54
