Getting endless Lost Connection to Session errors everytime

Repeat.. et al, This is hitting me now.. this morning i am getting the UDP3659 Port issue.. Can't connect, been doing everything Repeat has been. No luck. I can you the server is up and you bastards are playing.. LET ME IN.. LOL. I don't change anything on this machine.. it does one thing and I don't mess with it.. cleared cache, Renew/rejerked/replaed with config. I am running on Starlink service.. what are you on Repeat?

Land cable. This really sucks. Really look forward to every evening and having my talented buds killing me and having a chat. Hope you have better luck than I have had Gomer.
🍻
 
  • Like
Reactions: Animalllllll
Created a rule to open the port. No luck.

Getting old and just want to hang out with the guys. This is very depressing.

Hope you all are having a good time. Miss ya.
This really sucks bud.

The one thing I haven't seen is changing your DNS.

Id give 1.1.1.1 and then 8.8.8.8 a try and see if that routes the traffic/packets in a way that doesn't cause a hangup.

If that doesnt work you can do a node hop test from your IP to our bf4 server IP and see if or where there might be a problem. I had to do this in the past. Give me a few so I can look up the program I used to do the testing. For me in NY there are about 7 different node hops where one specific one was causing a packet issue.

At the time a new router fixed it for me. And then I moved to full fiber and never had an issue again. I feel your pain as I was going nuts for months about it.
 
BTW what is the difference between an American and a computer?

Americans have no trouble shooting!!!!

Frustrated Cut It Out GIF
minions GIF
 
This really sucks bud.

The one thing I haven't seen is changing your DNS.

Id give 1.1.1.1 and then 8.8.8.8 a try and see if that routes the traffic/packets in a way that doesn't cause a hangup.

If that doesnt work you can do a node hop test from your IP to our bf4 server IP and see if or where there might be a problem. I had to do this in the past. Give me a few so I can look up the program I used to do the testing. For me in NY there are about 7 different node hops where one specific one was causing a packet issue.

At the time a new router fixed it for me. And then I moved to full fiber and never had an issue again. I feel your pain as I was going nuts for months about it.

Up for anything. Will give it a go.
 
have you tried these yet? You probably did lol.
I saw someone post this somewhere on reddit lol,
Quote: If none of those things work for you, I spent a long ass time scrubbing steam forums for a solution and someone said if you load into a testing range and shoot down at least one target and leave, it should work when you load into a server. I tried it and this is the only thing that worked. I know this is years old but this is the Reddit post that comes up when you google it so hopefully it helps someone out there
 
Here's what chatgpt has to say about this.

That BF4 error is annoyingly common—and it’s usually network/ports/NAT, not the game itself. Let’s go straight to the stuff that actually fixes it.


What the error really means​

BF4 uses UDP port 3659 for game traffic. If that port is blocked, misrouted, or already in use, the server drops you instantly.


Step-by-step fixes (in order)​

1. Restart the boring stuff (but it matters)​

  • Restart modem + router (unplug for 30 seconds)
  • Restart your PC
    This clears stuck UDP sessions. Surprisingly high success rate.

2. Make sure your firewall isn’t killing it​

Windows Defender Firewall

  1. Open Windows Defender Firewall
  2. Click Allow an app or feature
  3. Make sure Battlefield 4 and Origin/EA App are allowed on Private and Public
  4. If unsure → temporarily disable firewall and test
If it works with firewall off → add rules and turn it back on.


3. Port forward UDP 3659 (this fixes most cases)​

Log into your router and forward these UDP ports to your PC’s local IP:

UDP: 3659<br>UDP: 14000–14016<br>UDP: 22990–23006<br>
If your router supports UPnP, turn it ON instead (don’t do both at the same time).


4. Check NAT type (huge for BF4)​

If your NAT is Strict or Symmetric, BF4 servers will kick you.

Quick check:

  • If you’re behind carrier-grade NAT (common with some ISPs), port forwarding won’t work at all
  • Try connecting your PC directly to the modem (bypass router) as a test
