Fix Network Incompatible in Grounded 2 Multiplayer (PC & Xbox)

Why I Wrote This (and What Finally Worked)

After spending two late nights wrestling with “Network incompatible” in Grounded 2, I finally pinned down the real culprits: mismatched game versions, Xbox account/crossplay settings, and a sneaky NAT issue on my router. I play on PC (Steam) but my group is a mix of Steam, Microsoft Store, and Xbox Series X. I wasted hours restarting the game before realizing the fix needed a sequence. Below is the order that consistently got us connected in under 10 minutes. Do it in order-skipping steps was my biggest mistake.

Step 1 – Verify Everyone Is on the Exact Same Version

This was my breakthrough. Grounded 2 refuses crossplay if versions don’t match exactly, down to hotfix digits. Don’t assume auto-updates worked.

On PC (Steam):

• Highlight Grounded 2 → right-click → Properties → Updates and confirm it’s set to keep updated.
• Check Properties → Betas. Set to None unless your entire party is on the same test branch.
• Launch the game and compare the build number on the main menu (bottom right) with your friends. It must match exactly.

On PC (Microsoft Store/Xbox app):

• Open the Xbox app → find Grounded 2 → click Update if available.
• Make sure the Gaming Services app is installed and up-to-date (it powers Xbox Live on PC).

On Xbox consoles:

• On the Home screen, highlight Grounded 2 → press the Menu button → Manage game and add-ons → Updates. Install everything.

Don’t make my mistake of assuming “it auto-updated.” Confirm the number on everyone’s title screen. If the numbers differ, restart the client (and Steam/Xbox app) to force the patch.

Step 2 – Enable Crossplay and Sign in to Xbox Live

Grounded 2 uses Xbox Live for friends and invites even on Steam. If you’re not signed in, or your privacy blocks cross-network play, you’ll get endless “Network incompatible” or failed joins.

In-game (all platforms):

• From the main menu, check the top-right profile indicator. If it’s blank, choose Sign in and log into your Xbox/Microsoft account.
• Open the in-game Options → Multiplayer (or similar) and ensure Crossplay is enabled.

Xbox account privacy (PC via Xbox app or Xbox console):

• Go to Settings → Account → Privacy & online safety.
• Select Xbox privacy → View details & customize.
• Set multiplayer and cross-network play options to Allow.

I burned 30 minutes because my friend’s “cross-network play” was set to Block. Flip those to Allow, then fully restart the PC/console. Also, if your Steam name doesn’t show in the Xbox friends list, add each other via Xbox Game Bar on PC: press Win + G → Xbox Social and add Gamertags there.

Step 3 — Fix Xbox Services on Windows (PC)

On Windows, Xbox Live relies on background services. If they’re stopped or set to Manual, you’ll see flaky multiplayer or “can’t reach servers.”

• Press Win and type “Services” → open it.
• Find and set each of these to Startup type: Automatic, then click Start if not running, and Apply → OK:
  • Xbox Live Auth Manager
  • Xbox Live Networking Service
  • Xbox Accessory Management Service (if present)
  • Gaming Services
  • IP Helper (needed for Teredo/IPv6 tunneling)

Then check Windows’ Xbox network test: Settings → Gaming → Xbox Networking. Wait for the scan. If it says Server connectivity: Blocked or Teredo issues, continue to the NAT section below. I had “Teredo is unable to qualify” and fixing that unlocked invites instantly.

Step 4 — NAT, Ports, and Router Setup

This was the silent killer for us. NAT type must be Open (or at least Moderate on both ends) for stable joining/hosting. Double NAT will cause headaches.

Check NAT type:

• PC: Settings → Gaming → Xbox Networking → note NAT type and server connectivity.
• Xbox: Settings → General → Network settings → NAT type → run Test NAT type.

Quick fixes that worked for me:

• Power cycle the router (unplug 30 seconds), then the PC/console.
• Enable UPnP in your router. This auto-opens the necessary ports.
• Avoid VPNs and disable third-party firewalls while testing.
• Use a wired Ethernet connection. It stabilized our join times and reduced desync.

If NAT stays Strict/Blocked, port forward these (what finally solved it for my mixed PC/Xbox group):

