NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Mike40
Jul 25, 2024Luminary
XR500 Geo-Filtering not working for COD
Just recently I noticed my games have been crazy lagging. I only play COD on my PC. I live about 50 miles (give or take) from the Chicago server. The server is trash so I pick a server in northern...
FURRYe38
Jul 25, 2024Guru - Experienced User
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-router
Mike40 wrote:
Just recently I noticed my games have been crazy lagging. I only play COD on my PC. I live about 50 miles (give or take) from the Chicago server. The server is trash so I pick a server in northern Georgia since it has a lower ping. I looked today to see what was going on but when I look at Geo-Filter it isn't connected to any server. I thought maybe it was a glitch on my PC so I looked in the app too and nothing. I'm 99.99% sure I'm connecting to the Chicago server since it is the closest to me.
I read through other posts and it said to quit the game, remove the device, resync cloud, wait 2 minutes then try again. This didn't work. I also tried changing my PC to console, did all the steps again, and the same thing. I tried doing all the steps again and restarting the router after, same thing.
I've tried using QOS with different settings or turning it completely off.
I even connected my PC directly into my CM1200 modem and it got even worse. I was rubberbanding, stuttering, etc so I plugged the PC back into the router.
I've also tried using NordVPN through HybridVPN but it doesn't change anything.
I'm using firmware V2.3.2.134 in case you need to know that.
The game is almost unplayable now because I'm either getting shot by invisible bullets or I'm getting hit marker after hit marker.
Other than factory resetting it (I'm tired of having to factory reset it every time there is an issue), do you have any other suggestions?
Thanks for your assistance.
- Mike40Jul 26, 2024Luminary
I was asked for this last time I had an issue. You guys blame it on the internet connection and my ISP says there isn't anything wrong with the line. I always have these critical things on there but they have been out here, replaced the line, and everything is fine. I play games through Bluestacks, and I play one other mobile game (Mech Arena) that has a PC version. I know the filter is on because when I play Mech Arena, I can't play it unless the filter is off.
Wed Jul 24 16:47:49 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Mon Jul 15 23:57:18 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Mon Jul 15 23:56:43 2024 Critical (3) UCD invalid or channel unusable;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Mon Jul 15 23:56:40 2024 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Mon Jul 15 23:56:39 2024 Critical (3) UCD invalid or channel unusable;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Mon Jul 15 23:56:33 2024 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Mon Jul 15 23:56:28 2024 Notice (6) TLV-11 - unrecognized OID;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01: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) UCD invalid or channel unusable;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Mon Jul 15 04:17:48 2024 Critical (3) UCD invalid or channel unusable;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Mon Jul 15 04:17:42 2024 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Mon Jul 15 04:17:37 2024 Notice (6) TLV-11 - unrecognized OID;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01: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) UCD invalid or channel unusable;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Wed Jun 12 08:32:50 2024 Critical (3) UCD invalid or channel unusable;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Wed Jun 12 08:32:42 2024 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Wed Jun 12 08:32:37 2024 Notice (6) TLV-11 - unrecognized OID;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01: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) UCD invalid or channel unusable;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Sun Jun 09 08:13:45 2024 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=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Sun Jun 09 08:12:16 2024 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=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Fri Jun 07 14:10:49 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Thu Jun 06 01:42:54 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Thu Jun 06 01:42:40 2024 Critical (3) UCD invalid or channel unusable;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Thu Jun 06 01:42:34 2024 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Thu Jun 06 01:42:29 2024 Notice (6) TLV-11 - unrecognized OID;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01: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) UCD invalid or channel unusable;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jun 06 01:18:28 2024 Warning (5) Lost MDD Timeout;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jun 06 01:18:22 2024 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jun 06 01:18:18 2024 Warning (5) Lost MDD Timeout;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Thu Jun 06 01:18:06 2024 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Thu Jun 06 01:18:05 2024 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Thu Jun 06 01:18:00 2024 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Thu Jun 06 01:17:16 2024 Warning (5) MDD message timeout;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; Thu Jun 06 00:04:30 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:cd:d6:6d:31:d4;CMTS-MAC=00:90:f0:7c:01:00;CM-QOS=1.1;CM-VER=3.1; - FURRYe38Jul 26, 2024Guru - Experienced User
There is a reason why we ask for bot of these items from the modem. It gives information and status on the modem and signals up to the modem. Weather GOOD or BAD. Reason for pointing to the modem is that you mentioned already that you directly connected to the modem and the problem got worse. Kinda rules out that the router is the problem. If routers can't get good singals from the ISP modem, then what you see is what you get down stream from the from thru any router.
In this case BAD so far. Now can we get the cable connections status page data as well?
- Mike40Jul 26, 2024Luminary
I don't have an ISP modem I have a CM1200 modem from Netgear. The Netgear is a little better than the Xfinity modem/router that they provide. Filtering out the Chicago server has worked the best for me as far as lag, etc. If I connect to the server i have a horrible experience no matter what. The reason I went with this set up was to eliminate the issues with connecting to whatever server. It has worked the way it is supposed to for about 4 months (give or take) then I have another issue with something else. Here is the log you requested.
Cable ConnectionApply Cancel 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 543000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enabled BPI+ IP Provisioning Mode Honor MDD honorMdd(4) Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 20 543000000 Hz 1.1 dBmV 42.8 dB 97 0 2 Locked QAM256 13 501000000 Hz 1.3 dBmV 43.2 dB 210 0 3 Locked QAM256 14 507000000 Hz 1.2 dBmV 43.1 dB 200 0 4 Locked QAM256 15 513000000 Hz 1.2 dBmV 43.1 dB 164 0 5 Locked QAM256 16 519000000 Hz 1.2 dBmV 43 dB 159 0 6 Locked QAM256 17 525000000 Hz 1.2 dBmV 43 dB 154 0 7 Locked QAM256 18 531000000 Hz 1.4 dBmV 43 dB 117 0 8 Locked QAM256 19 537000000 Hz 0.9 dBmV 42.7 dB 76 0 9 Locked QAM256 21 549000000 Hz 1 dBmV 42.8 dB 36 0 10 Locked QAM256 22 555000000 Hz 1.2 dBmV 42.8 dB 47 0 11 Locked QAM256 23 561000000 Hz 1.3 dBmV 42.9 dB 37 0 12 Locked QAM256 24 567000000 Hz 1.4 dBmV 43 dB 62 0 13 Locked QAM256 25 573000000 Hz 1.2 dBmV 42.9 dB 24 0 14 Locked QAM256 26 579000000 Hz 1.5 dBmV 43 dB 33 0 15 Locked QAM256 27 585000000 Hz 1.4 dBmV 42.9 dB 7 0 16 Locked QAM256 28 591000000 Hz 1.9 dBmV 43.1 dB 16 0 17 Locked QAM256 29 597000000 Hz 1.3 dBmV 42.9 dB 7 0 18 Locked QAM256 30 603000000 Hz 1.8 dBmV 43 dB 15 0 19 Locked QAM256 31 609000000 Hz 1.5 dBmV 43 dB 9 0 20 Locked QAM256 32 615000000 Hz 1.8 dBmV 43 dB 10 0 21 Locked QAM256 33 621000000 Hz 1.5 dBmV 43 dB 1 0 22 Locked QAM256 34 627000000 Hz 2 dBmV 43.1 dB 1 0 23 Locked QAM256 35 633000000 Hz 1.6 dBmV 43 dB 4 0 24 Locked QAM256 36 639000000 Hz 2.1 dBmV 43.1 dB 0 0 25 Locked QAM256 37 645000000 Hz 1.6 dBmV 42.9 dB 9 0 26 Locked QAM256 38 651000000 Hz 2.1 dBmV 43.1 dB 7 0 27 Locked QAM256 39 657000000 Hz 1.3 dBmV 42.8 dB 3 0 28 Locked QAM256 40 663000000 Hz 1.6 dBmV 42.8 dB 3 0 29 Locked QAM256 41 669000000 Hz 1.6 dBmV 42.8 dB 2 0 30 Locked QAM256 42 675000000 Hz 1.9 dBmV 42.1 dB 5 0 31 Locked QAM256 43 681000000 Hz 1.8 dBmV 42.9 dB 1 0 32 Locked QAM256 44 687000000 Hz 1.8 dBmV 42.9 dB 5 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 1 5120 Ksym/sec 16400000 Hz 46.8 dBmV 2 Locked ATDMA 2 5120 Ksym/sec 22800000 Hz 46.8 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 29200000 Hz 46.8 dBmV 4 Locked ATDMA 4 5120 Ksym/sec 35600000 Hz 46.8 dBmV 5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV Downstream OFDM Channels Channel Lock
StatusModulation /
Profile IDChannel
IDFrequency Power SNR /
MERActive Subcarrier
Number RangeUnerrored
CodewordsCorrectable
CodewordsUncorrectable
Codewords1 Locked 0 ,1 ,2 ,3 193 957000000 Hz 2.8 dBmV 42.4 dB 148 ~ 3947 9896466147 6592800824 0 2 Not Locked 0 0 0 Hz 0 dBmV 0.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 Extended Upstream Transmit Power Enable Extended Upstream Transmit Power Current System Time:Fri Jul 26 17:36:37 2024 System Up Time:10 days 17:40:43
Help Center
Show/Hide Help Center