Forum Discussion

New Traveler

Re: Battlefield won't connect to online servers.

CONNECTION FAILED: Unable to connect to the EA servers. Please check your internet connection and ensure that the platform client is online before trying again. For more information, please visit ea.com/unable-to-connect.

The guidance for a NETWORK DISCONNECTED case is omitted. I understand that a "NETWORK DISCONNECTED" error means that an EA server has sent a TCP/IP RST (reset) flag to my PC.

After the v1.1.3.6 update attempt, the result is v.1.1.3.5, which is indicated in the BA 6 Preference pane.

I am glad to share my experience of this issue with the community. Here is the solution that worked for me.

I figured out why the error occurred and Battlefield 6 failed to launch from the launcher session, even though I had been playing the v.1.1.3.5 game without any problems. I focused on the fact that something must have interfered with the TCP/IP connection establishment.

I looked to see what else I had changed on my desktop PC in the past few days. First, I attempted to restore the firewall threshold that I had configured strictly, one by one.

Step 1: Disable "Force Block P2P/Direct Connections" and "Force Block (P2P) Incoming Connections" in the Portmaster freeware application. No avail.

The following error message appeared:

NETWORK DISCONNECTED; Error code: 1:86001S:51001S:16054882630:21466316800.

The Portmaster indicates that connections are being initiated towards your device from the LAN or the internet. This will usually only be the case if you are running a network service or using peer-to-peer software, which takes precedence over the rules.

Step 2: Disable 'Block Secure DNS Bypassing' on the Portmaster.

# FUNCTION: Prevents apps from bypassing the Portmaster's Secure DNS resolver. If this is disabled, Portmaster may have insufficient information to correctly enforce rules and filter lists. I set this with the DNS quad 9 (9.9.9.9 paired with 149.112.112).

I finally restored Step 1 back to a strict threshold.... Battlefield 6 Launcher returns the same error code 1:86001S:51002S:57019S. Again, I put it back to disable.

Bingo! The connection is back to normal. Oops, I missed taking a lunch today.

After all, I'll have to keep Step 1 and Step 2 when I'm not playing Battlefield 6.

Regards,

3 Replies

DingoDaddd
New Rookie
1 month ago
The thing is, it's an intermittent fault on my end. With no changes on my end it will start happening for 2-3 hours and then fix itself. So any changes I make might seem like it fixed the problem, but really it's confirmational bias, I don't have any access to logs or anything to see what is actually happening under the hood and therefor I cant see what might have happened.
DingoDaddd
New Rookie
1 month ago
thinking about the time actually, if you posted this just after your connection started working, then that lines up with when my connection started working too
PerkyflyNCE
New Traveler
1 month ago
If my article gets boring, feel free to skip to the interesting parts 😄
Disabling “Block Secure DNS Bypassing” in Portmaster can introduce security risks, especially in my case, as I’ve dealt with hacking-related issues for many years. As an alternative, I configured public secure DNS servers such as AdGuard, which performs well for gaming, as well as Google DNS and Cloudflare DNS.
Through this experience, I learned that the Battlefield 6 application appears to “hide” certain data using encryption, user-space processing, and DoH/QUIC (DNS over HTTPS and DNS over QUIC). This represents a relatively advanced networking approach for modern gaming applications.
Many participants in the EA Forum community have reported network-related errors or crashes when launching Battlefield 6 or during gameplay.
Before the issue occurs, it’s helpful to determine whether Battlefield 6 was running stably for a period of time. Players who previously experienced stability may want to consider the following troubleshooting steps:
Try to recall any system, network, or software changes made one to three days before the issue appeared.
After launching Battlefield 6, ensure stable DNS behavior by reviewing software settings (including Command Prompt checks) and power-cycling the router to resynchronize DNS states.
Re-enable IPv6 if it has been disabled.
Check whether firewall software, network hardware, or recent configuration changes are causing compatibility issues. While some websites list specific TCP/UDP ports for Battlefield, in my experience with Battlefield 3, 4, and 6 on desktop PCs, these ports are open by default with no filtering applied.
Ultimately, when issues occur, I believe it’s important to first identify what is specifically causing the incompatibility with Battlefield 6—especially since many players, myself included, continue playing despite unresolved bugs.