NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Now Spectrum has updated the CM3000 to version 6.01.03 - they refuse to roll it back
This darn broken firmware has made its way to Spectrum. They refuse to believe the only solution is to rollback to 5.0.X as proven method by Xfinity and other ISPs who dealt with this mess months ago...
Hello:
Thought I would add to the issue regarding Cox Cable.
Have had same issue since Cox updated the CM3000 to version 6.01.03, likely in May. Have had 4 Cox service calls and last one finally advised either modem itself or bad firmware. He did advise he doubted Cox had ability to do firmware rollback, as had never heard of that happening. He advised if I got a new CM3000, unless the problem version had been suspended by Cox, the new modem would likely get immediately updated as part of the provisioning process. His only recommendation was to wait till next firmware update and see if fixed issues.
That is DOA; so likely giving it another week or so to see if Cox Cable initiates a rollback or will just buy Arris S34 and be done with this nonsense.
Find it hard to believe the firmware issue made it past both NETGEAR and Cox. Have usually had good luck with NETGEAR as also have Orbi 972 and it has been great.
Thanks
Kris
Same issue with my modem, had 5 techs on site they replaced everything inside and outside my home, made a FCC complaint with cox they replaced a bunch of stuff on the street as well as the hub and still having the same problems as so many other people (up stream not locking, constant disconnects, intermittent disconnects, and disconnects where nothing show up in the logs and everything shows good connection but have no internet) i really wish i could have returned this modem at this point, i bought it back in may it worked for about 20 days and than the problem's started when they pushed this firmware. and here we all are with a 300$ piece of useless equipment. kind of crazy this has started 3 months ago and netgear hasn't really done anything to fix this.