caddrel

The specific problem our group and others were experiencing (NNThink 2, servers suddenly stopped allowing connections through server browser) now appears to have been resolved as of a day or two ago. Other people may still be experiencing issues, but for our group at least that problem is gone and everyone can connect normally again through the server browser or by any other means. We didn't need to make any setup changes on clients or on the server. We're running a modded version of ARMA 2 (ACE and lots of islands).

Make sure your Day Z preset is selected on the left. Then right-click the server you want under "Server Browser", go to the "Updater Actions" sub-menu, then select "Join the server". It is possible to filter by name and other parameters by using the boxes over the various columns. To search for servers with "UK" in them, filter by "%UK" in the box above name for example.

"Connecting failed" can happen for a lot of reasons, which doesn't help. But a lot of people and servers are having "Connecting failed" issues accompanied by NAT and NNThink errors in their log file, which is what started happening last evening. Check your .rpt log file to be sure (see earlier in this thread for where it's located).

Just to double-check, what does your .rpt file say when you try to join using the Six Updater? Make sure to use the Six Updater not the Six Launcher; have no idea whether the Six Launcher will work at all.

Hrm, that's annoying. We tested it on one public server and one private server (hosted on someone's machine) running ARMA 2 Operation Arrowhead with mods.

A temporary solution which works for clients. Quoting my friend again: You CAN join servers that you get Connecting Failed to by using the Six Updater. You can join servers through the Six Updater's built-in server list. The Six Updater adds the command line parameters " -connect=<the Server IP here> -port=2302".

A temporary solution which works. Quoting my friend again: You CAN join servers that you get Connecting Failed to by using the Six Updater. The Six Updater adds the command line parameters " -connect=<the Server IP here> -port=2302".

Posted this on the other topics, but may as well put it here as well: 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." Doesn't help solve the problem at all, but at least gets us closer to figuring out what's going wrong.

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."

As a further diagnostic guys, go to your logfile (it's named arma2oa.rpt) and report what error you find there. The logfile is in: C\Users\<your username>\AppData\Local\ArmA 2 OA\

Another thread on the official BI forums that appears to be on the same issue: http://forums.bistudio.com/showthread.php?136844-Can-no-longer-host-multiplayer-games-with-a-friend

That's the error message people are getting. NNThink is a Gamespy API, and the problem started for people either 8:30 or 9:30GMT yesterday. Originally thought it was a Gamepsy issue and it would pass, but woke up today and still having issues getting people to connect to my ARMA 2 server.

There's a thread on the Troubleshooting forums where a lot of users are reporting the same issue: http://dayzmod.com/f...ed/page__st__20 A few unrelated posts in there, but most people reporting the same symptoms/problem. The main error on clients connecting is, "NAT Negotiation failed (NNThink - result 2)" The server error being shown is, "NAT Negotiation failed - unable to communicate with the server" This is happening with modded ARMA 2 OA servers as well: http://forums.bistudio.com/showthread.php?135123-Dedicated-Server-NAT-Negotiation-Failed&p=2193217#post2193217

This is not just a Day Z issue, our group is having trouble with base ARMA 2 with mods. In the middle of a playing session our server suddenly stopped accepting new players connecting, and hasn't worked since. A few related threads: http://dayzmod.com/forum/index.php?/topic/41845-95208-connecting-failed/ - other people with the same problem http://dayzmod.com/forum/index.php?/topic/41828-server-suddenly-stopped-working/ - Day Z server hosts have their servers suddenly stop working http://forums.bistudio.com/showthread.php?135123-Dedicated-Server-NAT-Negotiation-Failed - same issue when running ARMA 2 Operation Arrowhead servers

If I'm reading the comment I think you mean, that is completely unrelated.

Still having this issue. Have posted on the BI forums, but no replies there yet. Doesn't seem to be Day Z related, at least.

The problem started about an hour or two ago. I was in the middle of hosting an ARMA 2 game and then suddenly new people couldn't connect. Upon restarting the server (we wanted to get everyone in) no-one could connect at all, not even people who were playing fine just a few minutes before.

What are you guys getting in your arma2oa.RPT file? (this is the ARMA 2 error log file) It's located in C:\Users\<your user name>\AppData\Local\ArmA 2 OA\ If it says something along the lines of "NAT Negotiation failed (NNThink - result 2)", then it's a similar problem to this thread on the Server forum: http://dayzmod.com/f...topped-working/

I've just had exactly the same problem while running ARMA 2 with ACE (not running Day Z). Hosting off my local machine (non-dedicated server), been running this server for a few weeks without issues. Then, in the middle of a playing session this evening (we were playing an Isla Duala map with 5 people) a new person tried to join us, He got "Connecting failed" after entering the password correctly. One existing player disconnected to help him, and then was also unable to rejoin the server. I shut down the server and restarted it without closing the client, and then no-one could connect at all. Since then, everything has been tried with no success; suddenly no-one can connect to anyone else. .rpt fail reads "NAT Negotiation failed - unable to communicate with the server".

Choose the top three things you desperately want to be fixed, and three things you really want added. My three bugs: 1. Log off exploits. 2. The various duping exploits. 3. Helicopter permanently leaking fuel bug. My three features: 1. Even more vehicles around! Respawning vehicles! Vehicles are fun. 2. Survival made far harder; environment effects and zombies ramped up. 3. More base building stuff.

A few suggestions in two or three sentences each, with problem before suggestion. Currently: Vehicles require a large initial commitment to find and repair, but after that stage are trivial to steal from offline players. A friend suggested that players be allowed to remove parts from vehicles before they log out, providing a small measure of security. Wrench: allows a player to remove parts from cars (part must be >95% condition) Rubber tube: allows a player to remove fuel from a vehicle to a jerry can (must have at least 20L) Currently: Hiding vehicles and tents outside the map boundaries is 100% safe, but is tedious and immersion breaking. It can also allow a small group of players to monopolise all the vehicles on a server. Suggestion: Vehicles and tents should despawn if left or placed outside the map boundaries. Players should be given a countdown warning for moving outside the playable area (can add exclusion zones to this for the debug areas) Currently: Finding random tents in the wilderness is Fun, even abandoned ones. Suggestion: Tents should not despawn two/three days after a player dies. Instead, after that period give ANYONE the ability to pack the tent. Maybe let the original owner reclaim ownership of the tent if they return within the time limit. New item: Add camouflage netting (self explanatory). New item: Add smaller stashes using the "Guerilla Cache" model built into Arma 2. Can only carry five items. Rare spawn. TLDR: Was that really too long?

Not sure if this has been mentioned, but... This isn't the only method of duping. Currently tents that are packed and removed always reappear when a server restarts. It's very' date=' very easy to accidentally dupe tents if you're trying to get your tent position just right. It also allows a player to create hundreds of tents from just a single tent item, you just need to wait for the server to reboot for them all to appear. Also, on the topic of tents, see my thread about rubber tubes.

I like all of your ideas (especially the prospect of hunting down a mechanic just for the goddamn engine block parts he took so I couldn't steal his car) except this one. You die' date=' you should never be able to go back to your stuff without paying some kind of price*.[/quote'] That was simply an idea to counter the potentially onerous task of transferring gear from one tent to another whenever you die. Or, when a member of a group, someone else having to do it.

Great to see the helicopter fuel tank issue fixed. Apparently there's another bug where a helicopter's hull is unable to be repaired, experienced it once myself.