NHL26 Failed to find opponent

I ran the NAT test while plugged into the hotel LAN port and it says my NAT Type is Moderate.  I next connected to WiFi via my laptop and the NAT type changes to Open.  Of note, when connected via my laptop my IP now starts with 192.

Back to the 172 IP, why is the eSim I got for my phone using that?  I thought it was a hotel thing.

Fox, the error I get when connected to my laptop using a VPN is "Can't get an IP address".

Here are the steps to fix this:

​1. Change the VPN Protocol

​This is the most common fix. Open your VPN app's settings and look for Protocol or Connection.

​If it is set to "Automatic," manually switch it to WireGuard or OpenVPN (UDP or TCP).

​Different protocols use different methods to request IP addresses, and switching often bypasses the glitch.

​2. Flush DNS and Reset Network Stack

​Windows might be holding onto outdated or corrupt routing information.

​Type cmd in the Windows search bar, right-click it, and select Run as Administrator.

​Type ipconfig /flushdns and press Enter.

​Type netsh winsock reset and press Enter.

​Restart your computer.

​3. Cycle the Virtual Network Adapter

​The VPN creates a virtual "TAP" or "TUN" adapter that can sometimes hang.

​Press Win + R, type ncpa.cpl, and press Enter.

​Find the adapter associated with your VPN (it usually has the VPN's name in it).

​Right-click it, select Disable, wait 10 seconds, then right-click again and select Enable.

​4. Disable IPv6

​Some VPNs struggle when Windows tries to prioritize an IPv6 address over the VPN's IPv4 tunnel.

​Go back to the ncpa.cpl window from the previous step.

​Right-click your primary connection (Wi-Fi or Ethernet) and select Properties.

​Uncheck Internet Protocol Version 6 (TCP/IPv6).

​Click OK and try connecting the VPN again.

​5. Check Firewall/Antivirus

​Third-party security suites (like Norton, Bitdefender, or McAfee) can sometimes block the "handshake" required to assign an IP. Try disabling your firewall briefly to see if the VPN connects.

​Final Tip:

If the issue persists, reinstalling the VPN client is often the best move. It forces Windows to reinstall the virtual drivers, which fixes most underlying configuration errors.

hopefully you can get back online and enjoy the rest of your Friday!

Here is the breakdown of why those IPs look different and what it means for your NAT type:

​1. The 192.x.x.x IP (Laptop Wi-Fi)

​When you connect to your laptop's Wi-Fi (likely a hotspot), your laptop acts as a router.

​192.168.x.x is the most common range for private home or local networks.

​NAT Type Open: Your laptop is essentially giving your device a "clear path" to the internet. Because the laptop is doing the heavy lifting and isn't restricting specific ports, your connection appears "Open."

​2. The 172.x.x.x IP (Hotel LAN & eSim)

​It’s easy to assume a 172 IP is specific to the hotel, but it is actually a standard Private IP range (specifically 172.16.0.0 to 172.31.255.255).

​Why the eSim uses it: Mobile carriers almost never give your phone a "Public IP" because there aren't enough IPv4 addresses in the world. Instead, they use CGNAT (Carrier-Grade NAT). They put your phone on a giant internal network (using that 172 range) and then funnel thousands of users through one single public IP.

​Why the Hotel LAN uses it: Large enterprises and hotels use the 172 range because it allows for thousands of more internal addresses than the 192 range.

​NAT Type Moderate: Hotels often block certain "ports" for security and to prevent guests from hogging bandwidth with P2P file sharing or hosting servers. This is why it shows as "Moderate"—the network is letting you out, but it's not letting unsolicited traffic back in.

​Why the VPN "Can't get an IP" on the 172 Network

​This is likely the missing link. When you are on the Hotel LAN (172.x.x.x), the hotel's "Moderate" NAT or firewall might be blocking the specific DHCP or Tunneling requests your VPN needs to establish its own virtual IP address.

​Summary of the IP "Personalities":

| IP Range | Common Use | Why you see it here |

| :--- | :--- | :--- |

| 192.168.x.x | Small Networks | Your laptop's hotspot creates this. |

| 172.16.x.x | Large Networks | Used by the Hotel and your Mobile Carrier (eSim). |

| 10.x.x.x | Huge Networks | Often used by VPNs internally or massive corporations. |

​Since it's you're dealing with hotel LAN ports, it sounds like you're traveling! If the LAN port is giving you trouble with the VPN, the laptop Wi-Fi "Open" NAT is definitely your more stable bet for now.

​Does your VPN software have a "Stealth" or "Obfuscation" setting? Turning that on might help it "sneak" past the hotel's 172-range firewall.

​Fox, wow!!  Thank you for all of this.  I really appreciate you sending all of this to try.

1. Change the VPN Protocol

I was able to change this setting in each of my VPN’s, but to no luck.  Of note, Nord would not connect at all with UDP selected.

From your other post, I did not see Stealth or Obfuscation on either of my VPN’s.  Hide.me has a setting called SSTP; see HF2.  And it has a setting to disable Stealth Modde (see HF3), which I did not check.  And Nord has a setting called “Stay Invisible on LAN” (HF5) that as the closet thing I found to “Stealth”.

​​2. Flush DNS and Reset Network Stack

I was able to find and perform these steps, but with no luck. 

​​3. Cycle the Virtual Network Adapter

This step gave me troubles.  I was able to disable the VPN’s adapters, but nothing would happen when I clicked Enable after waiting 10 seconds.  See HF6.  Also, see HF1 for the error I was getting.

​​4. Disable IPv6

This was already disabled.  So, I did not make any changes.

​​5. Check Firewall/Antivirus

Turned off all three firewalls; see HF4.  I was not sure which one I needed to disable, so I turned off all three.  That did not work, at first.  But then I turned off each of my VPN’s, and tried with them off and the firewalls off.  I was able to join a match.  I got about halfway through the first period and it kicked me off.  I tried to recreate, but never could join again. 

​​Final Tip:

Tried this, no luck.  Then went back in and reperformed Step 1, again no luck.

Since you managed to join a match briefly before being kicked, it proves the connection is possible, but it's being "choked" by either the VPN protocol or your router.

​Here is the step-by-step fix in English to help you navigate your settings:

​1. Fix NordVPN: Enable "Obfuscated Servers"

​The reason you couldn't connect via UDP is likely because your network is filtering VPN traffic. To fix this, you need to use TCP combined with Obfuscation:

​Open NordVPN Settings (the gear icon).

​Go to Connection.

​Set VPN Protocol to OpenVPN (TCP).

​Go back to the main screen. Look for Specialty Servers.

​Select Obfuscated Servers. This masks your VPN traffic as regular web browsing, which usually bypasses the "kick" you experienced.

​2. Fix the Network Adapter "Enable" Issue (HF6)

​If the adapter won't enable manually, Windows is likely experiencing a "driver hang."

​Instead of the Control Panel, use the VPN app's built-in repair tool.

​In NordVPN: Go to Settings > Advanced > Run Diagnostics > Reset App.

​In Hide.me: Go to Settings > Advanced > Reinstall VPN Adapter.

​3. Adjust MTU Settings (Prevents being kicked mid-game)

​The "kick" halfway through the first period often happens because the data packets are too large for the VPN tunnel (MTU fragmentation).

​Open Command Prompt (CMD) as Administrator.

​Type this command and press Enter:

netsh interface ipv4 set subinterface "Ethernet" mtu=1400 store=persistent

(If you are on Wi-Fi, replace "Ethernet" with "Wi-Fi").

​This shrinks the packets so they slide through the VPN tunnel without getting dropped.

​4. Router Settings (The "Invisible" Firewall)

​Since turning off your PC firewalls (HF4) only worked temporarily, your Router’s built-in firewall is likely the culprit.

​Log into your router (usually 192.168.1.1 in your browser).

​Look for Security or Firewall settings.

​Ensure VPN Passthrough is set to Enabled.

​Disable "IP Flood Detection" or "Port Scan Detection" if you see them, as these often mistake gaming data for an attack.

​5. Hide.me Specifics

​SSTP Protocol: This is very slow for gaming but very hard to block. If nothing else works, try SSTP, but expect higher ping.

​Stealth Mode: Ensure "Disable Stealth Mode" is unchecked (meaning Stealth is active).

​Try the NordVPN "Obfuscated + TCP" method first. It is the most robust way to stay connected without the server kicking you out.

​How did the MTU command work for you?

Thanks Fox, I'll try these when I wake.

But, when you say "your router", do you mean the hotel's router?  Because I doubt I have access to alter any settings there.  Or did you mean the mobile hotspot from my laptop?

​The "Hotel Router" Problem

​When I mentioned "your router," I meant the Hotel's Router. You are correct—you cannot access their settings to change things like "VPN Passthrough" or "MTU."

​Hotels often have very strict firewalls to prevent people from using too much bandwidth or to block "suspicious" traffic like VPNs. This explains why:

​NordVPN UDP failed: The hotel is likely blocking UDP ports used by VPNs.

​You were kicked: The hotel's "Load Balancing" or "Security" probably saw your high-speed gaming data and cut the connection.

​How to Fix This in a Hotel (Plan C)

​Since you can't touch the hotel's hardware, we have to bypass their restrictions entirely:

​1. The "Mobile Hotspot" from your Phone (NOT the Laptop)

​The Fix: Use your Phone's Cellular Data (4G/5G) as a hotspot and connect your laptop to that.

​Why: This bypasses the hotel's router and firewall completely. If the game works on your phone's data, then we know the hotel's Wi-Fi is the culprit.

​2. Use NordVPN "Obfuscated Servers" (Crucial for Hotels)

​As we discussed, if you must use the hotel Wi-Fi, you must use OpenVPN (TCP) + Obfuscated Servers in NordVPN. This makes the hotel's router think you are just browsing a normal website, so it won't block you as easily.

​3. The "Mobile Hotspot" from your Laptop

​If you meant a hotspot created by your laptop (sharing the hotel Wi-Fi to another device), that will still be limited by the hotel's main router. It won't help with the "kick" issue.

Thanks again Fox.  Here were the results.  This is all using Nord, as it seems more robust that Hide.me.  Still no joy on getting this to work.

1. Fix NordVPN: Enable "Obfuscated Servers"

​Did this and received this message from my Xbox:  DNS isn’t resolving Xbox server names

Also, see HF7 for what it looks like on Nord.

​2. Fix the Network Adapter "Enable" Issue

​Done.

​3. Adjust MTU Settings (Prevents being kicked mid-game)

​Done.

​As for using my phone as a mobile hotspot, my U.S. based plan does not have the data or bandwidth to support gaming.  And I did try a local eSim on my phone and tried to use it as a hotspot again, but the same issue as the hotel, seemed blocked and also used a 172 IP.

As a reminder Halo works.  I have no issue matchmaking with that game.  For some reason that one works.  And I am plugged directly into the hotel LAN port to my Xbox.  No hot spot or VPN in use there.  It's only NHL26 that isn't working.