Spittingkobra

Solved the problem some how the battle eye service had been set to manual start when i updated to the new beta patch so i just set it to automatic and now it seems to be working.

Ofcourse they'v changed stuff in the beta patch sort of what its for... I have set every singel exe file that comes with arma 2, arma2 OA, the beta aswell as the server exe's to be allowed through the firewall on whatever port they like on both udp and tcp so it should not be a problem. I have also checked my firewall logs and it does show that it lets it through a few seconds before the game crashes. The AV/FW is not a problem in any other games and have never been a problem in arma either until beta build 101747 so obviously its something that they have changed that doesnt work well with ESET FW. Have double checked everything it works perfectly if i downgrade the beta patch to the one that came before 101747 but not on 101747 and after that. I have search through the other beta threads and can only find a reference to this thread in them. So any information on how to solve this would be greatly appriciated.

Well somehow it is but as i said my firewall works perfectly with arma pre beta patch build 101747, and i have done everything that can be done to allow it through the firewall so that only leaves that that something has changed with the networking concernign MP in build 101747 and on the following builds after that

Im having the same problem as Nixeh After updating my beta patch to ARMA2_OA_Build_102591 i had a pretty big problem , the game starts just fine and i can use all the buttons in the main menu except the MP button. When i Press Multiplayer it switches to the loading screen where it says Recieving and after a few seconds the background music stops and the program locks up completely to the point where i have to either logout from my user in windows or restart the whole computer. somehow even if im out of the game it belives that im in game and gives me the game mouse icon that i cant use to click on anything but the windows startbutton and the programs in that window. I have since tried alot of the betapatches and found out that i can run the betapatches up to and including ARMA2_OA_Build_101480 without any problems but not anyone after that one, they all give me the same error. After alot of tinkering around and changing my firewall rules to allow everything that has anything to do with ARMA 2 and OA. I found that only way for me to get the program running and letting me past the reciving lock when i click MP is for me to completely shutdown my firewall, this works with ARMA2_OA_Build_102591 and should work for those before it aswell (haven't tested it yet though), however this is not really a good solution. This leads me to believe that something was changed in ARMA2_OA_Build_101747 that effects network comunication. Have there been any additions in what ports should be open or have protocols changed for MP if so, what so i can reconfigure my firewall to fit the new beta patches? the AV/Firewall that im running is ESET Smart Security 5.095.0 OS : Windows 7 Ultimate 64bit Hardware I7 980x Nvidia 660 TI 16GB corsair Vengance 1600MHz