Forum Discussion
35 Replies
- FoxHoundTiger1 month agoNew Veteran
sounds like you've hit the classic "DNS blockade." When the Xbox says it can’t resolve server names, it basically means the connection is there, but the console can't find the "phonebook" of the internet to look up where the Xbox servers are located.
Since you've already enabled Obfuscated Servers and adjusted the MTU, the issue is likely that the DNS requests are getting lost between the hotel network and the VPN tunnel.
Here is the game plan to get this working:
1. Manually Set DNS on the Xbox
This is the most effective fix for "DNS isn't resolving" errors. Instead of letting the console guess, we give it a direct path.
On your Xbox: Go to Settings > General > Network settings > Advanced settings > DNS settings.
Select Manual.
Primary IPv4 DNS: 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare).
Secondary IPv4 DNS: 8.8.4.4 or 1.0.0.1.
Save and restart the console.
2. Use NordVPN’s Dedicated DNS
If Google's DNS doesn't cut it, try Nord’s own servers in the Xbox DNS settings:
103.86.96.100
103.86.99.100
3. Switch to OpenVPN (TCP)
Hotels often throttle or block UDP traffic (which VPNs usually use). TCP is more "stealthy" and handles DNS resolution better in restrictive environments.
In the NordVPN app: Go to Settings > Connection.
Change VPN Protocol to OpenVPN (TCP).
Reconnect the VPN and then try the Xbox connection again.
4. Disable "Threat Protection" (CyberSec)
In the NordVPN settings, turn off Threat Protection (or CyberSec). While it’s great for blocking ads, it can act as a secondary firewall that prevents the Xbox from communicating with Microsoft's authentication servers.
5. Verify the "Shared" Adapter
Since you are likely sharing the connection from a PC to the Xbox:
Go to Control Panel > Network and Sharing Center > Change adapter settings.
Find the NordVPN TAP or NordLynx adapter.
Right-click Properties > Sharing.
Ensure "Allow other network users to connect..." is checked and the correct output (the cable or Wi-Fi going to the Xbox) is selected.
Quick Tip for the Hotel 172 IP:
That 172.x.x.x IP confirms you are behind a local private network. This often causes a "Double NAT" issue. If the DNS fix above doesn't work, try turning off the "Obfuscated Servers" setting briefly just to see if the DNS resolves then—sometimes Obfuscation adds a layer of encryption that the hotel's 172-gateway simply doesn't know how to route.
Give the manual DNS (8.8.8.8) a shot first—it's usually the winner!
- hootiehome1 month agoNew Rookie
Hello Again Fox.
1. Manually Set DNS on the Xbox
This is one of the first things EA_Aljo had me try. But that was with the LAN cable connected. Tried it here through the laptop with Nord on = no joy.
2. Use NordVPN’s Dedicated DNS
Tried this = no joy.
3. Switch to OpenVPN (TCP)
This seems similar to what we tried in the past, but I tried it again = no joy.
4. Disable "Threat Protection" (CyberSec)
I did not find a setting with this exact title, but everything is turned off. See HF9.
5. Verify the "Shared" Adapter
This was giving me errors when I tried to select it. Am I in the correct area? See HF8.
Also, can you help my troubleshooting brain as to why Halo works so well with online matchmaking, but not NHL26?
- FoxHoundTiger1 month agoNew Veteran
I think the issue is the hotel's network stability. NHL is way more sensitive to jitter and packet loss than games like Halo. I've exhausted all troubleshooting steps, so I'm convinced there’s nothing more that can be done.
I’m sorry about this, but I think the hotel network just can't handle this specific game. I've tried everything on my end, so I believe there's nothing more that can be done.
- hootiehome1 month agoNew Rookie
Understood. Thanks for all of the tips and tricks Fox!!
- FoxHoundTiger1 month agoNew Veteran
And thanks to you
Featured Places
NHL 26 Technical Issues & Bug Reports
Technical issues with your NHL 26 game? Do you have a bug in your game? Get help from the community!Latest Activity: 2 hours agoCommunity Highlights
- EA_Aljo8 months ago
Community Manager