Orbi WiFi 7 RBE973
Reply

Re: CAX80 Unable to connect to online game servers

bilal_ahmed
Aspirant

CAX80 Unable to connect to online game servers

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

ProcedureStatusComment
Acquire Downstream Channel591 MHzLocked
Connectivity StateOKOperational
Boot StateOKOperational
SecurityEnabledBPI+
 

Downstream Bonded Channels

ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectables
1Locked256 QAM28591000000 Hz5.4 dBmV44.7 dB00
2Locked256 QAM13495000000 Hz6.9 dBmV45.8 dB00
3Locked256 QAM14507000000 Hz6.8 dBmV45.8 dB00
4Locked256 QAM15513000000 Hz6.7 dBmV45.8 dB00
5Locked256 QAM16519000000 Hz6.6 dBmV45.7 dB00
6Locked256 QAM17525000000 Hz6.5 dBmV45.7 dB00
7Locked256 QAM18531000000 Hz6.3 dBmV45.5 dB00
8Locked256 QAM19537000000 Hz6.2 dBmV45.4 dB00
9Locked256 QAM20543000000 Hz6.0 dBmV45.3 dB00
10Locked256 QAM21549000000 Hz5.9 dBmV45.2 dB00
11Locked256 QAM22555000000 Hz5.7 dBmV45.1 dB00
12Locked256 QAM23561000000 Hz5.8 dBmV45.1 dB00
13Locked256 QAM24567000000 Hz5.7 dBmV45.0 dB00
14Locked256 QAM25573000000 Hz5.5 dBmV45.0 dB00
15Locked256 QAM26579000000 Hz5.6 dBmV45.0 dB00
16Locked256 QAM27585000000 Hz5.5 dBmV44.9 dB00
17Locked256 QAM29597000000 Hz5.4 dBmV44.7 dB00
18Locked256 QAM30603000000 Hz5.3 dBmV44.6 dB00
19Locked256 QAM31609000000 Hz5.1 dBmV44.5 dB00
20Locked256 QAM32615000000 Hz5.1 dBmV44.5 dB00
21Locked256 QAM33621000000 Hz5.2 dBmV44.4 dB00
22Locked256 QAM34627000000 Hz5.2 dBmV44.4 dB00
23Locked256 QAM35633000000 Hz5.0 dBmV44.2 dB00
24Locked256 QAM36639000000 Hz4.9 dBmV44.1 dB00
25Locked256 QAM37645000000 Hz5.0 dBmV44.1 dB00
26Locked256 QAM38651000000 Hz4.9 dBmV44.0 dB00
27Locked256 QAM39657000000 Hz4.9 dBmV43.9 dB00
28Locked256 QAM40663000000 Hz4.9 dBmV43.9 dB00
29Locked256 QAM41669000000 Hz4.8 dBmV43.8 dB00
30Locked256 QAM42675000000 Hz4.7 dBmV42.4 dB00
31Locked256 QAM43681000000 Hz4.5 dBmV43.6 dB00
32Locked256 QAM44687000000 Hz4.7 dBmV43.3 dB00
 

Upstream Bonded Channels

ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA205120 Ksym/sec16400000 Hz29.0 dBmV
2LockedATDMA185120 Ksym/sec29200000 Hz30.5 dBmV
3LockedATDMA195120 Ksym/sec22800000 Hz29.8 dBmV
4LockedATDMA175120 Ksym/sec35600000 Hz30.8 dBmV
5Not LockedUnknown0000.0 dBmV
6Not LockedUnknown0000.0 dBmV
7Not LockedUnknown0000.0 dBmV
8Not LockedUnknown0000.0 dBmV
 

Downstream OFDM Channels

ChannelLock
Status
Modulation /
Profile ID
Channel
ID
FrequencyPowerSNR /
MER
Active Subcarrier
Number Range
Unerrored
Codewords
Correctable
Codewords
Uncorrectable
Codewords
1Locked0 ,1 ,2 ,3193693000000 Hz4.78 dBmV42.8 dB1108 ~ 29872452932777157400
2Not Locked000 Hz0 dBmV0 dB0 ~ 4095000
 

Upstream OFDMA Channels

ChannelLock StatusModulation / Profile IDChannel IDFrequencyPower
1Not Locked000 Hz0 dBmV
2Not Locked000 Hz0 dBmV
Message 1 of 10
DarrenM
Sr. NETGEAR Moderator

Re: CAX80 Unable to connect to online game servers

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

Message 2 of 10
bilal_ahmed
Aspirant

Re: CAX80 Unable to connect to online game servers

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

Message 3 of 10
FURRYe38
Guru

Re: CAX80 Unable to connect to online game servers

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...

Message 4 of 10
bilal_ahmed
Aspirant

Re: CAX80 Unable to connect to online game servers

Firmware VersionV2.1.5.2

 

TimePriorityDescription
Wed Jul 12 11:26:17 2023Notice (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 2023Notice (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 1970Notice (6)Honoring MDD; IP provisioning mode = IPv6
Thu Jan 1 00:00:43 1970Critical (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 2023Critical (3)Resetting the cable modem due to docsDevResetNow
Mon Jul 3 08:52:11 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 1970Critical (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 2023Critical (3)Resetting the cable modem due to docsDevResetNow
Sat Jun 24 15:22:43 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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. 

 

 

Message 5 of 10
FURRYe38
Guru

Re: CAX80 Unable to connect to online game servers

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. 

 

 

Message 6 of 10
Kitsap
Master

Re: CAX80 Unable to connect to online game servers

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

 

 

Message 7 of 10
bilal_ahmed
Aspirant

Re: CAX80 Unable to connect to online game servers

No
Message 8 of 10
bilal_ahmed
Aspirant

Re: CAX80 Unable to connect to online game servers

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. 

Message 9 of 10
Kitsap
Master

Re: CAX80 Unable to connect to online game servers



@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?

 

 

Message 10 of 10
Top Contributors
Discussion stats
  • 9 replies
  • 753 views
  • 0 kudos
  • 4 in conversation
Announcements

Orbi WiFi 7