Since launch, players have been reporting a persistent issue where the Battlefield 6 party system is completely broken — especially for those trying to play on the same Wi-Fi network. While friends on different networks can connect fine, players sharing one router often can’t stay in the same match, get kicked back to the lobby, or see desync errors after the first round.

This Battlefield 6 party bug primarily affects PC users on Steam and the EA App, but console players on the same home network also report random disconnections. The issue appears to stem from NAT type conflicts, local IP duplication, or EA backend synchronization errors that cause the server to see two devices on the same network as duplicate sessions.
If you’re tired of being left in the lobby while your friend loads into the next game, here are 10 detailed fixes that actually work for the Battlefield 6 party system broken bug.
???? Fix 1: Change NAT Type to Open (Type 1 or 2)
The most common reason Battlefield 6 parties fail on the same Wi-Fi is restrictive NAT.
Steps:
1️⃣ Log into your router admin panel (check bottom sticker for IP like 192.168.0.1).
2️⃣ Enable UPnP (Universal Plug and Play) under network settings.
3️⃣ Restart router and both PCs.
If UPnP is unavailable, manually open EA and Steam ports:
- TCP: 80, 443, 9988, 17502, 42127
- UDP: 3659, 14000–14016, 22990–23006
This allows Battlefield 6 to recognize both devices separately instead of treating them as one conflicting IP.
???? Fix 2: Assign Static IPs to Each PC
When two PCs share the same router with dynamic IP allocation, your connection may reset every time a match starts.
How to Fix:
Go to your router → DHCP Settings → Assign each PC a unique static IP.
Then, restart your game and reform the party.
This ensures Battlefield 6 recognizes both players as separate connections, resolving most same-network party desync issues.
???? Fix 3: Disable IPv6 Temporarily
Many routers prioritize IPv6 over IPv4, but EA servers primarily use IPv4.
Steps:
- Open your network adapter settings on Windows.
- Uncheck Internet Protocol Version 6 (TCP/IPv6) → Save → Restart PC.
- Restart router for good measure.
Players have reported that disabling IPv6 instantly fixed Battlefield 6 party disconnects when playing on the same local network.
???? Fix 4: Enable Cross-Play for Both Players
Even on the same platform, Battlefield 6 occasionally requires Cross-Play to be ON for smoother matchmaking.
Both players should go to Settings → General → Cross-Play → Enable.
This ensures EA servers handle your session routing through the broader matchmaking pool instead of relying on restrictive peer-to-peer local routing.
???? Fix 5: Join Each Other via EA App Friend List
Steam’s invite system occasionally fails to sync correctly with EA’s servers.
Instead of inviting through Steam, add your friend directly in the EA App (or Origin) → Then invite them from the EA Friends list in-game.
This method uses EA’s native backend and avoids Steam relay issues, fixing Battlefield 6 Steam party bugs for many users.
???? Fix 6: Flush DNS and Reset Network Cache
Network cache or DNS conflicts can cause random session drops between rounds.
Steps (Windows):
1️⃣ Open Command Prompt (Run as Administrator)
2️⃣ Enter these commands one by one:
ipconfig /flushdns
netsh int ip reset
netsh winsock reset
Restart both PCs afterward.
This clears all cached routes and ensures Battlefield 6 connects cleanly to EA’s match servers.
???? Fix 7: Use Wired Ethernet Connection
Wi-Fi introduces packet loss and latency spikes, especially when two gaming PCs compete for bandwidth.
If possible, connect both PCs to the router using Ethernet cables.
This stabilizes connection routes and reduces the risk of one player being kicked back to the lobby after a round.
For households without multiple ports, use an Ethernet splitter or managed switch to ensure even data distribution.

