NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
bcassell
Jan 26, 2017Aspirant
CM1000 requiring rebooting several times a day (Comcast)
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 w...
- Oct 17, 2017
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.
EnduroDriver
Feb 16, 2017Tutor
As of last night, I still had not received the .15 firmware (Comcast Seattle) on the modem I was having overheating problems with. I received a replacement from Amazon that did come with .15 so based on that and the other comments it looks like Amazon’s inventory is all up on the latest firmware anyway. Fingers crossed that my issues are resolved but I’m pretty sure my grief was from a faulty modem that was overheating and not related to the firmware issue some are having.
vkdelta
Feb 16, 2017NETGEAR Employee Retired
you will need to reboot the device to get the FW. Comcast has deployed the Fw in all the markets. Let me know if you dont get it.
If you are already on .15 FW, monitor it and let us know.
- Tr4visFeb 16, 2017Tutor
vkdelta I have x.15 installed and still lose bandwidth from 250Mbps down to 1Mbps over the course of about :30 after a restart of the modem. It never seems to return until I give it another reboot.
- vkdeltaFeb 16, 2017NETGEAR Employee Retired
Tr4vis did you check with just modem only or checking with router?
your problem may be different from other people reported of drop-outs.
do you have your event log and power levels? Pls post them there.
- Tr4visFeb 17, 2017Tutor
Here are the images:
Error log:
2017-02-15, 22:33:00 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1; 2017-02-15, 23:59:34 Warning (5) MDD message timeout;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;