New Poster
•
1 Message
Received Response to Broadcast Maintenance Request But no Unicast Maintenance opportunities received
Hello, I'm experiencing internet connectivity issues identical to those described in this post: https://forums.xfinity.com/t5/Your-Home-Network/Received-Response-to-Broadcast-Maintenance-Request-But-no/td-p/3375716
My symptoms include intermittent lapses in connection (my coworkers have reported significant stalls/lag on my end during video calls, even though I'm using a wired connection), frequent drops in download speed (well below 50% of the speed I'm paying for) and periodically glacial upload speeds (< 1Mbps). On average these lapses in service occur 2-3 times each day & don't seem to be correlated with internet usage by others in the house. My modem's logs lead me to believe that I'm facing the same issue experienced by @uwinmaine in October 2020 (see post linked above):
| Time | Priority | Description |
| 2021-2-6, 20:45:40 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:45:08 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:44:20 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:43:48 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:43:01 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:42:28 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:41:41 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:41:08 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:40:21 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:39:48 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:39:01 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:38:28 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:37:41 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:37:09 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:36:21 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:35:49 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:35:01 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:34:29 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:33:42 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:33:10 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:32:22 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:31:49 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:31:02 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:30:29 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:29:42 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:29:09 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:28:22 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:27:49 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:26:42 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:26:10 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:25:02 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:24:30 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:23:22 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:22:50 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:21:43 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:21:10 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:20:23 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:19:50 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:18:43 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
| 2021-2-6, 20:18:10 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:3a:0c:10;CMTS-MAC=d4:2c:44:7d:7f:1e;CM-QOS=1.1;CM-VER=3.0; |
My modem is a Netgear CM500 & as far as I can tell it's on the latest firmware version available to me: V1.01.14
Here's is some more information that seemed to help resolve the issue in the post linked above:
| Downstream Bonded Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Upstream Bonded Channels (Partial Service) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I've been experiencing these lapses in service for several months now & no amount of hardware resets / software updates have seemed to improve anything.
In the post linked above, @EG and @ComcastMorgan seemed to understand the situation better than I currently do & it looks like they both helped to resolve the issue for @uwinmaine -- can anyone help me understand what might be going on with my modem + whether or not anything can be done to improve my internet service?
Thanks in advance
(Original post, once more: https://forums.xfinity.com/t5/Your-Home-Network/Received-Response-to-Broadcast-Maintenance-Request-But-no/td-p/3375716#)
EG
Expert
•
110.1K Messages
4 years ago
The upstream power is high and is already out of spec on channel #3. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
In a self troubleshooting effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage types like GE, RadioShack, RCA, Philips, Leviton, Magnavox, and Rocketfish from big box stores like Home Depot, Lowes, Target, Wal-Mart etc. Splitters should be swapped with known to be good / new ones to test
If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two way splitter connected directly off of the drop from the street/pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed, and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.
0
0
user_aaa08a
Visitor
•
5 Messages
4 years ago
I had a Netgear C6300 which worked well for five or so years. It would drop connection but automatically restore maybe 2 or 3 times a month. I upgraded Comcast to 800 Mbps and that old router would only make ~ 550 so I got a new Netgear $500 Orbi setup with a CBR750 gateway. It was making 950 but would drop the Internet 2 or 3 times a day on my Eithernet connected PC: I know it wasn't a WiFi problem. After a few days I called Netqear twice and Comcast twice with no help after hours on the phone. I gave up on the Orbi after a couple of weeks of re-booting and got a Netgear C7000 which is making over 800 with DOCSIS 3.0, the Orbi was 3.1. That has dropped the web several times in the last couple of days. My upstream power is across the channels is -3.7 to .2 dBmV with the S/N 34.6 to 38.5 dB. Upstream reports 33 DBMv with 5 channels locked. On both new modems they would report a "Good" cable connection even when there was no Internet connecting. I tried using manual DNS servers also; to no avail. The Internet never came back on its on like the old modem, it always requires a re-boot to get it back.
How do I fix this? I think calling Netgear or Comcast support is a waste of time, they don't even hear or understand the problem!
3