If it works directly → router config is the issue.


5. Kill background apps that hijack UDP​

Close or uninstall temporarily:

  • VPNs (very common cause)
  • Hamachi
  • NetLimiter
  • Killer Network software
  • Any “gaming booster” nonsense
Then test again.


6. Repair the game files​

In EA App / Origin:

  • Library → Battlefield 4 → Repair
    Corrupt network files can trigger instant disconnects.

7. IPv6 can break BF4 (yep, really)​

Disable IPv6 on your PC:

  1. Network Settings → Change adapter options
  2. Right-click active connection → Properties
  3. Uncheck Internet Protocol Version 6 (IPv6)
  4. Reboot
This one fixes a shocking number of BF4 kicks.


Quick reality check​

If:

  • Other online games work
  • BF4 kicks instantly
  • Port forwarding doesn’t help
Then you’re almost certainly behind ISP NAT, and the only real fixes are:

  • Ask ISP for a public IPv4
  • Use a router with proper UPnP
  • Or (last resort) use a gaming-friendly VPN that supports UDP properly
 
  • Like
Reactions: repeat0ffender
have you tried these yet? You probably did lol.
I saw someone post this somewhere on reddit lol,
Quote: If none of those things work for you, I spent a long ass time scrubbing steam forums for a solution and someone said if you load into a testing range and shoot down at least one target and leave, it should work when you load into a server. I tried it and this is the only thing that worked. I know this is years old but this is the Reddit post that comes up when you google it so hopefully it helps someone out there

😆


I have tried this several times.
 
Here's what chatgpt has to say about this.

That BF4 error is annoyingly common—and it’s usually network/ports/NAT, not the game itself. Let’s go straight to the stuff that actually fixes it.


What the error really means​

BF4 uses UDP port 3659 for game traffic. If that port is blocked, misrouted, or already in use, the server drops you instantly.


Step-by-step fixes (in order)​

1. Restart the boring stuff (but it matters)​

  • Restart modem + router (unplug for 30 seconds)
  • Restart your PC
    This clears stuck UDP sessions. Surprisingly high success rate.

2. Make sure your firewall isn’t killing it​

Windows Defender Firewall

  1. Open Windows Defender Firewall
  2. Click Allow an app or feature
  3. Make sure Battlefield 4 and Origin/EA App are allowed on Private and Public
  4. If unsure → temporarily disable firewall and test
If it works with firewall off → add rules and turn it back on.


3. Port forward UDP 3659 (this fixes most cases)​

Log into your router and forward these UDP ports to your PC’s local IP:

UDP: 3659<br>UDP: 14000–14016<br>UDP: 22990–23006<br>
If your router supports UPnP, turn it ON instead (don’t do both at the same time).


4. Check NAT type (huge for BF4)​

If your NAT is Strict or Symmetric, BF4 servers will kick you.

Quick check:

  • If you’re behind carrier-grade NAT (common with some ISPs), port forwarding won’t work at all
  • Try connecting your PC directly to the modem (bypass router) as a test
If it works directly → router config is the issue.


5. Kill background apps that hijack UDP​

Close or uninstall temporarily:

  • VPNs (very common cause)
  • Hamachi
  • NetLimiter
  • Killer Network software
  • Any “gaming booster” nonsense
Then test again.


6. Repair the game files​

In EA App / Origin:

  • Library → Battlefield 4 → Repair
    Corrupt network files can trigger instant disconnects.

7. IPv6 can break BF4 (yep, really)​

Disable IPv6 on your PC:

  1. Network Settings → Change adapter options
  2. Right-click active connection → Properties
  3. Uncheck Internet Protocol Version 6 (IPv6)
  4. Reboot
This one fixes a shocking number of BF4 kicks.


Quick reality check​

If:

  • Other online games work
  • BF4 kicks instantly
  • Port forwarding doesn’t help
