NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
cshep5528
Dec 24, 2022Star
CBR750 not working with Comcast/XF
Having the same issue in Denver thanks to ISP "upgrades" from comcast. Just messaged Blanca_O . Keep me posted on progress please.
cshep5528
Jan 06, 2023Star
Another 5 hours on the phone with xfinity and netgear this week. Router cut out 3 times. Does anyone know how to formally request a refund? I am also planning to submit a request with the state AG for false advertising.
- FURRYe38Jan 07, 2023Guru - Experienced User
We need the following from you:
PM me the MAC address and serial number from the CBR.
Please enable debug logs on the CBRs web page under 192.168.1.1/debug.htm
Enable WAN/LAN capture as well.
Please post the following here in the forum:
FW version on the CBR.
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-routerThe ISP made changes to there speed tier program with out letting users know. They removed support for 1Gb and split the tier to 800Mpbs and 1.2Gb which seems that in some areas, the ISP is not supporting the CBR on the 1.2Gb tier. So some of this is ON the ISP. The CBR had been working fine up to this point until the ISP made changes. SInce the CBR only has 1000Mpbs LAN ports, doesn't make sense to have the 1.2Gb speed since you'll never see much over 900Mbps on the LAN side thru the CBR750. The CBR works as advertised on the 800Mbps speed tier.
cshep5528 wrote:
Another 5 hours on the phone with xfinity and netgear this week. Router cut out 3 times. Does anyone know how to formally request a refund? I am also planning to submit a request with the state AG for false advertising.
- FURRYe38Jan 11, 2023Guru - Experienced User
Please post a copy and paste of the modems connection status and event log page from the CBR.
- cshep5528Jan 12, 2023Star
mePriorityDescriptionJan 09 2023 16:50:54Alert (2)CM Certificate ErrorJan 09 2023 16:50:54Alert (2)CM Certificate ErrorJan 09 2023 16:50:54Alert (2)CM Certificate ErrorJan 09 2023 16:50:54Alert (2)CM Certificate ErrorJan 09 2023 16:50:54Alert (2)CM Certificate ErrorJan 09 2023 16:50:54Alert (2)CM Certificate ErrorJan 09 2023 16:50:54Alert (2)CM Certificate ErrorJan 09 2023 17:35:14Critical (3)No Ranging Response received - T3 time-outJan 10 2023 16:00:36Alert (2)CM Certificate ErrorJan 10 2023 16:32:44Critical (3)No Ranging Response received - T3 time-outJan 10 2023 19:47:07Alert (2)CM Certificate ErrorJan 10 2023 21:14:21Critical (3)No Ranging Response received - T3 time-outJan 11 2023 09:59:43Critical (3)SYNC Timing Synchronization failure - Loss of SyncJan 11 2023 09:59:44Notice (6)CM-STATUS message sent. Event Type Code: 21Jan 11 2023 09:59:48Warning (5)Lost MDD TimeoutJan 11 2023 10:00:31Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time outJan 11 2023 10:09:40Error (4)Missing Mandatory MDD TLV on primary DS ChannelJan 11 2023 10:23:11Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Jan 11 2023 10:23:11Notice (6)TLV-11 - unrecognized OIDJan 11 2023 10:23:11Critical (3)Config File Rejected due to Invalid or Unexpected TLV 11Jan 11 2023 10:23:16Warning (5)RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRWJan 11 2023 10:23:25Alert (2)CM Certificate ErrorJan 11 2023 10:28:14Critical (3)SYNC Timing Synchronization failure - Loss of SyncJan 11 2023 10:28:16Notice (6)CM-STATUS message sent. Event Type Code: 21Jan 11 2023 10:28:19Warning (5)Lost MDD TimeoutJan 11 2023 10:29:06Critical (3)No Ranging Response received - T3 time-outJan 11 2023 10:29:09Notice (6)CM-STATUS message sent. Event Type Code: 16Jan 11 2023 10:29:09Critical (3)No Ranging Response received - T3 time-outJan 11 2023 10:29:11Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time outJan 11 2023 10:29:11Critical (3)No Ranging Response received - T3 time-outJan 11 2023 10:29:13Notice (6)CM-STATUS message sent. Event Type Code: 6Jan 11 2023 10:29:13Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time outJan 11 2023 10:29:14Critical (3)No Ranging Response received - T3 time-outJan 11 2023 10:29:17Notice (6)CM-STATUS message sent. Event Type Code: 5Jan 11 2023 10:29:39Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Jan 11 2023 10:29:39Notice (6)TLV-11 - unrecognized OIDJan 11 2023 10:29:39Critical (3)Config File Rejected due to Invalid or Unexpected TLV 11Jan 11 2023 10:29:41Warning (5)RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRWJan 11 2023 10:29:50Alert (2)CM Certificate ErrorJan 11 2023 10:43:06Notice (6)DS profile config update. DS Chan ID: 193.Jan 11 2023 10:53:50Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1Jan 11 2023 10:53:50Notice (6)TLV-11 - unrecognized OIDJan 11 2023 10:53:50Critical (3)Config File Rejected due to Invalid or Unexpected TLV 11Jan 11 2023 10:53:55Warning (5)RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRWJan 11 2023 10:54:04Alert (2)CM Certificate ErrorJan 11 2023 20:02:30Critical (3)No Ranging Response received - T3 time-out