NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Nighthawk CM2050V Comcast Firmware Killed Speed
I understand Comcast has just updated the firmware in these routers from V2.01.03 to V9.01.01. My download speed went from 934 to 225. Comcast tech came out yesterday and cleared some signal loss but it did nothing to increase the speed back to what it was. I'm paying for 800.
Is anyone else having this issue? Is Comcast killing these routers?
I contacted a supervisor who actually responded he could see the modem was not properly provisioned, he opened another ticket and one of their best techs came out. I think they fixed it from inside but he was excellent. Problem solved after a month and about 15 tickets opened. Thanks for the encouragement
58 Replies
Please post a copy and paste of the modems connection status and event log page.
https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-modem-modem-router
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-modem-routerHas a power off for 1 minute then back ON with the ISP modem and router been performed since last update?
Be sure to restart your network in this sequence:
Turn off and unplug modem.
Turn off router and computers.
Plug in and turn on modem. Wait 2 minutes for it to connect.
Turn on the router and wait 2 minutes for it to connect.
Turn on computers and rest of network.Be sure your using a good quality LAN cable between the modem and router. CAT6 is recommended.
What is the brand and model of the host wifi router connected to the modem?CM series modems are not routers. Just only modems.
Time Priority Description Tue Sep 26 05:38:37 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Tue Sep 26 05:33:20 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Tue Sep 26 00:28:32 2023 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Tue Sep 26 00:28:24 2023 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Tue Sep 26 00:28:23 2023 (Notice (6)) TLV-11 - unrecognized OID;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Tue Sep 26 00:28:14 2023 (Notice (6)) Honoring MDD; IP provisioning mode = IPv6 Tue Sep 26 00:28:06 2023 (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Tue Sep 26 00:24:56 2023 (Warning (5)) ToD request sent - No Response received;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Tue Sep 26 00:24:55 2023 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Tue Sep 26 00:24:54 2023 (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Tue Sep 26 00:24:54 2023 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Tue Sep 26 00:24:53 2023 (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Tue Sep 26 00:24:06 2023 (Warning (5)) MDD message timeout;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Tue Sep 26 00:24:06 2023 (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Tue Sep 26 00:24:00 2023 (Warning (5)) MDD message timeout;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Tue Sep 26 00:24:00 2023 (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Mon Sep 25 23:31:45 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Mon Sep 25 23:26:06 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Mon Sep 25 23:19:33 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Mon Sep 25 22:36:04 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Mon Sep 25 22:27:00 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Mon Sep 25 20:50:10 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Mon Sep 25 15:26:40 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Mon Sep 25 15:19:33 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Mon Sep 25 14:40:36 2023 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Mon Sep 25 14:40:30 2023 (Notice (6)) TLV-11 - unrecognized OID;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Time Not Established (Notice (6)) Honoring MDD; IP provisioning mode = IPv6 Time Not Established (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Mon Sep 25 13:51:38 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Mon Sep 25 13:12:40 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Mon Sep 25 13:05:08 2023 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Mon Sep 25 13:05:02 2023 (Notice (6)) TLV-11 - unrecognized OID;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Time Not Established (Notice (6)) Honoring MDD; IP provisioning mode = IPv6 Time Not Established (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Mon Sep 25 13:01:14 2023 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Mon Sep 25 13:01:13 2023 (Notice (6)) TLV-11 - unrecognized OID;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Mon Sep 25 13:01:05 2023 (Notice (6)) Honoring MDD; IP provisioning mode = IPv6 Mon Sep 25 13:00:58 2023 (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Mon Sep 25 12:58:41 2023 (Warning (5)) ToD request sent - No Response received;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Mon Sep 25 12:58:39 2023 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:b5:15:40;CMTS-MAC=00:90:f0:67:04:00;CM-QOS=1.1;CM-VER=3.1; Please post the cable connections status data page as well.
Any Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP. Indicates a signal issue on the ISP line up to the modem.
I misspoke...I know
db3058 wrote:I understand Comcast has just updated the firmware in these routers from V2.01.03 to V9.01.01. My download speed went from 934 to 225. Comcast tech came out yesterday and cleared some signal loss but it did nothing to increase the speed back to what it was. I'm paying for 800.
Is anyone else having this issue? Is Comcast killing these routers?
The firmware on my CM2050V was updated several days ago. No degradation in throughput capacity. No indication elsewhere on the web that the firmware update is killing the modems.
Recommend you use the Ookla stand alone application for testing throughput. It is available from the play store. What device are you using to test throughput and how is it connected to the internet? Maybe via Wi-Fi?
If you are on Windows, check to see if your Network Profile has changed from Private to Public. If yes, change it back to Private.
Check the router that sets between your modem and whatever device you are using to test throughput.
So as I know regardless of diagnostics hardware fails and did in this case.
Comcast came out today and measured the input speed to the back of the modem to 1500mhz. From the back of the RJ45 on the modem I'm getting 300....200 to my laptop hardwired I was getting 934 a month ago. It worked for 2 months.
I will post whether or not support who I have an open ticket with under the 3 month hardware warranty replaces my modem.
This ISP has been working with something call mid-split. Might ask them about this. IF it was working at one point then not, ISP has done something.
The tech who came out here knew his s**t....he was awesome. The bottom line is I'm getting 1500 mhz into the modem and 200 out. It's a piece of junk. I worked outside plant with ATT for 7 years and 30 years as a PBX tech with thousands of circuits. I'm a commercial electrician as well. I know many times regardless of diagnostics, stuff needs to be replaced.
Netgear has finally agreed to process my replacement of the defective modem. That's not before they seriously tortured me for a month with ungodly slow emails back and forth....there is no phone support. They had to make sure Comcast did everything they could on their end including at the last email changing the drop and modem. Try doing that with Comcast...it takes an extraordinary amount of effort....as if it was not enough Comcast verified 1500 mhz to my modem with their 5K piece of equipment. It's not an acceptable practice to me to have another company spend all their time and money without lifting a finger to help resolve the issue. I should have been provided with an RMA replacement weeks ago after providing evidence that there was nothing else to change but the modem. I'm persistent and thankfully retired or I would need to in order to have the time for them to cough up a replacement. If you're trying to leave a sour taste in customers mouths they are absolutely adept at that.
db3058 wrote:Netgear has finally agreed to process my replacement of the defective modem. That's not before they seriously tortured me for a month with ungodly slow emails back and forth....there is no phone support. They had to make sure Comcast did everything they could on their end including at the last email changing the drop and modem. Try doing that with Comcast...it takes an extraordinary amount of effort....as if it was not enough Comcast verified 1500 mhz to my modem with their 5K piece of equipment. It's not an acceptable practice to me to have another company spend all their time and money without lifting a finger to help resolve the issue. I should have been provided with an RMA replacement weeks ago after providing evidence that there was nothing else to change but the modem. I'm persistent and thankfully retired or I would need to in order to have the time for them to cough up a replacement. If you're trying to leave a sour taste in customers mouths they are absolutely adept at that.
You should get your units of measure correct. 1500 mhz is a frequency and not a measure of data throughput. I would guess you mean 1500 Mbps (mega-bits per second) throughput. That value would be consistent for a 1200 Mbps Comcast plan that is over provisioned for 20%.
When you receive a RMA replacement, do not be surprised if it is a refurbished unit.
Are you going to wait on the RMA replacement or are you going to lease a Comcast gateway in the mean time? I would be very curious to know how a leased gateway performed in your specific installation and test setup.
You are right...I should be more accurate with my terms. It's bad Jersey youth history speaking the English language in 100 words or less. I am going to wait for the unit they send me. I won't upgrade to the latest Comcast proprietary gateway right now...it does not support DHCP IP addresses being added and my old Panasonic laserjet will not work on their network. I use that every day for printing scanning and faxing and have a lot of toner, etc. The Comcast unit is an all in one wifi gateway. In the end I'd will probably just reinstall my old Arris Tombstone that was bullet proof and still working when I decided to "upgrade". I was getting 350 Mbps with that when I disconnected it and that's plenty for grandpa. And it has a battery that works great in the CA mountains where PGE can't keep the power up for longer than a week now. They installed sensors on the lines that a squirrel can trip and it's out for 10-20 hrs while they "inspect" the lines.
I'm not sure I can turn off their wifi router function and install my own. I'll have to research that. I do understand their wifi function on the latest revisions are excellent though and are a unique newer generation wifi signal design. They also have an add-on battery backup for outages so that would work. I'm still thinking..... I pay the horrible monsters too much already and am not fond of paying them more. Their tech support over the past year has been a joke.
I installed the NEW Netgear CM2050V that arrived yesterday. The bad news is nothing has changed. The speed is still 600 Mbps slower than it was when the original CM2050V was installed in June. So Comcast has done something to kill the speed. Funny thing is I installed it at the pole because my cell will not work in the house (mountains...middle of nowhere) and although the gigabit data light on the modem was blinking I was still getting the exact same speed back of the modem as the one I replaced. So with Comcast saying I'm getting 1500 Mbps to the modem why is the modem only passing 350-360, and down to 212 hard wired LAN when it was 934. They without a doubt changed something that killed the speed in this particular modem. My buddy down the street is using an Arris T25 because he doesn't mind the horrible static on the VOIP and his speed is close to 900. Something in the new software provisioning as of 2 months ago is not compatible with the Netgear CM2050V. It is only 1 of 2 modems on their website that they indicate is compatible with speed 800 and above with telephony. Evidently that's nonsense. I guess they found a way to only allow their proprietary modems to pass high speeds through....at least that's what I'm thinking.
db3058 wrote:I installed the NEW Netgear CM2050V that arrived yesterday. The bad news is nothing has changed. The speed is still 600 Mbps slower than it was when the original CM2050V was installed in June. So Comcast has done something to kill the speed. Funny thing is I installed it at the pole because my cell will not work in the house (mountains...middle of nowhere) and although the gigabit data light on the modem was blinking I was still getting the exact same speed back of the modem as the one I replaced. So with Comcast saying I'm getting 1500 Mbps to the modem why is the modem only passing 350-360, and down to 212 hard wired LAN when it was 934. They without a doubt changed something that killed the speed in this particular modem. My buddy down the street is using an Arris T25 because he doesn't mind the horrible static on the VOIP and his speed is close to 900. Something in the new software provisioning as of 2 months ago is not compatible with the Netgear CM2050V. It is only 1 of 2 modems on their website that they indicate is compatible with speed 800 and above with telephony. Evidently that's nonsense. I guess they found a way to only allow their proprietary modems to pass high speeds through....at least that's what I'm thinking.
Information to adjust your thinking.
On paper my Comcast plan is 1000/15 Mbps. With the standard 20% over provisioning, it comes out to 1200/18 Mbps. The firmware on my CM2050V was updated last month.
The output from the modem goes through a 6 ft. Cat 6A patch cord to a RJ45/SPF+ adapter to the SPF+ input on my R9000 router.
Appropriate screen snips in attached PDF file. One from the modem user interface, one from the advanced statistics page on the router, and one history page from the Nighthawk mobile application. The mobile application test measures throughput at the input to the router.
Now that you have tried two different modems with the same results, you should consider looking at the other pieces that make up your LAN or your test methodology.
I measured the speed back of the modem RJ45 outside on the street at the base of the pole before it goes underground via conduit to my garage. None of my wiring or other equipment was connected. The drop from the pole comes to a pole on my land RG11, 50 ft. Then it runs underground conduit RG11 to my garage and RG6 to the modem. I saw the Comcast tech's test equipment measure 1500 Mbps. at every break point. I eliminated the possibility of it being any of my peripheral equipment or wiring early on and stayed consistent measuring the speed at the base of the pole, back of the modem direct with my laptop. Actually that's the only place I can get a shaky cell signal on my property. I'm only measuring what comes through the CM2050V, 50 ft from their output in the street. It's the same speed I get when moving the modem inside and measuring off the RJ45 on the modem direct from the drop before any of my stuff is a factor. I get 345 Mbps at those points so my router is dropping the speed about 120 Mbps. Just to do so I replaced the cords, Comcast wired splitter, router and switch attached to it early on...I have 2 of everything. So installing a new 3.1 router will have some benefit but still won't get me anywhere near what I'm paying for or what I had 5 weeks ago.
