Server starts but cannot be connected to (discontinued)

[Grombald 11]

Hi everyone,

after the server of my players group was shut down I tried to create a temporary solution with a second PC in my living room, where I run the server on. The problem is, though the server starts up correctly, it cannot be found in the server browser nor can it be connected to directly via IP.

 

The server runs on Windows 10 and has an own Steam-Account. The game version is 1.66.

The server window starts and the usual four lines of text apear. According to the RPT-file, the server is "Connected to Steam servers".

 

Some things I tried so far:

- Starting with ARMA 3 Launcher

- Starting with TADST (Steam on and off)

- Starting with Batch-file (the command line is to long for links)

- Forwarding the ports 2302-2305, the BE-ports and the steam-ports (270XX) in the router and the windows firewall

- Activating UPNP (opens ports 2302, 2303 and 2304)

- Deactivating windows firewall

- Deactivating port filtering at all

 

Even when launching A3 and hosting a new game with the ingame-server-browser, the server cannot be found.

 

I'm out of ideas. I'd much appreciate if somebody had an idea what else to try.

Cheers!

[Capwell 16]

Make sure in TADST you are using 2302 as the port.

Make sure that in your server directory, that the appid.txt has 107410.

Make sure you port forward within your router and windows firewall.

[Capwell 16]

Use the windows cmd (command prompt) and type ipconfig, to find your IPv4 Address.

 

Like so: https://gyazo.com/c42e71ace4bdb9bab4f4b70d91824a93

These are wrong: https://gyazo.com/aa2680fd9f9d3b03f11ba188b5ac057a

These are right: https://gyazo.com/0efb72dbc17cf6d159f72118ada3def5 

[Grombald 11]

Thanks for your reply.

 

 

I just found out that my ISP only supports IPv4 adresses via DS-lite tunneling (IPv4 and IPv6 go out but only IPv6 goes in), somebody else will have to host the server in his livingroom...

 

The problem can be considered discontinued.