Re: CAX80 Unable to connect to online game servers

bilal_ahmed · ‎2023-07-12

I am having trouble connecting to Call of Duty servers. I have tried port warding, changing DNS, and disabling DoS protection all in the router settings but nothing seems to work. Using a VPN solves the problem but comes with slower speeds. My upstream power is poor but I do not think that is the issue. When contacting my ISP they sent out a tech and he determined the cable needed to be changed coming to the house. That has not solved the issue. Below is the cable diagnostic. What can I do to change router settings and how can I solve the cable issue?

Cable Diagnostic

Status: Poor

Action:
[Upstream Power Level]
Try these actions (Click the Refresh button after each step):
1) Make sure the coaxial cable is tightly connected.
2) Remove any unnecessary splitters.
3) Replace any required splitters.
4) Contact your service provider for troubleshooting help.

Internet Access:

Downstream Status:

Upstream Status:

Upstream Power Level:
	Upstream power is poor (29.0dBmV). The recommended level is from 30 to 55dBmV.

Refresh Save Cable Diagnostic Info

Advanced Information

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	591 MHz	Locked
Connectivity State	OK	Operational
Boot State	OK	Operational
Security	Enabled	BPI+

Downstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Frequency	Power	SNR	Correctables	Uncorrectables
1	Locked	256 QAM	28	591000000 Hz	5.4 dBmV	44.7 dB	0	0
2	Locked	256 QAM	13	495000000 Hz	6.9 dBmV	45.8 dB	0	0
3	Locked	256 QAM	14	507000000 Hz	6.8 dBmV	45.8 dB	0	0
4	Locked	256 QAM	15	513000000 Hz	6.7 dBmV	45.8 dB	0	0
5	Locked	256 QAM	16	519000000 Hz	6.6 dBmV	45.7 dB	0	0
6	Locked	256 QAM	17	525000000 Hz	6.5 dBmV	45.7 dB	0	0
7	Locked	256 QAM	18	531000000 Hz	6.3 dBmV	45.5 dB	0	0
8	Locked	256 QAM	19	537000000 Hz	6.2 dBmV	45.4 dB	0	0
9	Locked	256 QAM	20	543000000 Hz	6.0 dBmV	45.3 dB	0	0
10	Locked	256 QAM	21	549000000 Hz	5.9 dBmV	45.2 dB	0	0
11	Locked	256 QAM	22	555000000 Hz	5.7 dBmV	45.1 dB	0	0
12	Locked	256 QAM	23	561000000 Hz	5.8 dBmV	45.1 dB	0	0
13	Locked	256 QAM	24	567000000 Hz	5.7 dBmV	45.0 dB	0	0
14	Locked	256 QAM	25	573000000 Hz	5.5 dBmV	45.0 dB	0	0
15	Locked	256 QAM	26	579000000 Hz	5.6 dBmV	45.0 dB	0	0
16	Locked	256 QAM	27	585000000 Hz	5.5 dBmV	44.9 dB	0	0
17	Locked	256 QAM	29	597000000 Hz	5.4 dBmV	44.7 dB	0	0
18	Locked	256 QAM	30	603000000 Hz	5.3 dBmV	44.6 dB	0	0
19	Locked	256 QAM	31	609000000 Hz	5.1 dBmV	44.5 dB	0	0
20	Locked	256 QAM	32	615000000 Hz	5.1 dBmV	44.5 dB	0	0
21	Locked	256 QAM	33	621000000 Hz	5.2 dBmV	44.4 dB	0	0
22	Locked	256 QAM	34	627000000 Hz	5.2 dBmV	44.4 dB	0	0
23	Locked	256 QAM	35	633000000 Hz	5.0 dBmV	44.2 dB	0	0
24	Locked	256 QAM	36	639000000 Hz	4.9 dBmV	44.1 dB	0	0
25	Locked	256 QAM	37	645000000 Hz	5.0 dBmV	44.1 dB	0	0
26	Locked	256 QAM	38	651000000 Hz	4.9 dBmV	44.0 dB	0	0
27	Locked	256 QAM	39	657000000 Hz	4.9 dBmV	43.9 dB	0	0
28	Locked	256 QAM	40	663000000 Hz	4.9 dBmV	43.9 dB	0	0
29	Locked	256 QAM	41	669000000 Hz	4.8 dBmV	43.8 dB	0	0
30	Locked	256 QAM	42	675000000 Hz	4.7 dBmV	42.4 dB	0	0
31	Locked	256 QAM	43	681000000 Hz	4.5 dBmV	43.6 dB	0	0
32	Locked	256 QAM	44	687000000 Hz	4.7 dBmV	43.3 dB	0	0

Upstream Bonded Channels

Channel	Lock Status	US Channel Type	Channel ID	Symbol Rate	Frequency	Power
1	Locked	ATDMA	20	5120 Ksym/sec	16400000 Hz	29.0 dBmV
2	Locked	ATDMA	18	5120 Ksym/sec	29200000 Hz	30.5 dBmV
3	Locked	ATDMA	19	5120 Ksym/sec	22800000 Hz	29.8 dBmV
4	Locked	ATDMA	17	5120 Ksym/sec	35600000 Hz	30.8 dBmV
5	Not Locked	Unknown	0	0	0	0.0 dBmV
6	Not Locked	Unknown	0	0	0	0.0 dBmV
7	Not Locked	Unknown	0	0	0	0.0 dBmV
8	Not Locked	Unknown	0	0	0	0.0 dBmV

