Network and quality
NAT, double NAT and CGNAT in Xbox Remote Play: how to check your network
Compare Remote Play at home and over mobile data first, then check your network layout and WAN IPv4 address. A NAT status alone does not explain a failure.
On this page
If Xbox Remote Play works at home but will not connect from elsewhere, first repeat the test with the console switched on, using both your home network and an external network. Then compare the router’s WAN IPv4 address with its external IPv4 address and find out where NAT occurs: at home, at the provider or in both places. Double NAT and CGNAT can complicate connections, but neither automatically makes Remote Play unavailable.
Separate a network failure from a console problem first
- Turn on the Xbox normally and confirm that remote features are enabled. Keep the console on during this test; test wake-up separately.
- Connect the XBPlayer device to the same home network as the Xbox. Start Remote Play from your console and record whether the stream appears or which error message you receive.
- End the session. On your phone, turn off Wi-Fi and try again over mobile data with the same client and account. If possible, try another external network too.
- On the Xbox itself, open network settings, run the NAT test and record the status and any additional messages. Compare these with the connection attempts rather than treating them as a final diagnosis.
If even the home-network test fails, first check remote features, account sign-in and console availability. If one external network works and another does not, investigate the receiving device’s network using the Remote Play away-from-home guide. If you can connect only when the Xbox is already on, move on to remote wake-up troubleshooting.
Where a second layer of NAT can occur
NAT translates network addresses. In a typical home IPv4 network, a router lets several devices with internal addresses access the internet through one connection. A second translation layer may be in another home router or the provider’s network.
| Setup | Path from the Xbox | What to check |
|---|---|---|
| One layer of home NAT | Xbox → home router → internet | Which address the router receives from the provider |
| Double NAT at home | Xbox → your router → provider’s modem-router → internet | Whether both devices route traffic using NAT |
| CGNAT | Xbox → home router → provider NAT → internet | Whether the provider shares one public IPv4 address among several customers |
Two boxes at home do not necessarily mean double NAT: one may be a modem without routing or an access point. Likewise, having only one router in your home does not rule out CGNAT. Home double NAT and CGNAT can exist together. Record the models and operating modes before changing anything.
How to compare WAN and external IPv4 addresses
In the router’s interface, find the IPv4 address of the active internet connection, usually under WAN or Internet. You need that connection’s address, not the Xbox address or the address used to open the router settings. Then use an external-IP checker on a device connected to the same home network, and choose the IPv4 result specifically.
Compare addresses obtained at roughly the same time over the same internet connection. An active VPN, proxy or second connection may change the test route. If you can temporarily disable the VPN, repeat the comparison without it; otherwise, remember that you are seeing the tunnel’s exit address. Comparing IPv4 with IPv6 tells you nothing about an additional IPv4 NAT layer.
| WAN IPv4 address | What it means | Next step |
|---|---|---|
| 10.0.0.0–10.255.255.255; 172.16.0.0–172.31.255.255; 192.168.0.0–192.168.255.255 | RFC 1918 private ranges: 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16 | Check any upstream home router and ask your provider about the network setup. The address alone cannot tell you where NAT occurs. |
| 100.64.0.0–100.127.255.255 | Shared Address Space, 100.64.0.0/10 under RFC 6598: a service-provider range separate from RFC 1918 | Ask your provider about CGNAT. This is not a public IPv4 address. |
| Another address | An address outside these four ranges is not necessarily public; other special-purpose ranges exist | Compare it with the external IPv4 address and confirm the address type with your provider. |
A mismatch between WAN and external IPv4 may indicate upstream NAT, but first rule out a different test route. A match does not guarantee that the connections you need are allowed. If there is no WAN IPv4 address, or the interface shows several addresses you cannot identify, do not substitute a local-network address. Ask the provider to explain your connection type.
Check your WAN IPv4 range
Find the router’s active WAN IPv4 address using the instructions above. Enter it to check its range; optionally compare it with the external IPv4 address on the same internet connection.
Private ranges: RFC 1918
10.0.0.0–10.255.255.255, 172.16.0.0–172.31.255.255 and 192.168.0.0–192.168.255.255. If the WAN address is in one of these ranges, find out which upstream device assigned it: a home router or the provider’s network. The address alone does not locate NAT.
Shared Address Space
100.64.0.0–100.127.255.255 is a separate shared range for service-provider networks. Ask your provider about CGNAT. This finding alone does not explain why Remote Play fails.
Special-purpose ranges checked
127.0.0.0–127.255.255.255 is loopback, referring to the device itself; 169.254.0.0–169.254.255.255 is link-local, for communication on the local link; 224.0.0.0–239.255.255.255 is multicast, for group addressing. These are unsuitable for comparison with a normal external IPv4 address. Check where you obtained the address.
Other addresses and manual comparison
Outside the checked ranges; public status and reachability are not established. For a manual comparison, obtain the WAN and external IPv4 addresses at roughly the same time over one internet connection, without a VPN or proxy. A match does not guarantee incoming connections. A mismatch may suggest upstream NAT or a different route, but it does not locate NAT or establish CGNAT.
If the WAN IPv4 address is missing or unclear, ask your provider to describe the connection.
Why NAT status is not a complete answer
The Xbox NAT status helps with troubleshooting, but it does not measure stream quality or confirm access from every external network. If a direct connection is unavailable, XBPlayer may relay the stream through an intermediary server. Whether it can connect still depends on the restrictions of the particular network.
The actual result matters more than one indicator. Record whether the client connected, which network you used and the console’s power state. If streaming already works, there is no need to change addressing solely to obtain a different NAT status.
What to ask your provider before paying for an address
- Does my connection use CGNAT, and is a public IPv4 address assigned directly to my router?
- Does the supplied modem-router perform NAT, and which mode should it use with my own router?
- Can I get a dynamic public IPv4 address, and which restrictions on incoming connections will remain?
- If only a static address is available, exactly which restriction would the service remove, and what does it cost?
Being public and staying the same are different properties: a public IPv4 address can change. A static address is not automatically public either. Confirm both properties. If a provider uses labels such as “white IP” or “gaming IP,” ask for the technical details. Paying for a public IPv4 address does not remove double NAT that remains at home or guarantee a fix for Remote Play.
What to change once the cause is confirmed
With double NAT at home, the aim is to leave one home router performing NAT. Options include bridge mode on the provider’s modem-router while keeping your own router, or access-point mode on the second device while the provider’s router remains in charge. Choose a supported option using the instructions for the exact model.
Before switching modes, save the settings and a way to restore them. Confirm the internet connection parameters and how any TV or phone services use the equipment. After one change, repeat the home and external connection tests. If the connection gets worse, restore the previous configuration. With CGNAT, changing the home router does not remove translation in the provider’s network.
Do not enable DMZ, open ports at random or install a VPN solely because of a NAT message. First find manufacturer or Xbox guidance that matches your setup and the specific change. If you already use a tunnel, check its effect separately using the VPN and Remote Play guide.
Sources and further reading
- RFC 1918: Address Allocation for Private Internets — The three private IPv4 ranges and how they differ from public addressing.
- RFC 6598: IANA-Reserved IPv4 Prefix for Shared Address Space — 100.64.0.0/10 is reserved for Shared Address Space and is separate from RFC 1918.
- IANA: IPv4 Special-Purpose Address Space — Private, shared and other special-purpose ranges. Falling outside the four listed ranges does not prove that an address is public.
- Xbox Remote Play — Remote Play streams games from your own console with remote features enabled. Leave the Xbox switched on when testing the connection.
- XBPlayer: Remote Play and Cloud Gaming — The official app website and download links. Detailed definitions of diagnostics and how settings take effect are covered in the relevant guides.
- TP-Link: Deco with an Existing Router — Double NAT with two routers, access-point mode and bridge mode. The specific switching instructions apply to Deco; use the documentation for other models.
- Google Home and Nest: Bridge mode — Bridge mode addresses specific double-NAT problems; capabilities and limitations depend on the equipment.
Get the key points
Open a summary request with this article’s link. For Gemini, the request is copied — paste it into the chat.