Forum Discussion
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.
- Anonymous12 years ago
Thanks for your reply, however, I've already tried all those fixes. None of them seemed to work so far.
Thanks for the effort though.
- Anonymous12 years ago
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.
- Anonymous12 years ago
Fact #10: Even with CCDC (Client Closed Down Connection), I can connect to a server if I try to reconnect SEVERAL times.
In 10 retries, I get to pass from "Connecting" to "Loading Level".
But if the server gets full, it's useless and frustrating because you join the queue, wait for your turn to connect and then CCDC, only to rejoin the queue and try again.After Server Update #6, it got worse here
- FIX #1: Ensuring that every network equipment (router, modem, load balance, etc) have UPnP Enabled and Firewall Disabled