"Connection Failed" With Error Code 1:86001S:51002S:57019S

Hello. I merged your message with the already existing thread for this issue. Please see the accepted solution for assistance. If that doesn't help, try disabling IPv6. That also has helped others resolve this. Thanks!

I keep getting error code 1:86001S:66003S:4688822970:0B and from what people said it's an authentication issue with players on steam and them having a usb plugged in and removing a usb fixes the problem. Unfortunately, a lot of us dont have that luxury since we have USBs plugged in that are absolutely necessary to use our computers, like keyboards and mice. Plus I dont even have any USBs with files plugged in and I still get this error. It just boots me from games I'm actually enjoying and it's really annoying. 

I've NEVER had an authentication error happen from my side. This is always on the side of the company and needs to be addressed immediately. This is immersion breaking and should never be happening to ANYONE.

Wow, just got a random notification from the buggy EA Forums about this - what a surprise that it's still hasn't been fixed 😂
After waiting years for EA to fix the exact same issue that was plaguing BF1 and BF2042, as soon as I started getting that error I knew what I had to do - got my money back and never looked back. And as someone that has worked both in Game dev and software development for decades I can tell you the issue is 100% on their end and they could fix it within a week if they wanted to. But they don't.
Their management is letting all their hard work go down the drain and you are going to see the same thing happen and there will be 20 people in their servers, to the point that you'll be waiting for a game to start for an hour. Good luck y'all! If you managed to get your money back - great! If not - write a salty review and move on...🤷‍♂️

You can also try disabling IPv6. That has been another solution for others with this issue.

having the same issue and done as the mod requested. can not even play the game... because of it..

did you get it fixed? 

EA_Vendcera​ 

Long post, but I've been troubleshooting this for the past 48 hours. Full disclosure I did use ChatGPT pro to help me keep track of what I had done. I utilized Microsoft Event Viewer, Windows Logs, and Hardware Monitoring software. I genuinely spent 48 hours working on this, please take the time to read through. I did include a part at the bottom for players; a TL;DR.

THIS IS NO LONGER WORKING. IT WORKED FOR 2 MATCHES AND CRASHES UPON CONNECTION TO ANOTHER MATCH. IT NO LONGER ALLOWS ME TO CONNECT TO A MATCH. EA FIX YOUR JAVELIN ANTICHEAT CLIENT

Root Cause Analysis – Battlefield 6 Network Disconnect During Gauntlet / RedSec Match Entry

Status: Issue reproduced across multiple devices and networks. Workaround identified (disable IPv6 on game client). Underlying defect still present.

Problem Description:

On multiple Windows 11 PCs in the same household, Battlefield 6 consistently caused a full network disconnect specifically when entering Gauntlet / RedSec (during helicopter insertion). Menus and normal multiplayer modes worked normally, but during Gauntlet load the PC would lose connectivity, Windows would report Connected – No Internet, DHCP lease renewal failed, DNS lookups failed, and the network only recovered after disabling and re-enabling the adapter or rebooting. Physical link never dropped.

This occurred on Ethernet and Wi-Fi, across two different Comcast gateways (XB8 and XB10), and on two separate PCs. No other applications or games were affected.

Troubleshooting Performed:

Clean Windows 11 reinstall performed. Latest chipset, NIC, and GPU drivers installed. Issue reproduced on a clean OS with no third-party utilities, overlays, tuning tools, or background services installed.

NIC settings tested at default and with conservative configurations. Same result.

Tested Ethernet and Wi-Fi independently. Same behavior.

Tested across two XB-series gateways. Same behavior.

Tested on mobile hotspot and Xfinity public Wi-Fi. Same behavior.

Tested on second PC in same environment. Same behavior.

This ruled out hardware faults, NIC firmware, router or gateway firmware, ISP routing, local DNS configuration, or operating system configuration.

Event Viewer Observations:

At the instant Gauntlet match entry begins, the following sequence consistently occurs:

DNS Client Event 1014 (name resolution timeout)

DHCP Client Event 1003 with error 0x79 (lease renewal failure)

