arma3server.exe fails to listen on steam ports when Steam Client is already running
Closed, ResolvedPublic
Actions

Description

Occurs on latest dev build (Beta)

For some users (as reported here http://forums.bistudio.com/showthread.php?147537-Tutorial-How-to-run-ArmA3-on-a-dedicated-server&p=2422167&viewfull=1#post2422167) arma3server.exe fails to listen on steam ports. This means that clients cannot connect to the server.

This occurs when the steam client is running and the arma3server.exe is launched.

If the arma3server.exe is launched prior to the steam client, the server initializes correctly.

This occurs regardless of the steam port configuration in the server.cfg.

Note that the issue does not occur with arma3.exe -server.

Steps To Reproduce

Launch Steam Client on PC
Launch arma3server.exe on same PC
run "netstat -ano" from command line and check to see if the arma3server.exe process is listening on default steam ports
Launch arma3.exe on same PC, attempt to connect to local server.
Connection timesout

Additional Information

Tupolov edited Additional Information. (Show Details)

Tupolov set Category to Server.

Tupolov set Reproducibility to Sometimes.

Tupolov set Severity to None.

Tupolov set Resolution to Fixed.

Tupolov set Legacy ID to 1025904624.May 7 2016, 2:53 PM

I wonder if this is related:

The command line looks a bit funky; a orphaned " and the param '-server' shouldn't be needed/used for the server binary.

Apart from that it's fine.

Fireball, it occurs regardless of params, that paste was a typo.

Not sure what is causing this as only some users experience it.

I no longer see this with the latest Steam Client (beta) and the Beta Dev dedi server. Anyone else still see this issue?

This no longer occurs on the dev version