Page MenuHomeFeedback Tracker

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


Occurs on latest dev build (Beta)

For some users (as reported here 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.


Legacy ID
Steps To Reproduce
  1. Launch Steam Client on PC
  2. Launch arma3server.exe on same PC
  3. run "netstat -ano" from command line and check to see if the arma3server.exe process is listening on default steam ports
  4. Launch arma3.exe on same PC, attempt to connect to local server.
  5. Connection timesout
Additional Information - server.cfg

"C:\Program Files (x86)\Steam\SteamApps\common\Arma 3\arma3server.exe" -nosplash -winxp -noPause -world=empty -skipIntro -showScriptErrors -window -cpucount=1 -maxmem=1024 -config=server.cfg -port=2302 -cfg=arma3.cfg

Event Timeline

Tupolov edited Steps To Reproduce. (Show Details)Jun 25 2013, 12:09 PM
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

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.

Tupolov added a subscriber: Tupolov.May 7 2016, 2:53 PM

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