Network transitions to No Network Access

EA Anti-Cheat / Javelin filter unload recorded

These appear to be downstream effects of a networking stack failure rather than primary causes. The adapter link remains up, but the routing layer collapses.

Network Path Findings:

Per EA request, traceroute, ipconfig, and route print output were captured on both home network and alternate network connections. Battlefield 6 traffic consistently routed to EA infrastructure in London / EU via Telia / twelve99 backbone and AWS / Akamai edge nodes. Routing paths were clean and stable. No packet loss or congestion signatures were present. The disconnect only occurred during protected Gauntlet session transition when anti-cheat filters attach.

Breakthrough Finding:

Disabling IPv6 on the game client network adapter immediately resolved the issue.

Adapter properties opened, Internet Protocol Version 6 unchecked, system rebooted.

After disabling IPv6:

Gauntlet and RedSec load normally

No DHCP failures

No DNS timeout events

No network disconnect

No anti-cheat filter unload events

Multiple matches played successfully

Same behavior confirmed on two separate PCs.

Conclusion – Likely Root Cause:

Issue appears to be caused by an IPv6-specific Battlefield 6 / Javelin Anti-Cheat Windows Filtering Platform (WFP) filter failure during Gauntlet / RedSec protected session hand-off.

During Gauntlet entry, BF6 prefers IPv6 transport. Javelin attaches IPv6 WFP security filters. Under certain routing or region assignment conditions, the IPv6 filter path triggers a networking stack failure, resulting in DHCP renewal failure, DNS resolution errors, and complete loss of gateway routing until adapter reset.

Disabling IPv6 forces IPv4 transport, which fully avoids the faulty path and restores stability.

Factors Confirmed Not Related:

Not caused by hardware, router firmware, Comcast routing, IPv6 at the network level, DNS provider, Windows configuration, driver versions, or local security software.

Issue is isolated to:

Battlefield 6

Multiplayer / Gauntlet / RedSec mode

IPv6 transport path

EA Anti-Cheat / Javelin filter behavior

Current Workaround:

Disable IPv6 only on affected PC network adapter. Do not disable IPv6 across entire network infrastructure.

Recommendation for EA Engineering Teams:

Areas suggested for investigation:

IPv6 WFP filter handling in Javelin Anti-Cheat

IPv6 session protection during Gauntlet transition

IPv6 to IPv4 fallback logic

Blaze IPv6 routing and region assignment interaction

Behavior across AWS / Akamai EU points of presence

Available diagnostic artifacts:

Traceroute logs across two network environments

Crash-time Windows networking logs

NIC driver and OS build data

Cross-system and cross-network reproduction notes

Willing to provide directly to engineering if needed.

I have reached out to customer service several times with no resolution to this issue and have not received any feedback or replies to my inquiries through the web support request. Here are my issues:

Error Code: 1:86001S:89001S:9C:-13561655840 An undefined error

Battlefield 6 worked on my home Xbox for multiplayer for my son for a couple of weeks. Then, an update made the game unusable due to an undefined error. We have been dealing with this since that first update.

To resolve the issue, we purchased him his own license for the game, but the same errors occurred.

We tried setting a MAC address for the Xbox, as instructed by EA and Microsoft, but the same errors happened.

We wiped all accounts and games from the Xbox, set it up as my home Xbox again, and reinstalled the game under his user, but we still receive the same errors.

Lastly, we factory reset the Xbox and set it up with my son’s account as primary, but we continue to receive the same error code.

I have been working on this issue for months with no resolution.

We have ensured that both the EA account settings for him as a minor should permit the game to play. The online support chat has done nothing aside from telling us to uninstall and reinstall again. I am trying to work a resolution and get something for putting as much time as I have been for this issue. I am going on about 20 hours of effort on my behalf over the past 3 months. Please help!

Can't connect to the game, everytime I get past the queue, I get this error message

Error Code1:86001s:227069s:20002U

Hi there. Do you have UPnP enabled? I saw someone else reporting that helping.