Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet

jredmann · ‎2021-07-27

I upgraded my internet service with WoW! three days ago from 100Mbs to 500Mbs. I have not been able to get over a download speed of 120Mbs and upload speed of 24Mbs. They are unsure why this is happening and so am I. I do not know where in my setting to make the router and modem receive the 500Mbs. Any help and knowledge is greatly appreciated.

plemans · ‎2021-07-27

Test it first directly connected to the modem with a pc/laptop. its pointless to troubleshoot a router if the modem is the issues.

So what speeds do you get directly off the modem?

what speeds does wow rate the CM600 for their service? (its different for each isp)

jredmann · ‎2021-07-27

I did test directly from the modem on a laptop, it was 35Mbs download and 24Mbs upload, I also have tested from a desktop connected to a repeater that is plugged into the wall outlet, the last time I tested that it was 90Mbs download and 13Mbs upload. It has been as high as 130Mbs download and 24Mbs upload. The people from WoW that I have spoken to have all said that the modem should be able to handle 600Mbs.

plemans · ‎2021-07-27

do you have a screen snip of the modems cable connection page and its logs?

plemans · ‎2021-07-27

Again, make sure to remove the router. You need to first get the modem up to speed.

And if the routers having issues as well (unknown) it can complicate things.

jredmann · ‎2021-07-27

Where would I find the modems cable connection page and its logs?

FURRYe38 · ‎2021-07-27

Log into the modems web page and there should be a connection status button or tab to select on. (192.168.100.1) This page will have a channels, signals and more information regarding the modems and it's connections to the ISP service. You can copy and paste this information in the next post or output to pdf file or some text file and select the Choose File button on the next post to attach it to the post.

jredmann · ‎2021-07-27

FURRYe38 · ‎2021-07-27

Choose File button on the next post to attach it to the post. We have to wait for inline pictures to be approved.

jredmann · ‎2021-07-27

Frequency start Value

This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.

Starting Frequency

Startup Procedure

Procedure	Status	Comment
Acquire Downstream Channel	603000000 Hz	Locked
Connectivity State	OK	Operational
Boot State	OK	Operational
Security	Enable	BPI+
IP Provisioning Mode	Honor MDD	IPv4 only

<tabindex=-1>Downstream Bonded Channels</tabindex=-1>

Channel	Lock Status	Modulation	Channel ID	Frequency	Power	SNR	Correctables	Uncorrectables
1	Locked	QAM256	19	603000000 Hz	-6.5 dBmV	34.5 dB	527	0
2	Locked	QAM256	1	489000000 Hz	-0.6 dBmV	36.6 dB	2041	4580
3	Locked	QAM256	2	495000000 Hz	-0.4 dBmV	34.3 dB	227	13
4	Locked	QAM256	3	501000000 Hz	-0.7 dBmV	36.3 dB	188	0
5	Locked	QAM256	4	507000000 Hz	-0.7 dBmV	37.9 dB	173	0
6	Locked	QAM256	5	513000000 Hz	-0.1 dBmV	39.0 dB	155	0
7	Locked	QAM256	6	519000000 Hz	0.1 dBmV	39.0 dB	214	0
8	Locked	QAM256	7	525000000 Hz	-0.2 dBmV	38.5 dB	222	0
9	Locked	QAM256	8	531000000 Hz	-0.1 dBmV	35.4 dB	234	0
10	Locked	QAM256	9	537000000 Hz	-0.6 dBmV	38.7 dB	227	0
11	Locked	QAM256	10	543000000 Hz	-0.4 dBmV	38.2 dB	393	0
12	Locked	QAM256	11	555000000 Hz	-0.8 dBmV	37.9 dB	1096	86
13	Locked	QAM256	12	561000000 Hz	-0.6 dBmV	37.4 dB	1399	0
14	Locked	QAM256	14	567000000 Hz	-1.2 dBmV	37.9 dB	1259	0
15	Locked	QAM256	13	573000000 Hz	-1.3 dBmV	37.1 dB	942	0
16	Locked	QAM256	15	579000000 Hz	-1.2 dBmV	37.1 dB	881	0
17	Locked	QAM256	16	585000000 Hz	-2.3 dBmV	37.9 dB	343	0
18	Locked	QAM256	17	591000000 Hz	-3.5 dBmV	36.8 dB	358	0
19	Locked	QAM256	18	597000000 Hz	-6.3 dBmV	34.6 dB	277	0
20	Locked	QAM256	20	615000000 Hz	-1.8 dBmV	39.4 dB	114	4
21	Locked	QAM256	22	627000000 Hz	-1.5 dBmV	37.9 dB	121	7
22	Locked	QAM256	23	633000000 Hz	-1.6 dBmV	39.4 dB	57	0
23	Locked	QAM256	29	669000000 Hz	-1.5 dBmV	39.9 dB	15	0
24	Locked	QAM256	31	675000000 Hz	-1.5 dBmV	39.4 dB	547850	877309