Then you’re almost certainly behind ISP NAT, and the only real fixes are:

  • Ask ISP for a public IPv4
  • Use a router with proper UPnP
  • Or (last resort) use a gaming-friendly VPN that supports UDP properly

Thanks for taking the time. Have done most of these but some I have not. Will try the others.
 
  • Like
Reactions: zRaidenn-__
If you have a second computer, try running bf4 on that one to see if the problem is on the connection side or the computer side.

Any time I had udp 3659 errors, it was when i was tethering off a cell phone. Changing to a different connection always fixed it.
 
Last edited:
Another data point, tethering to my phone generates the same banned message that connecting to a VPN does at RC1.

I can still connect to some servers that do not have the same entry regulations as our BF4 servers.

Going to walk through post #67 items and see what happens.

edit: went through the items in post #67 and still have the same issue with our servers.
 
Last edited:
  • Sad
Reactions: Dan_
Have you done these?

install pb from inside the game folder then try the game View attachment 9523 ALSO RESTART
You run pbsvc.exe which is in your Battlefield 4 install folder. For me it's under C:\Program Files (x86)\Steam\steamapps\common\Battlefield 4\__Installer\punkbuster\redist


have you try
Full Network Reset (CMD):
Open Command Prompt as Administrator and run these in order, then reboot:
  • ipconfig /flushdns
  • ipconfig /release
  • ipconfig /renew
  • netsh winsock reset


Here's what chatgpt has to say about this.

That BF4 error is annoyingly common—and it’s usually network/ports/NAT, not the game itself. Let’s go straight to the stuff that actually fixes it.


What the error really means​

BF4 uses UDP port 3659 for game traffic. If that port is blocked, misrouted, or already in use, the server drops you instantly.


Step-by-step fixes (in order)​

1. Restart the boring stuff (but it matters)​

  • Restart modem + router (unplug for 30 seconds)
  • Restart your PC
    This clears stuck UDP sessions. Surprisingly high success rate.

2. Make sure your firewall isn’t killing it​

Windows Defender Firewall

  1. Open Windows Defender Firewall
  2. Click Allow an app or feature
  3. Make sure Battlefield 4 and Origin/EA App are allowed on Private and Public
  4. If unsure → temporarily disable firewall and test
If it works with firewall off → add rules and turn it back on.


3. Port forward UDP 3659 (this fixes most cases)​

Log into your router and forward these UDP ports to your PC’s local IP:

UDP: 3659<br>UDP: 14000–14016<br>UDP: 22990–23006<br>
If your router supports UPnP, turn it ON instead (don’t do both at the same time).


4. Check NAT type (huge for BF4)​

If your NAT is Strict or Symmetric, BF4 servers will kick you.

Quick check:

  • If you’re behind carrier-grade NAT (common with some ISPs), port forwarding won’t work at all
  • Try connecting your PC directly to the modem (bypass router) as a test
If it works directly → router config is the issue.


5. Kill background apps that hijack UDP​

Close or uninstall temporarily:

  • VPNs (very common cause)
  • Hamachi
  • NetLimiter
  • Killer Network software
  • Any “gaming booster” nonsense
Then test again.


6. Repair the game files​

In EA App / Origin:

  • Library → Battlefield 4 → Repair
    Corrupt network files can trigger instant disconnects.

7. IPv6 can break BF4 (yep, really)​

Disable IPv6 on your PC:

  1. Network Settings → Change adapter options
  2. Right-click active connection → Properties
  3. Uncheck Internet Protocol Version 6 (IPv6)
  4. Reboot
This one fixes a shocking number of BF4 kicks.


Quick reality check​

If:

  • Other online games work
  • BF4 kicks instantly
  • Port forwarding doesn’t help
Then you’re almost certainly behind ISP NAT, and the only real fixes are:

  • Ask ISP for a public IPv4
  • Use a router with proper UPnP
  • Or (last resort) use a gaming-friendly VPN that supports UDP properly
All of this.
 
  • Like
Reactions: 8bAd8