• Xbox Live core:
  • TCP/UDP 3074
  • UDP 88, 500, 3544, 4500
  • TCP/UDP 53
  • TCP 80
• Steam (for Steam players/hosts):
  • UDP 27015-27030, 27036
  • TCP 27015-27030
  • UDP 4380

Only forward to the device hosting ground (PC or Xbox). If you have two routers (ISP modem + your router), put the ISP modem in bridge mode or the gaming router in DMZ on the ISP box to remove double NAT. After I bridged my ISP gateway and turned on UPnP, my NAT flipped to Open immediately.

PC-only Teredo tip: If Xbox Networking flags Teredo, ensure IP Helper service is running (Step 3), then in Windows Terminal (Admin) you can reset network components if needed. I fixed mine by toggling the adapter and restarting, but avoid drastic resets unless you’re comfortable restoring network settings.

Step 5 — Sync Date/Time and Region

I didn’t expect this to matter, but TLS handshakes can fail if your clock’s off. One friend’s PC was 7 minutes fast and could never join until we synced time.

PC: Settings → Time & Language → Date & time → enable Set time automatically and click Sync now.

Xbox: Settings → System → Time → set to automatic. Reboot after changing.

Step 6 — Firewall and App Clean-Up

On Windows, allow the apps through the firewall or the host might be unjoinable even with Open NAT.

• Open Windows Defender Firewall → Allow an app or feature → ensure Grounded 2, Xbox app, and Gaming Services are allowed on Private (and Public if you use it).
• Close bandwidth hogs: launchers updating other games, streaming apps, cloud backups.
• Temporarily disable overlays (Discord, GeForce Experience) if you see instant disconnects after joining.

Step 7 — Console-Specific Fixes

On Xbox, two tweaks saved our session when the PC folks were fine but the console couldn’t join:

• Clear alternate MAC: Settings → General → Network settings → Advanced settings → Alternate MAC address → Clear → restart console.
• Alternate port selection: Settings → General → Network settings → Advanced settings → Alternate port selection → choose another port and test NAT again.

If you changed privacy settings in Step 2, do a full power cycle: hold the Xbox power button for 10 seconds, unplug 30 seconds, then boot.

Hosting & Joining Best Practices (From Painful Trials)

• One host, best connection: Pick the player with Open NAT and wired Ethernet to host.
• Shared Worlds: If using a cloud/shared save, ensure the owner is online or has shared it properly. If not, invites may fail silently.
• Invite method: Use the in-game invite first; if flaky, try Xbox Game Bar on PC (Win + G → Social → Invite to game) or the Xbox Guide on console.
• Restart order: If something breaks mid-session, have only the host restart the game first. If that fails, then guests restart, then finally reboot router/PC/console.

Common Mistakes I Made (Skip These)

• Assuming versions match without checking the main menu build number.
• Leaving Cross-network play set to Block in Xbox privacy settings.
• Testing invites over Wi‑Fi on a congested 2.4 GHz network; 5 GHz or Ethernet is far better.
• Ignoring a Strict NAT warning—no amount of game restarts will overcome it.
• Running a VPN “just for voice” and forgetting it routes the game too.

Advanced Tips (If You Still Can’t Connect)

• Router QoS: Give your PC/Xbox “Highest” priority to smooth out spikes.
• DNS change (PC/Xbox): Switching to a reliable DNS (e.g., your ISP’s or well-known public resolvers) reduced our lobby timeouts. Reboot after changing.
• Isolate the problem: Have the host tether to a mobile hotspot just to test. If it works, your ISP/router is the bottleneck (often CGNAT or double NAT).
• One port-forward at a time: Start with 3074 and UPnP. Add others only if the NAT test still fails.

Fast Recap

• Match versions and branches on every platform.
• Enable crossplay and Allow multiplayer in Xbox privacy.
• Start Xbox/Gaming Services and verify Xbox Networking on Windows.
• Open NAT via UPnP or port forwarding (3074, 88, 500, 3544, 4500; Steam ports if needed).
• Sync date/time, allow apps through firewall, use wired where possible.

Follow this order and you should beat the “Network incompatible” wall like I did. Once everything’s green, joining is near-instant and stays stable. If you’ve run the full checklist and still can’t connect, it might be an ISP-side restriction—capture your NAT test results and open a ticket with the game’s support so they can check your session logs.