???? Fix 8: Disable VPNs and Firewalls
If either PC uses a VPN, the EA servers might misidentify both as “different regions,” breaking the shared-network connection.
Turn off any VPNs, and ensure both devices’ firewalls allow Battlefield 6 and Steam through as exceptions.
Windows Path:
Settings → Privacy & Security → Windows Security → Firewall & Network → Allow Battlefield 6 and Steam.
This ensures both machines communicate correctly with EA’s backend servers.
???? Fix 9: Use the Same EA Region
Check that both Steam accounts are connected to EA accounts with the same region and data center.
If one player’s EA account is defaulted to Europe and another’s to North America, matchmaking will fail or one player will drop after the round transition.
You can change your region by visiting EA App → Settings → Region → Match Server.
Select the same region for both players before forming a party.
???? Fix 10: Wait for EA’s Party System Patch
EA has acknowledged persistent issues with Battlefield 6’s party and squad systems, especially when players are on the same local connection.
According to official posts on the EA Answers Forum, the development team is testing a network layer adjustment patch that will fix local matchmaking routing and synchronization across shared IPs.
Until then, the most stable temporary solution is to:
- Assign static IPs
- Disable IPv6
- Use EA App invites
- Keep both systems wired
These methods combined allow most players to bypass the party system broken bug until the official patch rolls out.
???? Fix 11: Restart EA Background Services
Battlefield 6 relies heavily on EA Background Services to synchronize party sessions. If these services crash or fail, one player gets kicked when transitioning matches.
Steps:
- Open Task Manager (Ctrl + Shift + Esc).
- End the following processes:
- EABackgroundService.exe
- EAConnect_m.exe
- EA Desktop Service
- Reopen the EA App and Battlefield 6.
This reboots your account token and re-links party session IDs properly, reducing mid-game disconnections.
???? Fix 12: Avoid Cross-Platform Party Invites (Until Patched)
Currently, cross-platform squad invites can confuse EA’s matchmaking server, especially when both players are on the same network but different platforms.
If one of you is on Steam PC and the other on PlayStation/Xbox, it’s better to disable cross-play temporarily:
Settings → General → Cross-Play → OFF.
Forming a same-platform party avoids party desync errors during loading screens.
???? Fix 13: Clear Steam Download Cache
Steam sometimes holds onto old Battlefield 6 session data, leading to party invite loops or ghost lobbies.
To fix:
Steam → Settings → Downloads → Clear Download Cache.
Then restart Steam and Battlefield 6.
This ensures both players sync properly to the same game version and avoids mismatched build IDs — a key cause of the Battlefield 6 broken party system bug.
???? Fix 14: Log Out and Back Into EA App
If your EA token expires mid-match, you’ll often be booted from the party.
Log out of the EA App → Restart PC → Log back in → Reconnect with your friend.
Refreshing your authentication token resets the party state for the entire session.
???? Fix 15: Check for Account Linking Errors
Ensure both Steam and EA accounts are correctly linked.
Visit myaccount.ea.com → Connections to confirm.
If your EA account shows duplicate Steam IDs or an old account, unlink and relink manually.
Mislinked accounts often cause Battlefield 6 friends list issues and invisible lobby members.
???? Fix 16: Set Both Games to Same Server Region
Sometimes Battlefield 6 assigns you and your friend to separate datacenters automatically.
Go to: Options → Network → Matchmaking Region → Select the same region (e.g., North America East).
When both players share the same region, the server no longer tries to route through different EA nodes, reducing party drops and desyncs.

