NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Mike40's avatar
Mike40
Luminary
Jul 25, 2024

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

54 Replies

  • The fact you're getting this when connected directly to the modem (which means no other devices or router settings could be impacting you) and you're still having issues means it's either purely on the game side or potentially on the ISP side.

    For the Geo, check the IP on the PC itself then try to match it to the device you think it is on the Device Manager, do they match?
    • Mike40's avatar
      Mike40
      Luminary

      COD has never worked well connecting right to the modem.  That is why I bought the XR500.  For some reason, Comcast/Xfinity works like crap for COD.  I have been playing for like 10 - 12 years and it's always been like that.  I have lived at different houses with different ISPs, I even used my phone as a hotspot for about a year.

      My PC has a dedicated IP address, plus I named it "Hardlined PC" after the last time I factory reset the router because of issues.

      Any other suggestions why the Geo-Filter just stopped working?

      Other than having to factory reset it yet again, I'm willing to try anything to fix it.

      Plus I STILL have the same issue that I messaged you guys about awhile back that if I don't reset the router every time before I play, I always lag.

      • Netduma-Fraser's avatar
        Netduma-Fraser
        NetDuma Partner
        That does sound like there is an inherent issue then that the router potentially won't be able to resolve. Is the PC showing online on the Device Manager? How have you added it to the Geo-Filter?
  • FURRYe38's avatar
    FURRYe38
    Guru - 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.


     

    • Mike40's avatar
      Mike40
      Luminary

      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 2024Critical (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 2024Notice (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 2024Critical (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 2024Critical (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 2024Critical (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 2024Notice (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 2024Notice (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 EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
      Time Not EstablishedCritical (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 EstablishedCritical (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 2024Critical (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 2024Notice (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 2024Notice (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 EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
      Time Not EstablishedCritical (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 EstablishedCritical (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 2024Critical (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 2024Notice (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 2024Notice (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 EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
      Time Not EstablishedCritical (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 EstablishedCritical (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 2024Notice (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 2024Notice (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 2024Critical (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 2024Notice (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 2024Critical (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 2024Notice (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 2024Notice (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 EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
      Time Not EstablishedCritical (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 EstablishedCritical (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 2024Warning (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 2024Critical (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 2024Warning (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 2024Critical (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 2024Critical (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 2024Critical (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 2024Warning (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 2024Critical (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;
      • FURRYe38's avatar
        FURRYe38
        Guru - 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?