Jump to content

loose_unit

Member
  • Content Count

    4
  • Joined

  • Last visited

  • Medals

Posts posted by loose_unit


  1. if you have multiple interfaces always use the -multihome=IP commandline switch http://community.bistudio.com/wiki/Arma2:_Startup_Parameters#Server_Options

    If I use that option, I get the "Cannot start host on port 2302" Screenshot Here error... And no, I don't have anything else running on that port. It works when I use -ip=0.0.0.0 in my launcher but I cannot connect to the game. This is currently my launcher:

    "arma2oaserver.exe" -ip=177.28.1.127 -port=2302 "-config=server_patrol_ops\patrol_ops.cfg" "-profiles=server_patrol_ops" "-mod=@UK_SFTG;@CBA_A2;@CBA_OA;@CBA;@ACE;@ACEX;@JayArma2Lib;@ACRE;@Bowman;@ACEX_USNavy;@ACEX_RU" -noPause -noSound -cpuCount=2 -exThreads=1 -maxMem=2048

    It is a new problem - It all worked fine before and I haven't changed anything.


  2. I am having this issue also, our clans server had a hardware failure, so we were trying to setup locally hosted servers to kill some time - No one could start one, we would always get this "Joining Game" then "Connection Failed" issue.

    I then tried to run my previously working Wasteland server on my dedicated box and had the same issue, my dedicated box has Public IP addresses without NAT.

    Any updates from BI on this?

×