- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: CM1000 requiring rebooting several times a day (Comcast)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I recently purchased a Netgear CM1000 for use on Comcast and several times a day the internet just stops working despite all lights still showing green. When this happens I can't even log into the web management app. Turning the modem off and back on removes the problem, but this is really annoying to have to do multiple times a day! Any advice is welcomed. Here are some pertinent pieces of information:
Hardware Version | 2.02 |
Firmware Version | V2.01.14 |
| |||||||||||||||
|
Downstream Bonded Channels | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Upstream Bonded Channels | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Time | Priority | Description |
2017-01-22, 21:03:53 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-22, 21:03:58 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-22, 21:04:05 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-22, 21:04:49 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-22, 21:04:49 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-22, 21:05:09 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-22, 21:05:10 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-22, 21:05:28 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-22, 21:05:29 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-22, 21:05:48 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 19:26:40 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 21:01:18 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 21:01:21 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 21:01:27 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 21:02:09 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 21:02:09 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 21:02:29 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 21:02:30 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 21:02:49 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 21:02:50 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 21:03:09 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 22:53:14 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 23:00:30 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 23:00:35 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 23:00:41 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 23:01:11 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 23:01:12 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 23:01:32 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 23:01:32 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 23:01:53 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 23:01:54 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
2017-01-24, 23:02:12 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
This event log comes shortly after I had to restart my modem for the second time in the last 2 hours!
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Interesting, the overall problem was solved for me and several neighbors. Cox replaced a mini-amplifier in the box at the street. However, I found the item that had the largest impact to overall network stability was unplugging our Ac1200's extenders. interestingly, we each had one on our individual networks and removing them resolved the overall issues.
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
Hello bcassell
I see alot of T3 and T4 timeouts this usually is a issue with the connection to your home you may need to have your ISP tech come out and check the lines.
https://volpefirm.com/docsis_timout_descriptions/
DarrenM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
Hi,
NTGR observed this issue with specific users and working on FW fix and is currently under validation.
we should have an update for you by 2/7. Hit us back and we will let you.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
I am having the exact same issues with my CM1000, as well as slower download and upload speeds than my previous Arris SB6190. I sent an email to netgearteam@netgear.com and they replied they are going to work with Comcast to pull logs, etc., on my modem to see if they can figure out what is going on. The reply here from Netgear is also promising. I suspected these issues were due to a firmware bug, so am now hopeful Netgear will have a fix soon. I am subscribing to this thread to watch for any updates.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
I would like to chime in and add that I am also experiencing this exact same issue with the same log entries. I had to power cycle today to get my internet access back. I am hopeful we will get a firmware update soon as I would prefer not to have to return the modem.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
thank for your patience. Will let you know our validation results soon.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
Any update?
I'm experiencing the same issues stated above PLUS if I change the modem login password, I can no longer hardwire my laptop to the cm1000 for speed test purposes.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
Also desperate here for an update on this as I am having the exact same issues and almost ready to return the modem to the store unless something is very very close to being done about this.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
I am having the same problems and have the same type of logs. Comcast has been here several times in the last 2 weeks and replaced cable lines from the pole to the modem also installed a powered amplifier and am now on my second test modem. They checked the nodes in my area and found a large amount of noise. It has been escalated up to a regional customer service manager and no one even seems to know that this is a known issue with the CM1000.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
FW is certified by the ISP. Just waiting for deployment. Will confirm soon.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
Is FW coming to Cox as well? I'm having similar issues on Cox.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
That's great news, vkdelta. Please keep us updated.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
What version should we be looking for when the ISPs start pusing it out?
I'm currently showing V2.01.14
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
A response from a Netgear engineer by email on another forum indicated it would be 2.01.15 for those of us on Comcast, since we are on 2.01.14 right now. I assume Cox will be going to .14 since they are apparently on .13.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
Any update? I had another "incident" last night.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
I have a feeling Comcast isn't pushing the new firmware out yet. I have power-cycled my modem several times in the hope I would receive the new firmware, with no luck.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
Comcast apparently hasn't pushed it yet (according to my own experience as well as that of others on DSLReports) but Cox is pushing it out, and they're getting .15. Comcast fails us again.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
Comcast should happen early next week.
COX will directly go to .15 as well. (no need to go .14). no ETA but should happen soon.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
Two more dropouts today, one yesterday. I really hope early next week means tomorrow. This is beyond frustrating.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
Try having this many disconnects in the last 5 hors.....
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
Dropouts from CM1000 are now increasing to several times a day for me - this is now well past being an annoyance...
Oh mighty Netgear and Comcast gods - please release v .15 firmware asap!!!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 requiring rebooting several times a day (Comcast)
One last step to go...almost getting there. I can understand your situation..
Just waiting for ISP to deploy new config files.
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more