Forum Discussion

Anonymous's avatar
Anonymous
12 years ago

Game disconnected: client closed down connection. DURING GAME.

While playing somewhere between 10-20 minutes on a server, Everything on the server suddenly freezes for 10 seconds, followed by the saving black screen, and closing the client.

IF YOU CAN READ PROPERLY; THIS MEANS I AM ABLE TO JOIN SERVERS. NOT ABLE TO JOINING ISSUES ARE NOT RELEVANT ON THIS THREAD. Yes, you too EA. Ignore page 2-6.

 

Pretty much confirmed by now: it's a server issue. (crash). Fix please! :D

 

Followed by a error message on battlelog: 

Game disconnected: client closed down connection.
 
This is very frustrating, as I can't play any game lasting longer then 30 minutes without losing all my progress.
 
I did not have this issue during the beta.
 
System:
OS: Windows 7 x64
CPU: i7 3770K 
GPU: Radeon HD 7970
RAM: 8GB
Internet connection: 60 MB/s
 
''Fixes'' I've tried:
- Update Punkbuster
- Opening ports
- Google
Spoiler

1.open CMD
2.type ipconfig /flushdns confirm
3.type ipconfig /registerdns confirm
4.type ipconfig /release confirm
5.type ipconfig /renew confirm
6.type netsh winsoc reset confirm
7.restart ur computer

And didn't work

 

------------------

Adding stuff that I tried and failed:

1) Editing host file in windows/system32/drivers/, removing 127.0.0.1

2) Disabling NVIDIA Shadowplay

3) Uninstalling GeForce Experience

4) Manually re-adding PunkBuster to ProgramFiles/OriginGames/BF4/PB/ and re-running PBSetup

5) Playing the 32-bit version (gives me Invalid License, Code = Missing DLL [MSVCP110.dll] Error: 0x7E)

6) Running PunkBuster Service Test

 7) Removing ™ in the Regedit (Windows Registry Editor)

8) In Audio > Advanced, removing selection from "Allow applications to take exclusive control of this device" and "Give exclusive mode applications priority"
9) Removing NVIDIA Audio Driver

10) Trying "Repair Installation", but didn't work

11) Tried to connect through other ISP (distinct physical connection)

I still cant join servers with more than 5 players

------------------

On router:

-UPnP: Enabled

-Port Forwarding (Both TCP and UDP): 53, 3074, 3659, 9988, 14000:14016, 17502, 20000:20100, 22990:23006, 25200:25300, 42127

-Firewall: Disabled

On Windows:

-Firewall: Disabled

-Services: "SSDP Discovery" on AUTO (and running)

-Punkbuster: Updated to the latest version

Tried already:

-Reboot (PC, Router, Modem, Origin...)

 
None of those worked though. Hope someone is able to help me.

