4 years ago
Stuck on standby screen
When I select conquest or hazard zone my game starts loading into the game mode, goers to the map screen and says standby, showing the map I’ll be playing on but will never load past this screen. It ...
@EA_AticI'm glad I could help.
Its solve my friend same issue as all mention in this thread.
My friend for example cannot never join a game after the game starts, it show him the count down then "Waiting for leader to start game" and repeat. Now it work also in all mods include portal, which my friend cannot never join from game release.
Anyway, I suggest a test that help me resolve that issue -
Run a Trace Route:
• Open the Start Menu and search for ‘cmd’.
• Open the Command Prompt.
• When prompted, type ‘tracert’ followed by a space and the URL you want to test.
• Press the Enter key.
This test maps the internet traffic between your computer and an internet destination. It is often used to identify connectivity problems or delays.
Once the trace route is complete, check the first two IP addresses listed. If they are both private IP addresses, you are using a double NAT.
Private IP addresses usually appear in these number ranges:
10.0.0.0 to 10.255.255.255
172.16.0.0 to 172.31.255.255
192.168.0.0 to 192.168.255.255
In a double NAT set up, the connection will travel through two private networks, which can cause or add to other connectivity issues.
Forwarding ports can help resolve some of the issues you may be experiencing.
If necessary - I forward those ports I read that BF2042 use:
TCP:
5222, 9988, 1705, 20000-20100, 22990, 42127
UDP:
3659, 14000-14016, 22990-23006, 25200-25300
I use good application HERE that got free port checker, and it's reliable as you can check for example for "TCP 5222" and it tells you if this specific port open to your external IP, and its good indication if you got "double NAT" after you forward ports and they are still blocked.
Now the game works 100% of the time, Cheers EA team and players.🥳
I faced the exactly same issue: I cannot join any further matches after the first match.
My original network configuration is actually double NAT:
After several attempts of different configurations, I finally found the best and easiest solution:
There're several important conditions in order to ensure the Battlefield 2042 can build connection behind NAT:
Now the issue is totally fixed.
this problem got nothing related to connection issue of player's internet. Stop shifting the blame to the players Cheapskate EA game server is the culprit, but knowing EA. This will be never resolved ever.