Connecting Failed

Hi all,

I know some people have posted about this error before In Dayz, (it also occurs in OA) so isn't actually an issue with Dayz itself( as far as I can tell) it seems to me that since the last BE update a few Beta patches ago people seem to be getting the problem, there is no other error message, you attempt to connect to a server that your friends can get on fine only to get "connecting Failed", or you may be able to get on a server then after you disconnect every time after that you get that message. I have tried reinstalling ARMA2 free and OA(steam) as well as manually reinstalling BE and also rolling back the Beta patch version to no effect. I have both installed on 2 computers in different locations one of them works fine on said problem servers and one doesn't. I have seen a growing trend of people getting this issue in the past few weeks so have made a post on the Dayz forum as well as here (because it effects both Vanilla and modded games), so any suggestions would be great.

I also have this problem...tried everything,router settings,re installing game and nothing....Arma 2 Free,and CO...stuck to campaign atm...

There's a thread on the multiplayer forum here with server owners reporting this same issue. A lot of server owners began reporting this problem Sunday at 8:30pm to 9:30pm GMT:

http://forums.bistudio.com/showthread.php?135123-Dedicated-Server-NAT-Negotiation-Failed&p=2192882&viewfull=1#post2192882

A lot of Day Z users having the same issue (a few unrelated posts, but mostly all reporting exactly the same symptoms):

http://dayzmod.com/forum/index.php?/topic/36686-connecting-failed/page__st__20

Here's the thread with Day Z server owners where you can see the time scale clearly. Contrary to what one person says, this problem hasn't been resolved:

http://dayzmod.com/forum/index.php?/topic/41828-server-suddenly-stopped-working/

---------- Post added at 04:06 PM ---------- Previous post was at 03:45 PM ----------

A friend did some research:

"On the servers where I can connect, Arma immediately tries to connect to port 2302

Whereas the games where it doesn't work, ArmA tries to negotiate the UDP using 69.10.30.x IPs - I'm guessing those are the negotiation servers.

(And they answer with ICMP Destination unreachable)

IGN owns Gamespy, right?

The 69.10.30.x IPs resolve through IGN's dns servers.

It could be that in case where the server is behind a NAT it'll do the negotiation."

---------- Post added at 04:25 PM ---------- Previous post was at 04:06 PM ----------

A temporary solution which works. Quoting my friend again:

"I just tested joining through Six Updater and that one managed to join a server I couldn't join through the in-game browser.

*I started my local server without changing anything*

Not seeing your server in that list though so refreshing it. Takes a while.

Well that is interesting.

I'm in"

You CAN join servers that you get Connecting Failed to by using the Six Updater. You can use the Six Updater's built in server browser.

The Six Updater adds the command line parameters " -connect=<the Server IP here> -port=2302".

We still can't join using the in-game browser. But we can get a game going by all joining the server via the Six Updater.

Just as a follow-up this problem appears to be resolved for our group (no setup changes were needed). We can now join the previously affected servers via the server browser again.

Does appear to have been a problem on Gamespy's end.

Just as a follow-up this problem appears to be resolved for our group (no setup changes were needed). We can now join the previously affected servers via the server browser again.

Does appear to have been a problem on Gamespy's end.

Reporting the same, issue was resolved after 2 days.