109 Replies

  • Anonymous's avatar
    Anonymous
    12 years ago

    Nearly two weeks after go live and I still have this problem. Is there a fix on it's way?

  • Anonymous's avatar
    Anonymous
    12 years ago

    Three weeks after launch and I still have this issue on a daily basis.

    I've contacted the EA Support since from very first day and had no success at all. As they said to me twice: my case (problem) has been escalated to a "specialist team".

    Through help.ea.com Case #10333236, I've posted over 20 (attempts of) fix and tests. They did answer me yesterday:

    Spoiler
    This email is to inform you that your case has been escalated to our specialist team. After reviewing the UO Trace you have provided, it is determine that the disconnection you are experiencing is due to your home network not being able to connected to the EA servers. If you are running on a wireless connection please try a direct connection using ethernet cable or try by passing the router and connecting straight to the modem. Also, contact your internet service provider and make sure you have the proper ports opened.

    You should enable the following online ports on your connection:
    TCP: 80, 443, 9988, 20000-20100, 22990, 17502, 42127
    UDP: 3659, 14000-14016, 22990-23006, 25200-25300

    I do apologize for the inconvenience and thank you for being patient. If there is anything else that we could help you with please do not hesitate to contact us again or you can simply visit http://help.ea.com.

    Note that I reported over the several feedbacks I posted in this case, that...

    1) I've tested with different ISP (distinct physical connections/cables/networks), including no routers in the way, plugging the PC directly to the modems.

    2) BF3 and BF4 Beta NEVER had this problem (BF3 still connects flawlessly). They NEVER had problem to "connect to the EA Servers".

    3) I've tested ALWAYS with Ethernet Cable, and not with Wireless Connection

    4) I've opened/forwarded all the ports

    Not only they did not read my feedbacks, but they've closed the damn case and I can't send anymore messages/feedback. It's useless.

    Now I understand why the Battlefield Forums over Battlelog forwards people to this one: PEOPLE GOTTA BE THE HEROES.

    It's basically EA saying: "It's your **bleep**ing problem. Deal with it"

    I'm quoting below the compilation of fixes that I've tried before. For some, they work. It didn't work for me.

    Spoiler

    Server Update #7 rolled out (06/Oct/13), but I still get Client Closed Down Connection (CCDC).

    For those who didn't see my post at page 7:

    I've done further testing and I'm going to rewrite my log to be in a more organized reading so other people can try exactly what I did.

    I know the OP talks about the error (Client Closed Connection) DURING the game, but I didn't see any other topic with the same level of feedback than this one, so please, don't get mad.

    Let's go:

    MY PROBLEM #1: After I launch the game and browsing servers in Battlelog, I try to Join a Server and a few seconds after the "Connecting" message, it gives me the error "Game disconnected: client closed down connection"

    MY PROBLEM #2: (that might be related) When I succesfully join a server, after a few minutes (5 to 15 minutes), I get black screen with blinking loading "dot" and the game closes. Then it shows me the error "Disconnected from EA⚽".

    FACT #1: I usually get to connect to servers with very few people (0 to ~5). The probability of joining seems to be higher when the round didn't start yet.

    FACT #2: There are some servers that I have a higher probability of joining, even it's 15 players already. I don't know the reason, but seems to be a server-side problem (maybe specific to some hoster companies, as I've seen some servers have Join Queue and some don't).

    FACT #3: I don't have any problem with BF3 (still installed and running)

    FACT #4: I didn't have this problem with BF4 Beta 

    FACT #5: BF4 Singleplayer works without any problem (just to point out that Singleplayer's Achievment and stuff needs to be authenticated online and sync'ed and I didn't have any problems with that)

    FACT #6: I've had other crashing problems (like CTD when the Shangai building falls), but don't seem to be related to this one.

    FACT #7: I've contacted EA through the Support Chat and they forwarded my case to a higher level team. No response, so far.

    FACT #8: On 30 Oct 2013, there was an ~600MB update, but the problem persisted.

    FACT #9: I did the tracerout/ping, with the tool EA provided UOTrace, to EASO.EA.COM and MASTER.GAMESPY.COM, but all seems to be fine. Test done with 100+ packets, trace was ok, and no significant packet loss.

    I list below the fix suggestions that I've tried and did not work for me (but for some people worked, so go ahead and try them):

    • FIX #1: Ensuring that every network equipment (router, modem, load balance, etc) have UPnP Enabled and Firewall Disabled

    • FIX #2: Ensuring these ports are forwarded on your network equipment: 
      Port Forwarding (Both TCP and UDP): 53, 3074, 3659, 9988, 14000:14016, 17502, 20000:20100, 22990:23006,
      25200:25300, 42127 

    • FIX #3: Disabling Windows Firewall completly

    • FIX #4: Ensuring that Windows Service "SSDP Discovery" is running and is set to "AUTO"

    • FIX #5: Ensuring that PunkBuster is updated to the latest version

    • FIX #6: Editing the "host" file in windows/system32/drivers/, and removing the lines containing "127.0.0.1"

    • FIX #7: Disabling NVIDIA Shadowplay

    • FIX #8: Uninstalling GeForce Experience 

    • FIX #9: Manually re-adding PunkBuster to ProgramFiles/OriginGames/BF4/PB/ and re-running PBSetup

    • FIX #10: Playing the 32-bit version (gives me Invalid License, Code = Missing DLL Error: 0x7E) 

    • FIX #11: Running PunkBuster Service Test to ensure it's working

    • FIX #12: Removing the symbol "™" from BF4 in Regedit (Windows Registry Editor) 

    • FIX #13: In Sound/Playback Devices > (your default Audio Device) > Properties > Advanced, unticking "Allow applications to take exclusive control of this device" and "Give exclusive mode applications priority" 

    • FIX #14: Removing NVIDIA Audio Driver

    • FIX #15: Repairing BF4 Installation in Origin

    • FIX #16: Renewing IPCONFIG
      1.open CMD 
      2.type ipconfig /flushdns confirm 
      3.type ipconfig /registerdns confirm 
      4.type ipconfig /release confirm 
      5.type ipconfig /renew confirm 
      6.type netsh winsoc reset confirm 
      7.restart ur computer 

    • FIX #17: Using Google DNS (8.8.8.8)

    • FIX #18: Connecting with a totally different ISP (distinct physical connection)

    • FIX #19: Reinstalling Google Chrome's Battlelog Plugin

    • FIX #20: Installing / Reinstalling Microsoft .NET 4.0 and 4.5 Frameworks

    If anyone got a suggestion or a fix that worked for you, please comment below!

     

    If the OP prefers, I can open another thread, as long he is willing to link to the another thread in the post #1.

  • Anonymous's avatar
    Anonymous
    12 years ago

    Yes, same problem here, totally rustling my jimmies.

  • Anonymous's avatar
    Anonymous
    12 years ago

    After 15 mins, i would drop out of game, very frustrating. so i decided to deep deep and google/research simular issues people have had. i came across and old artical about faults with BF3. it had simular faults, and a slight improvement to this situation. thus follows;

    turn off UPnP off your router and go to start run😕ervices.msc and stop services, SSDP discovery and UPnP, also run msconfig and untick in start up same services. i found that the client closed down connection happens less. works for me.

    Worth a try?

  • Anonymous's avatar
    Anonymous
    12 years ago

    After 15 mins, i would drop out of game, very frustrating. so i decided to deep deep and google/research simular issues people have had. i came across and old artical about faults with BF3. it had simular faults, and a slight improvement to this situation. thus follows;

    turn off UPnP off your router and go to start run😕ervices.msc and stop services, SSDP discovery and UPnP, also run msconfig and untick in start up same services. i found that the client closed down connection happens less. works for me.

    Worth a try?

  • Anonymous's avatar
    Anonymous
    12 years ago

    Still happens several times, every day

  • Anonymous's avatar
    Anonymous
    12 years ago

    Ok, guys.

    This is how I solved my problem:

    All previous tests I did (as you can see all thread-long), I was behind multiple Network Equipment (Router, Load Balance, Modems and Modem/Router).

    That means I was on Multiple NAT environment, and you'll see why that is important later.

    I'm going to repeat: all the other games that I have/played, INCLUDING Battlefield 3, work / worked fine.

    I've never needed to configure UPnP, DMZ, or Port Forwarding for them to work.

    As I stated before in this topic, I have 2 Internet Connections with 2 different ISP.

    One of them provided me a modem/router with locked configuration/firmware. I've tested BF4 directly connected to this ISP's router/modem, and that was it! No more "Client Closed Connection" problems.

    So if you ask me what is the problem:

    The BF4 makes a initial connection to EA servers to authenticate the client, before you can connect to the actual BF4 Multiplayer Server.

    If you're on a Multiple NAT Network, this first connection FAILS...

    ...unless you're trying to connect to

    1) an UNRANKED server or

    2) a RANKED server with a number of players that is less than the "Minimum Players to Start" (e.g. less than 4 players, on default server configuration)

    I understand that this problem might be affecting very few players that are in Multi-NAT, and that authentication to EA is important to keep cheaters outside of servers, but this is an issue that need to be addressed by EA / DICE, and not players. BF3 did not need this. Implement Multi-NAT support.

  • Anonymous's avatar
    Anonymous
    12 years ago

    ive had this same problem during game same message same length of time and everything just freezes and it kicks me and that message i didnt have this problem before china rising