Downstream OFDM Channels

Channel	Lock Status	Modulation / Profile ID	Channel ID	Frequency	Power	SNR / MER	Active Subcarrier Number Range	Unerrored Codewords	Correctable Codewords	Uncorrectable Codewords
1	Locked	0 ,1 ,2 ,3	193	693000000 Hz	4.78 dBmV	42.8 dB	1108 ~ 2987	24529327	7715740	0
2	Not Locked	0	0	0 Hz	0 dBmV	0 dB	0 ~ 4095	0	0	0

Upstream OFDMA Channels

Channel	Lock Status	Modulation / Profile ID	Channel ID	Frequency	Power
1	Not Locked	0	0	0 Hz	0 dBmV
2	Not Locked	0	0	0 Hz	0 dBmV

DarrenM · ‎2023-07-12

Do you have any other routers connected to the CAX80? Are you gaming on Xbox Playstation or PC?

bilal_ahmed · ‎2023-07-12

Nope, CAX80 is my router/modem and I am having the issue on multiple PCs.

FURRYe38 · ‎2023-07-12

What Firmware version is currently loaded?
Please post a copy and paste of the modems event log page.
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-mode...

Power on the UP Side is low, something to ask the ISP to see if they can raise it some.

What game services are you connected too?

Has a factory reset and setup from scratch been performed since last FW update? A complete pull of the power adapters for a period of time after the factory reset then walk thru the setup wizard and setup from scratch with a wired PC and web browser. Recommend setting the default DHCP IP address pool range to the following after applying and a factory reset: 192.168.#.100 to 192.168.#.200.
https://kb.netgear.com/24089/How-do-I-specify-the-pool-of-IP-addresses-assigned-by-my-Nighthawk-rout...

bilal_ahmed · ‎2023-07-12

Firmware Version

V2.1.5.2

Time	Priority	Description
Wed Jul 12 11:26:17 2023	Notice (6)	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 12 11:25:51 2023	Notice (6)	TLV-11 - unrecognized OID;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:52 1970	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
Thu Jan 1 00:00:43 1970	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 12 00:00:10 2023	Critical (3)	Resetting the cable modem due to docsDevResetNow
Mon Jul 3 08:52:11 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Mon Jul 3 08:52:06 2023	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Mon Jul 3 08:51:54 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Mon Jul 3 08:51:53 2023	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Mon Jul 3 08:51:53 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Mon Jul 3 08:51:52 2023	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Mon Jul 3 08:51:11 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Mon Jul 3 08:51:09 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:43 1970	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Mon Jun 26 16:08:16 2023	Critical (3)	Resetting the cable modem due to docsDevResetNow
Sat Jun 24 15:22:43 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 15:22:38 2023	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 15:22:38 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 15:22:37 2023	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 15:22:02 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 15:21:57 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 15:21:54 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 15:16:20 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 15:16:16 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 15:09:36 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 15:09:31 2023	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 15:09:29 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 15:09:28 2023	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 15:08:46 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 15:08:39 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 15:08:36 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 14:59:56 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 14:59:51 2023	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 14:59:40 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 14:59:40 2023	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 14:59:40 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 14:59:39 2023	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 14:59:04 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 14:58:58 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jun 24 14:58:54 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2a:18;CMTS-MAC=00:90:f0:60:05:00;CM-QOS=1.1;CM-VER=3.1;

A factory reset has not been done. I am using Steam to launch Call of Duty.

FURRYe38 · ‎2023-07-12

See lots of Criticals that indicated a signal problem on the ISP side of the modem. ISP should review and resolve these and if Warnings or Errors are seen in the logs as well.

Kitsap · ‎2023-07-12

Do you have any splitters, amplifiers, or filters in the coax line upstream of your CAX80?

bilal_ahmed · ‎2023-07-13

No

bilal_ahmed · ‎2023-07-16

UPDATE:

I had my ISP come out and they determined it was nothing on their end. They however were able to fix the poor upstream power levels. For some reason, I was able to access COD servers using ethernet and my 2.4GHz. I was not able to use my 5Ghz wifi. What could be the issue? I have factory reset the router and still has not fixed the issue. I am speculating there is something wrong with the router settings.

Kitsap · ‎2023-07-16

@bilal_ahmed wrote:
UPDATE:
I had my ISP come out and they determined it was nothing on their end. They however were able to fix the poor upstream power levels. For some reason, I was able to access COD servers using ethernet and my 2.4GHz. I was not able to use my 5Ghz wifi. What could be the issue? I have factory reset the router and still has not fixed the issue. I am speculating there is something wrong with the router settings.

That is pretty much the default assessment from an ISP.

Need further details on your 5 GHz issue.

Could you see the 5 GHz Wi-Fi SSID? Could you see the 5 GHz Wi-Fi SSID and not connect? Did you get an error message when you tried to connect? If yes, what device were you using to try to connect to the 5 GHz Wi-Fi?