Your Xbox Series S shows NAT Type Strict or NAT Type Failed, and multiplayer won't connect. Party chat drops. Downloads stall. The network test keeps giving you a red X on NAT. This is almost always a router configuration issue, not a problem with your console.
Start with the built-in check. Open Settings > General > Network settings > Test network connection. The Series S runs through connection quality, latency, packet loss, and NAT type. If NAT comes back Strict, the fix chain starts here.
If the test failed entirely (no connection at all), that's a different problem. This guide covers the strict and failed NAT scenarios specifically.
Why the Series S Shows Strict NAT
Three things cause it most of the time:
- Double-NAT: your ISP's modem-router combo plus your own router both handing out IPs. Xbox sees two layers of NAT and picks Strict.
- UPnP disabled: the router can't automatically open the ports Xbox Live needs.
- Cabled ISP with no public IP: some carriers drop you behind Carrier-Grade NAT. You can fix that, but it requires a phone call to the ISP.
The Series S networking hardware tops out at WiFi 5, so don't expect WiFi 6 or 7 performance. That's fine for most gaming, but if you're in a dense apartment complex, wireless congestion makes NAT detection flaky.
Restart Everything Properly
Unplug your modem and router for a full 30 seconds. Plug the modem back in first, wait until all the online lights are solid (usually 2-3 minutes), then plug in the router. Wait another 2 minutes.
On the Series S, do a full power cycle. Hold the power button on the front of the console for 10 seconds until it shuts off completely. Unplug the power cord for 30 seconds, plug it back in, and start normally. This clears any stale network cache on the console itself.
The soft restart alone fixes probably half of intermittent NAT issues by forcing the Series S to request a fresh DHCP lease from the router.
Run Xbox's Built-in Fix
Microsoft added a network troubleshooting tool right in the settings menu. Go to Settings > General > Network settings > Advanced settings > Alternate port selection. Set it to Manual and try a different port (a common suggestion is 3074).
While you're there, go back to the Network settings page and select NAT type under Wired or Wireless status. Xbox will run a check and sometimes clear a false Strict reading.
Plug In a Wired Connection
The Series S has an ethernet port on the back. If your console is within cable range of the router, a wired connection eliminates wireless interference as a variable entirely. Grab a Cat5e or Cat6 cable and run it directly from the router LAN port to the Series S.
Go to Settings > General > Network settings and confirm it shows Wired. Run the network test again. Wired connections on the Series S typically show Open NAT within seconds, assuming the router side is configured correctly.
If wired fixes it and you really can't run a cable, focus on your WiFi channel congestion (covered later).
Fix Double-NAT by Bridging the Modem
This is the single most common cause of persistent Strict NAT. If your ISP gave you a modem-router combo (Xfinity, AT&T, Spectrum, etc.) and you have your own router plugged into it, you're running two routers. The Xbox sees the second NAT layer and defaults to Strict.
The fix is to put the ISP modem into bridge mode. Log into the modem's admin panel (usually 192.168.0.1 or 192.168.1.1) and look for Bridge Mode, IP Pass-Through, or DMZ Plus. Once enabled, the ISP unit becomes a dumb modem and your router handles everything.
After changing the setting, restart the modem, router, and Series S. The NAT type should drop to Open within a few minutes.
Enable UPnP on Your Router
Universal Plug and Play lets your Xbox automatically request and open the ports it needs without manual configuration. If UPnP is disabled on your router, the Series S can't negotiate its NAT properly.
Log into your router admin panel and find the UPnP setting. It's usually under Advanced > NAT or Advanced > Security. Make sure it's enabled. Disable and re-enable it if it was already on, then restart the console.
UPnP is safe to keep on for a console. The Xbox uses it only for Live traffic and won't open random ports.
Port Forward Manually (When UPnP Isn't Cutting It)
Some routers handle UPnP poorly, especially older models or ISP-provided units. If UPnP is on and you still get Strict NAT, forward the ports directly. Microsoft's official ports for Xbox Live:
- TCP: 3074
- UDP: 3074, 88, 500, 3544, 4500
Find your Series S local IP by going to Settings > General > Network settings > Advanced settings > IP settings. Write down the IPv4 address. Then set a DHCP reservation in your router so that IP never changes.
Go into your router's port forwarding section and create entries for each port listed above, pointing to the Xbox's reserved IP. Restart the console and test again.
Is the Console Up to Date?
The current Xbox system software build as of April 2026 is OS 10.0.26100.7807. Earlier builds had reported issues with network stack stability during Quick Resume transitions. If your console hasn't updated recently, that could be a factor.
Open Settings > System > Updates and check for updates. If the console won't reach update servers (chicken-and-egg with a bad network), download the system update file to a USB drive from a PC and install it offline via the offline system update tool at Settings > System > Console info > Reset console > Keep my games & apps.
Use Google or Cloudflare DNS
ISP default DNS servers are sometimes slow or buggy, which can make the Xbox Live connection test time out or report NAT incorrectly. Switching DNS is a quick test that costs nothing.
Go to Settings > General > Network settings > Advanced settings > DNS settings. Switch from Automatic to Manual. Enter Primary as 1.1.1.1 and Secondary as 1.0.0.1 for Cloudflare, or 8.8.8.8 and 8.8.4.4 for Google. Save and run the network test again.
Clean Up Your WiFi Channel
The Series S connects on WiFi 5 (5GHz) or 2.4GHz. In dense housing, 2.4GHz channels are overcrowded with neighbor networks, Bluetooth devices, and microwaves. That packet interference can cause the NAT detection handshake to fail.
Open your router admin panel and check which channel your 5GHz network is using. Channels 36-48 (low band) tend to be less congested in most areas. Set the channel manually or toggle Auto on and off to force a rescan.
On the Series S, make sure you're connected to the 5GHz SSID, not the 2.4GHz one. If your router broadcasts them as separate networks (most do), connect to the one labeled with -5G. The 2.4GHz band works for web browsing but introduces latency issues in multiplayer.
Reset to Factory Defaults (Keep Your Games)
If you've tried everything and the Series S still shows Strict NAT or the test fails, reset the console's network settings back to zero. Open Profile & system > Settings > System > Console info > Reset console.
Choose Reset and keep my games & apps. This wipes all system settings including network configs, accounts, and preferences, but leaves your installed games and Quick Resume snapshots intact. After the restart, go through the initial network setup fresh, re-enter your WiFi password, and run the test.
This is the nuclear option for software-level network corruption. If your Series S still shows Strict NAT after a factory reset, the issue is 100% on the router or ISP side, not the console.
