Netgear CM-1000 Reboots at Same Time Every Night / Suspect Recent Firmware Update.
A week ago, I and at least two other Cox subscribers with Netgear CM-1000 modems began experiencing NIGHTLY modem resets -- multiple times per night, all at exactly the same time. Two of us are in San Diego, one in AZ. But the real issues appears to be the model of modem AND a recent (I suspect within the last 6-7 days) problematic firmware update. I have a hardcopy modem status page printed on 8/5/19 indicating firmware rev v3.01.04. CURRENT firmware rev is v5.01.04. WHEN was this revision pushed out?3.4KViews0likes1CommentNetgear Orbi CBR750 Wi-Fi 6 DOCSIS 3.1 Mesh Wi-Fi Cable Modem Router - won't bond to more than 4-upstream bonded channels
I spoke to Cox sales & tech support prior to purchase of the CBR750 to verify this device is certified to work on the Cox network. - The Cox website actually features the modem-COX CBR750 page I have reached out though Facebook messenger, andcox.help@cox.com The issue is that we had a scheduled ‘upgrade’ to our service area in Apri 22, 2021 Our service areahad an additional 4-upstream channels added to allow for the full ‘8’ — the Cox tech verified today that his field modem was getting the full 8 — the above The CBR750is only locking Channel ID 1-4 The Cox webpage (link above) clearly states for the CBR750:“32x8 channel bonding” I need someone in Cox engineering to determine that the current modem firmware (V1.01.08.)does not allow for all 8 - upstream bonded channels with Cox cable.And or that my modem is correctly provisioned with theappropriate coding to allow for the full 32x8 channel bonding. I cannot personally provision these settings—or modify firmware. Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 4 5120 Ksym/sec 16900000 Hz 40.0 dBmV 2 Locked ATDMA 3 5120 Ksym/sec 23500000 Hz 42.0 dBmV 3 Locked ATDMA 2 5120 Ksym/sec 29900000 Hz 43.8 dBmV 4 Locked ATDMA 1 5120 Ksym/sec 36300000 Hz 43.3 dBmV 5 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV 6 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV 7 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV 8 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV ROUTER INFORMATION Hardware Version CBR750 Orbi Firmware Version V3.2.18.2_1.4.14 CM Firmware Version V1.01.08 CM Serial Number 67A109XXXXXXX CM Certificate Installed Facebook Messenger replies from Cox: "Hello XXXX. My name is Allison and I will be assisting you while Maria is away. We value you as a customer and apologize that you are experiencing issues with your modem upload bond channels. After reviewing your account, your account shows that your modem's current firmware version is V1.01.08. We are unable to send anything to you confirming this, but I will provide additional information on getting to this information on your own shortly. Currently, your modem is bonding to 4 upstream channels. We would have to refer you to the manufacturer of the modem to see why all 8 channels on your modem is not working. You can also attempt to log into your modem on your own by going to http://routerlogin.net and use the default username "admin" and password of "password" to login to your router directly to troubleshoot this. Here, you will also be able to find the latest firmware that is on your modem. We are unable to troubleshoot 3rd party equipment through this channel. However, for additional support on this you would have to reach out to NETGEAR or you can add our Advance support Cox Complete Care which $9.99 a month, they can remotely access your computer and assist you with diagnosing your equipment. -Allison" /////// I apologize XXXX, there is no other team I can get you over to, besides the options I've already provided. I understand this is not the answers you are seeking, however those are the only two options I can provide to you. You can also reach out to our Technical Support department at 800-234-3993, if you wanted to speak to someone directly about this. -Allison /////// I definitely understand your frustrations XXXX. I'm sorry we could not be of more help. Please feel free to download our free Cox App to manage your account. If we can ever be of additional support, please reach out. We are online 24 hours a day, 7 days a week. -Allison Apple Devices - https://itunes.apple.com/us/app/cox-connect/id415894489?mt=8 Android Devices - https://play.google.com/store/apps/detailsid=com.cox.android.mobileconnect&hl=enSolved2.7KViews0likes7Commentsnetgear c7000 firmware upgrades not pushed through???
I received an email from netgear stating security breaches and firmware patches being issued. I am running v1.01.18, since then two firmware patches have been released v1.01.23 and v1.01.28. v1.01.28 has been approved by cox via netgears website but when I call they have no knowledge of either firmware updates or how to manually push through????2.6KViews0likes5CommentsHow to update C6250-100NAS router firmware?
According tohttps://kb.netgear.com/000036375/What-s-the-latest-firmware-version-of-my-NETGEAR-cable-modem-or-modem-router,COX has approved firmwareV1.01.29 for my C6250 router. However, I'm still on V1.02.01 -- how do I upgrade my router to V1.01.29?1.3KViews0likes2CommentsIntermittent Wifi Connectivity Issues and SLOW connection
I pay for the premier internet service, but seem to get anything BUT... it's slow like dial up many times or just stops responding, which doesn't make sense since I can test my speed at times and see 35.9 mbps download and 6.88mbps upload. I know I have quite a few devices connected, which is why I pay for better internet service, but only 2 or 3 at a time that are actually streaming or internet browsing. I checked my channels and have adjusted to account for a lot of neighborhood cross-pollination, but no luck. Tried On my Netgear Gateway C3600BD modem logs, I see a ton of error logs. Any advice is appreciated. This has been ongoing for quite a while, and usually the response is to reset the modem, but that's getting old. 2018-01-06, 21:33:54.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-06, 21:33:06.0 Notice (6) TLV-11 - unrecognized OID;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 18:14:08.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 14:37:35.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 14:37:03.0 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 14:36:15.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 14:35:43.0 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 14:34:55.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 14:34:23.0 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 14:33:35.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 14:33:03.0 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 14:32:16.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 14:31:43.0 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 14:30:56.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 14:30:23.0 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 13:16:15.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 13:15:10.0 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 08:08:25.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 08:07:20.0 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 08:06:45.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 08:05:40.0 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 08:05:06.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 08:04:01.0 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 08:03:26.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; 2018-01-05, 08:02:21.0 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.1;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=b0:7f:b9:b2:6a:78;CMTS-MAC=2c:86:d2:88:a2:ad;CM-QOS=1.0;CM-VER=3.0;1KViews0likes1CommentNetgear CAX80 combo modem / router. Router connection keeps dropping off several times during the day
I purchased this Netgear CAX80 in Oct 2021. At the time a high end modem/router ($400). I can say fairly OK for the last 17 months. However, during the last week (early Mar 2023) I've had to reset the modem multiple times during the day (3x) after loosing all the WiFi network connections. I have done the following w/o any successful results: 1. Changed the SSID name & paswords for all the netwoks 2. Changed the modem/router location 3. Plugged the modem/router directly to wall outlet (it used to be plugged to a power strip) Because the router is out of warranty I can't get proper support from Netgear Today, during another router outage I decided to test if hard wiring into the modem w/ ethernet cable I could get online. To my surprise, yes I was able to. So this tells me is therouter section (WiFi) of this modem causing the problem. Again, I had toreset the modem to get everything working again. This can't be normal Yesterday I called COX to check if they could help and the only thing they said was the normal ..."reset" ... which I know that resolves the problem temporarily. However, I shouldn't have to do that 3 or more times a day!!! Has anyone else run into the same problem? What solutions did you apply to fix the issue. Much appreciated for the forum feedback999Views0likes6Comments