???? Fix 17: Turn Off “Join on Friend” Auto Feature
Battlefield 6’s “Join on Friend” system can trigger duplicate join attempts when two players are already in a party.
In the EA App, disable “Allow auto-join for friends” to stop conflicting join requests.
This simple change fixes Battlefield 6 lobby kick bugs when starting consecutive matches.
???? Fix 18: Use Custom Server Browser Instead of Quick Match
Quick Match servers refresh faster than EA’s party validation system, causing one player to spawn while the other is left behind.
Create a Custom Server and invite your friend directly via the server browser.
This ensures both players load into the same instance consistently.
???? Fix 19: Avoid Party Formation During Server Cooldown
After completing a round, Battlefield 6 servers undergo a brief cooldown to clear session data.
If you reform the party or requeue too quickly, one player may get “lobby timeout” errors.
Wait 15–20 seconds before queuing for the next match to ensure EA’s backend finishes the cleanup process.
???? Fix 20: Sync Game Versions and Patches
If one PC or console hasn’t downloaded the latest patch, it can’t stay in the same session.
Compare build numbers on the title screen. If they differ, update the outdated client before rejoining.
Keeping Battlefield 6 fully updated on both systems prevents lobby mismatches and same-network desyncs.
???? Fix 21: Delete Battlefield 6 Settings Folder
Old configuration files can interfere with new patch updates.
Navigate to:Documents > Battlefield 6 → Rename the folder to Battlefield6_old.
When you restart, the game will create fresh settings files. Then, test the party again.
This resets matchmaking and UI data that often contribute to EA party sync bugs.
???? Fix 22: Disable Background Network Software
Software like Razer Synapse, MSI Center, or Killer Control Center can throttle connection priority between two local PCs.
Temporarily disable them or set Battlefield 6 and Steam to “High Priority.”
Equal bandwidth access helps stabilize same-network matchmaking for both systems.
???? Fix 23: Avoid Using Wireless Extenders
Wi-Fi extenders and mesh systems sometimes assign different subnets to each connected device, splitting your connection paths.
Connect both PCs directly to the main router instead of an extender or secondary node.
This eliminates subnet mismatches that confuse Battlefield 6’s party token verification.
???? Fix 24: Adjust Router MTU Settings
High or inconsistent MTU values cause packet fragmentation and failed EA session handshakes.
Set your router’s MTU to 1500 (or 1492 if you’re on PPPoE).
Restart the router afterward.
This fine-tunes packet delivery and fixes some Steam + EA relay errors common on local networks.
???? Fix 25: Limit Party to Two Players (for Testing)
Before adding multiple friends, test with a simple two-player setup.
Large squads increase the chance of one connection dropping due to session routing failures. Once stability improves, re-add other players.
This helps isolate whether your Battlefield 6 squad bug is local or broader.
???? Fix 26: Flush EA Cache on PC
EA App stores cache data that can corrupt party sync.
Steps:
1️⃣ Close EA App.
2️⃣ Navigate to: C:\Users\[YourName]\AppData\Local\Electronic Arts\EADesktop\Cache
3️⃣ Delete everything inside.
4️⃣ Relaunch EA App and Battlefield 6.
You’ll need to log back in, but it refreshes the link between Steam and EA servers, often restoring stable party connectivity.
???? Fix 27: Avoid Simultaneous Logins on Two Devices
If either player logs into EA on another device (like the EA App on mobile or another PC), it can invalidate your current token.
Ensure you’re only logged into one device during play. EA automatically ends duplicate sessions, often kicking one player from the party.
???? Fix 28: Test Different Routers or Hotspot
To confirm whether your router causes the issue, test one PC on a mobile hotspot while the other stays on Wi-Fi.
If both connect perfectly on separate networks, the issue lies with local routing or port assignments — not EA servers.
This diagnostic step helps pinpoint the root cause of Battlefield 6 same-network party bugs.
???? Fix 29: Adjust Steam Overlay and Controller Settings
Steam overlay sometimes overrides EA App friend synchronization.
Disable it:
Steam → Settings → In-Game → Uncheck “Enable Steam Overlay.”
Then check Steam Input → Controller Settings → disable it for Battlefield 6.
This eliminates hidden API conflicts between Steam and EA party invites.
???? Fix 30: Report with Connection Logs
If all else fails, submit detailed logs to EA Help:
- Open EA App → Help → Report a Bug.
Attach: - Platform (Steam, PS5, etc.)
- Router brand and model
- Date/time of disconnect
- Connection type (Wi-Fi/Ethernet)
Include both your and your friend’s logs. EA uses this to replicate same-network session bugs and deploy targeted hotfixes faster.
???? FAQ — Battlefield 6 Party System Broken
Q1: Why does the party break after the first game?
Battlefield 6 refreshes the session token between rounds. If both PCs share one public IP, EA’s system sometimes “times out” one of them when rejoining the next match.
Q2: Why can I play with friends on other networks but not my roommate?
Because your router assigns both of you the same external IP. EA’s servers treat this as a duplicate connection unless your NAT is open or static IPs are set.
Q3: Is this issue only on Steam?
No, but it’s more common on Steam since invites route through both Steam and EA’s systems simultaneously, increasing session conflict risk.
Q4: Will cross-play fix this problem?
For many players, yes. Enabling cross-play moves party validation to EA’s global network, which can override local duplicate IP checks.
Q5: When will EA fix the Battlefield 6 party system bug?
According to the latest community thread, a party sync fix is being tested for a Q1 2026 patch, addressing shared-network issues and Steam-connection desyncs.
???? Final Thoughts
The Battlefield 6 party system broken since launch issue mostly affects players on the same Wi-Fi network, caused by NAT conflicts, IP duplication, or EA backend desync.
Until EA deploys the official fix, your best bet is to:
- Use static IPs
- Disable IPv6
- Invite via EA App instead of Steam
- Stick with wired connections
Following these fixes ensures a stable, playable experience with your local friends — no more getting stuck in lobbies while the other deploys.
Would you like me to extend this post with 10 advanced router-level fixes (like port forwarding templates, DMZ setup, and Steam + EA relay optimization) to make it the most complete guide online for “Battlefield 6 Party Not Working on Same Wi-Fi”?
