- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: Cm500 disconnection issues
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Performed a search and similar topics were marked resolved, so I'm starting a new one. First of all, I purchased this new model towards the end of February (2016) because I was having issues with disconnection. Comcast recommended that I purchase a new modem, which I did (CM500).
I'm trying to determine what is causing the disconnection issues. It's very strange in that it always seems to happen around the same times. I work from home and notice it happening around 11:00-12:00PM in the afternoon. Then it's fine until 11:00-12:00AM. I am a gamer and during online sessions with friends on Playstation, I can watch my modem disconnect and reboot multiple times in a row.
I have been working with Comcast on this issue. I even had a technician out to check my connections and line strength and signal noise and decibal levels two days ago. It continues to happen every single day. They are sending someone out on Friday to check again, but recommended that I contact you for support.
Note: I bought this at Best Buy and purchased the protection plan, so I can simply swap it out for a new one if it's the modem. But I suspect there is something else going on. The technician who was out here two days ago said it's possible it is the Comcast Node Grid for my neighborhood. However, none of my neighbors have been calling in, so they are telling me it's my modem.
The technician did replace the coax connector outside, saying it was weathered and after checking the decibal levels said it was indicating it was well within parameters. I have an Apple Airport wireless router that's connected to the CM500 and my Playstation and Apple TV are connected directly via ethernet, so no wireless issues. When my internet goes out, I can see my modem resetting. During the day, it will do this once or twice, but at night it's happening multiple times.
I just reset the Event Log after the technician was out and here is a copy in the event this is helpful.
2016-5-24, 15:50:14 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-24, 15:50:22 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-24, 15:50:34 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-24, 15:50:43 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.0;CM-VER=3.0; |
2016-5-24, 15:51:43 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-24, 19:50:32 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-24, 19:50:52 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-24, 19:51:04 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-24, 19:51:12 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-24, 19:51:24 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-24, 19:51:32 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.0;CM-VER=3.0; |
2016-5-25, 00:00:29 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-25, 00:00:49 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-25, 00:01:01 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-25, 00:01:09 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-25, 00:01:21 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-25, 00:01:29 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.0;CM-VER=3.0; |
2016-5-25, 00:02:39 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-25, 02:34:28 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-25, 02:34:48 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-25, 02:35:00 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-25, 02:35:08 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-25, 02:35:20 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-25, 02:35:29 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.0;CM-VER=3.0; |
1970-1-1, 00:00:21 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
1970-1-1, 00:00:27 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.0;CM-VER=3.0; |
1970-1-1, 00:00:35 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
2016-5-25, 13:12:43 | Warning (5) | Dynamic Range Window violation |
2016-5-25, 13:12:59 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-25, 13:13:03 | Warning (5) | Dynamic Range Window violation |
2016-5-25, 13:13:19 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-25, 13:13:22 | Warning (5) | Dynamic Range Window violation |
2016-5-25, 13:13:31 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-25, 13:13:33 | Warning (5) | Dynamic Range Window violation |
2016-5-25, 13:13:39 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-25, 13:13:42 | Warning (5) | Dynamic Range Window violation |
2016-5-25, 13:13:51 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
2016-5-25, 13:14:00 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.0;CM-VER=3.0; |
2016-5-25, 13:14:15 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
2016-5-25, 13:15:06 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=40:5d:82:42:3a:68;CMTS-MAC=00:cc:fc:61:31:ce;CM-QOS=1.1;CM-VER=3.0; |
Also, here is the Cable Connection information currently:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Downstream Bonded Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Upstream Bonded Channels | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Any suggestions, ideas as to why this is happening?
Thanks in advance! |
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello randykepple
Typically when you see T3 and T4 timeouts its a line issue with the ISP but if they are claiming its the modem after checking it out I would try to swap it out just to make sure it is not the modem that is having issues.
DarrenM
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello randykepple
Typically when you see T3 and T4 timeouts its a line issue with the ISP but if they are claiming its the modem after checking it out I would try to swap it out just to make sure it is not the modem that is having issues.
DarrenM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Cm500 disconnection issues
Thanks Darren.
I did have them out again this morning. They verified the modem and line are spot on with regard to signal noise, decibal levels and signal strength. However, when he climbed up on the pole to check the connection, he discovered a very old piece of equipment. The upstream signal was very weak and he said this could very well be the issue. That alone would cause the disconnection issues.
I'm on a dead end street and apparently it's the end-of-the line connection and any spikes (electrical, storm related, etc. ) are handled at this connection. They are going to replace it over the weekend and we'll see if that corrects the issue.
Of course, the troubleshooting steps are to check the connections, power cycle the modem, blame the modem, advise you to buy their overpriced modem (or even worse, rent one for years) and then advise you to replace the modem. They could not make heads or tails of the logs I provided to you. So, it's nice that you were able to confirm what they discovered this morning.
Thank you very much!
• Introducing NETGEAR WiFi 7 Orbi 770 Series and Nighthawk RS300
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more