This is another attempt to solving a problem that seems to be hopeless. I'm running a Dayz Private server on a virtual windows machine. The Network is NAT'd. I have ports including 2302-2305 forwarded to the LAN host. I have updated DayZ files to 1.7.3 and BE .dll's to the latest, many many many times. I have tried updating the Arma2 beta patch between the last three latest releases. And my problem is, when the server starts, no one is able to join without being kicked by battleye for atleast 1-2 times. In addition to this, battleye randomly swipes all the players off the server ( with the message: client not responding ) I'm in full control of the virtualserver and the host. Are there some ports I need to open for battleye that are more or less 'hidden'. Taking all sorts of advice, just need to get forward with this.. ### EDIT I forgot to include in the initial post that I'm suffering from the "Receiving missionfiles 0kb/0kb"-stuck Every user on my server is suffering from that, until you press esc, and re-join. Thats when you are able to join the server. #### /EDIT #### EDIT2 Further investigation done, apparently the first connection attempt from a client that is trying to join the server shows as the servers gateway address. Battleye then kicks the client off the server for "Client not responding". When the client re-attempts to join, the server will now see the clients real IP-address and everything works like a charm. Does anyone have a solution for this? as I said, I have the ports 2302-2305 forwarded from host to the NAT'd guest machine. Theres no firewall. #### /EDIT2 #### EDIT3 Deleted the server files, reinstalled a clean arma2 installation from steam, merged the folder, installed the dayz private hive files. Now I got rid of the 0kb/0kb problem, but the battleye clientkicking remains... #### /EDIT3 -R