<tabindex=-1>Upstream Bonded Channels</tabindex=-1>

Channel	Lock Status	US Channel Type	Channel ID	Symbol Rate	Frequency	Power
1	Locked	ATDMA	1	5120 Ksym/sec	21900000 Hz	49.8 dBmV
2	Locked	ATDMA	2	5120 Ksym/sec	28300000 Hz	47.5 dBmV
3	Locked	ATDMA	3	5120 Ksym/sec	34700000 Hz	47.0 dBmV
4	Locked	ATDMA	4	2560 Ksym/sec	39500000 Hz	47.3 dBmV

Current System Time: Tue Jul 27 16:03:50 2021

plemans · ‎2021-07-28

Do you also have your logs?

You don't have a lot of errors but your power is a bit out of spec. The channels should be within 3.5dbmv of each other. You're a bit out of that.

if you have any splitters, amplifiers, or signal attenuators in line, remove them.

Check the link for kinks, loose/old/bad/cheap/corroded connections and remove them if you do.

jredmann · ‎2021-07-28

@plemans

Time	Priority	Description
2021-07-27, 21:22:41	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-07-27, 09:22:56	Critical (3)	Resetting the cable modem due to docsDevResetNow
2021-07-25, 14:08:04	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-07-25, 03:06:58	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-07-24, 10:47:01	Critical (3)	Resetting the cable modem due to docsDevResetNow
2021-07-24, 10:42:15	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-07-22, 03:35:11	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-07-21, 06:16:47	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-07-16, 19:22:40	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-06-09, 00:08:40	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-06-09, 00:07:23	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-06-09, 00:04:30	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-06-08, 11:29:12	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-06-05, 01:47:06	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-06-03, 01:17:30	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-05-30, 03:24:25	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-05-28, 11:40:18	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-05-25, 11:17:47	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-05-25, 11:06:33	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-05-19, 00:12:43	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-05-19, 00:08:48	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-05-19, 00:08:44	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-04-28, 04:34:28	Critical (3)	Resetting the cable modem due to docsDevResetNow
2021-04-26, 14:08:54	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-04-21, 14:13:37	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-03-15, 17:41:31	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.1;CM-VER=3.0;
2021-03-11, 14:14:47	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.0;CM-VER=3.0;
2021-03-11, 14:14:25	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2021-03-11, 14:14:21	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.0;CM-VER=3.0;
2021-03-11, 14:13:54	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2021-03-11, 14:13:52	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2021-03-11, 14:13:50	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2021-03-11, 14:13:49	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.0;CM-VER=3.0;
Time Not Established	Warning (5)	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.0;CM-VER=3.0;
Time Not Established	Notice (6)	Honoring MDD; IP provisioning mode = IPv4
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.0;CM-VER=3.0;
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.0;CM-VER=3.0;
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.0;CM-VER=3.0;
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:6a:ae:d8;CMTS-MAC=00:01:5c:b7:7e:49;CM-QOS=1.0;CM-VER=3.0;

FURRYe38 · ‎2021-07-28

Lots of criticals...

https://highspeed.tips/docsis-events/

jredmann · ‎2021-07-28

@FURRYe38 wrote:

Lots of criticals...

https://highspeed.tips/docsis-events/

I am assuming thats not good. I was considering buying a new modem, what would be your recomendation?

FURRYe38 · ‎2021-07-28

You can try a new modem for sure and see if these are seen on the new modem. If they are then the ISP needs to review there service line and signals UP to the modem. If the problem is not seen on the new modem then the CM600 could be faulty.

jredmann · ‎2021-07-28

Okay, I've had this modem for a few years, probably close to 4 or 5 years. So it would not suprise me if it was going out.

FURRYe38 · ‎2021-07-28

Try another CM modem. CM1000, 1100, 1200 or 2000. See what one of these reports.

plemans · ‎2021-07-28

I'd also check the line carefully. Move the modem to right where the coax enters the home to prevent wiring in the home being the issue.

The docsresets are issued from the cmts usually. And t3 tends to indicate line issues.

not saying somethings not wrong with the modem but those errors tend to be line issues

Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet

Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet

Re: Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet

Re: Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet

Re: Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet

Re: Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet

Re: Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet

Re: Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet

Re: Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet

Re: Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet

Re: Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet

Re: Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet

Re: Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet

Re: Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet

Re: Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet

Re: Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet

Re: Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet

Re: Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet

Re: Unable to reach 500Mbs using Netgear CM600 cable modem and R6400v2 router with WoW! internet