Netduma Fraser

It's just occurred to me, are you trying to match make so you have some consoles on one team and some on the other?

In LAN Settings, set the DHCP lease hours to 168 and apply, this should help with the disconnects, then while connected via ethernet, disable WiFi entirely from the WiFi settings, reboot the router from the interface, wait 2 minutes, access, enable WiFi, apply, reboot from the interface, wait 2 minutes then see if it's more stable from then on.

Yes that's right. You should be able to upgrade yourself now, it's best to try it now otherwise we won't know if the issue is present still

We'll need a direct line through to the R2 so there can't be a double NAT, if you can sort it out using DMZ and modem mode we can connect and force through an upgrade

It may not necessarily be on their side but if you can't make that direct connection to them with a simple ping then that could be why they don't appear on the map

Are ALL your devices connected to the XR? Do you get the same issue direct to the modem?

We'll check that out, thanks for the report! I'd say Classified Games but experiment and see what works best for you.

Ask your friends what their IP address is, then try to ping it using command prompt on the PC, do you get ping responses?

That's very difficult to say, it could be for a number of reasons, do you have QoS active and if so what settings are you using?

It depends, try this: Quit the application/game/client completely Remove device from the Geo-Filter Give PC PlayStation Device Type in the Device Manager (if on PC) Resync from the Geo-Filter Map menu Re-add the device to the Geo-Filter with the manual option Set up the Geo-Filter how you like Wait 2 minutes Boot up application/game/client Then see if it works better and gets you games faster. It would be beneficial to have an Open NAT if you don't already (NAT Type 2 is Open) as it can influence who you're able to connect to but as it's a server based game that is less important.

You don't need to change the DNS at all, it's all automatic and will use the correct DNS that your ISP uses

That's fine to leave it that way, you would see the same behavior on a device connected to the XR for example, the DNS would be the XR LAN IP. It has to go through the device first so that's why it appears there.

No real best in this scenario, I would just suggest keeping your radius on the East Coast of the US so your ping isn't as high

Did you try on a different device to see if the same issue occurs?

You need to set Ping Assist to 0, then it should work correctly

Yes I believe so

Thanks for that, it looks okay, can you see if there is a change after the resync? You do have access to the Early Access group so it would be worth trying that firmware to see if you get the same issue.

I've responded in your other topic

Using any of the pre-installed options for TP in addition to custom port rules there is a high chance it will overlap, we suggest using one or the other. They're different but when using ports for consoles it would be 1024-65535 I believe

If you believe it to be a hardware fault, which is quite possible then you'll need to make a ticket with Netgear support about that, we can only troubleshoot, we can't authorize a replacement for another company.

Reboot the R2 then try to access as soon as possible and put the upgrade through, sometimes the speed at which you do this can help complete it before any issues arise, if that doesn't work try again but with a factory reset

Likely we'll need to update the CoD preset, the Console service should work though, can you confirm if that is the case?

You can just post it here in the topic

Did you change the retries and see if that helped after a reboot?

Interesting, just to double check can you clear your browser cache/cookies and then check the version again? The version can sometimes get cached