skydive

Today BattlEye tried to update and now the ArmA 2 OA will not launch. I have tried all of the fixes posted on the BI forums as well as other sites and none have worked. I have uninstalled BattlEye AND Arma 2 OA, cleaned the registry, deleted all the BE .dll and .exe files from all the directories, disabled my AV software and reinstalled ArmA 2 OA and still when I try to launch A2 OA, it tries to update BattlEye and then the game will not launch. This is the 3rd time this problem with a BattlEye update has occurred quite recently and is absolutely ridiculous. The past couple of times the fixes posted around worked, but this time nothing I do is working. This is a real problem for me since I run a number of ArmA 2 OA based servers. What can be done to resolve this and more importantly, what can be done to PREVENT this in the future??

Is development still ongoing for this? I have been running a server for it, but there have been no players in a while. I'm sure it would gain more traction if more updates were coming.

I've been running this beta since it came out and have not seen that error ever. Running on both my server and client.

Meh, I'm not really concerned. If by some huge stretch the server got hacked, I would have it back up with a fresh image in a matter of a couple of minutes.

What you will need to do is change the port on your client to use a steam port other than 27016. Use 27017 or some other number. It's the same if you are running multiple server instances on a box; you need to open a range of ports so that each instance uses a different range and does not overlap. Here is how I have my dedicated box set up for ArmA 2 & ArmA 3 so that they can each use different ports: Ports open for both TCP and UDP: 2300-2400, 8766-8866, 27016-27116, 47624, 28800-28900 This was taken from a steam help thread on this subject: "If you intend on playing on your dedicated server from the same computer, you will need to change the server port in which your client listens to. The simplest way to do this is to right click on the game in your Steam games list, select Properties, select Launch Options, and add +port 27095 to the text box -- or any number of your choice really, providing it is different to what your server is using."

I am having the same problem with my server. What I have found is that your server will not show up in the server browser once you have converted to steam until a player has connected to your server and completely joins into the server fully starting the mission. Once this has happened, your server will show up in the browser. It's catch 22. How do you get players to join your server so that the mission is started and shows up in the server browser when they can't see your server listed until this happens??

The only real issues I've experienced so far was the problems fixed with the latest beta build. I could not view all of my new Steam UID, but I got around this with using the #userlist command on my server to see the part that had been cut off. Other than that, I had to edit my admin tools that check my UID to allow them to enable and be executed had to be modified as well as I had to add a few new BattlEye exceptions for some of my scripts, but other than that, it seems okay. I have noticed that I cannot see my own server in the server browser, so I just use the "Remote" button to enter the IP and port to connect to it. Obviously others can see it since I've had players on my server pretty steadily. ---------- Post added at 22:24 ---------- Previous post was at 22:18 ---------- This is on your client side or your server?

ArmA2 server requires the following ports open to UDP network traffic. TCP is not needed. port 2302 UDP ArmA2 game network communication. port+1 2303 UDP Gamespy public server reporting. port+3 2305 UDP Voice Over Net transmission. 8766 UDP Steam Port 27016 UDP Steam Query Port 47624 TCP/UDP (Direct Play Server) Does initial negotiation between client and server if I remember correctly 28800-28900 UDP Don't remember what these are for.

Ports and ranges you need to have open for a dedicated server: 2300-2400, 8766, 27016, 47624, 28800-28900

To be very specific, with a Cisco ASA or really any cisco device, if you want to allow a server to respond to ping you must allow ICMP echo-reply, ICMP time-exceeded and ICMP-unreachable on that server through the firewall. On the windows side, if you want a windows server to respond to ping, you have to enable under Inbound Rules: File and Printer Sharing (Echo Request - ICMPv4-In). This is what to look for if the server is running Windows Firewall.

This is a bug I have suffered from for quite some time now. Last night and today I have finally managed to resolve it. I have had numerous players on my public hive DayZ server receive the message box, "You were banned". This is not an admin ban nor is it a BattlEye Global ban. I had tried everything from full server reloads of the OS and ArmA 2 OA and all of my DayZ files and server files to no avail. I have been running on Windows Server 2012 and Windows Server 2012 R2 both since they released which looking back now is about the time this problem started popping up. It is sporadic and does not occur that often. Lately the problems seems to have been occurring more more frequently which lead me to try everything from complete reloads to even replacing most all of the server hardware in an attempt to resolve this problem. None of it had worked until now. This last full reload, I used Windows Server 2008 R2 instead of the 2012 variants. Immediately regular players that were getting the "You were banned" message were now able to connect and play on my server once again. Dwarden and any other devs, please take note of this! I would not be surprised to find that a similar problem has carried over into ArmA 3. I do run an ArmA 3 server with a mod I have been developing, but the users allowed to connect are white listed to help test and develop so I have not witnessed this problem in the A3 environment yet. At some point server providers (other than me now) will start to spin up ArmA 2 and ArmA 3 servers running on Windows Server 2012 and the R2 update which will cause this random and unpredictable problem. Somewhere (I don't know where since I don't write software anymore) code needs to be updated to rectify this problem. Please look into it!

In the 404Games version of Wasteland you should have to add your PID to the admins file in order to have access to the admin menu. If you are in the allowed admins list, you do not need to log in as admin with the #login command. If you have NOT been added to the admins list and can still access the admin functions you have a big problem on your hands.

I would recommend Gcam. I use it on my servers and it works great. http://www.armaholic.com/page.php?id=10390

Take a look at this thread. It may explain this phenomenon for you. I run all my servers on Server 2012 and in ArmA 3 I have this problem, but I use the VerifySignatures=2 switch in the config. It occurs whether I run it in a VM or directly on server hardware. http://forums.bistudio.com/showthread.php?152124-Server-Security

Sean- What I have done for this (and use for my ArmA 2 based servers as well) is within my ArmA 3\ directory I have ArmA 3\Cfg\1, ArmA 3\Cfg\2, etc. In each of those Instance Number directories I have copied the arma3.exe and renamed them to arma3_1.exe, arma3_2.exe, etc and put them in the corresponding directories. In addition to the exe files, in each of the instance number directories you want to have unique basic.cfg and config.cfg (name them whatever you want) for each server instance. I use a batch file for each of those that I launch from the root ArmA 3 directory. Also note the command line switches for -config -cfg and -profiles. Name the instance directory in those as well so all of your logs, etc are placed in the instance directories for the corresponding server. This is what my .bat files look like: @echo off :start C:\Windows\System32\tasklist /FI "IMAGENAME eq arma3_1.exe" 2>NUL | C:\Windows\System32\find /I /N "arma3_1.exe">NUL if "%ERRORLEVEL%"=="0" goto loop echo Server monitored is not running, will be started now @start /abovenormal "" /wait "C:\Program Files (x86)\Steam\SteamApps\common\Arma 3\Cfg\1\arma3_1.exe" -server -mod=@Arma2NET -name=Server -config=cfg\1\Wasteland.cfg -cfg=cfg\1\Arma3Alpha.cfg -profiles=cfg\1 -world=Stratis -port=2302 -nosplash echo Server started succesfully goto started :loop cls echo Server is already running, running monitoring loop :started C:\Windows\System32\timeout /t 10 C:\Windows\System32\tasklist /FI "IMAGENAME eq arma3_1.exe" 2>NUL | C:\Windows\System32\find /I /N "arma3_1.exe">NUL if "%ERRORLEVEL%"=="0" goto loop goto start