Page MenuHomeFeedback Tracker

Unable to connect to dedicated server hosted on LAN
New, NormalPublic

Description

Game Version: 183417 (Windows dedicated server binary engine version, Steam, latest as of 05.20.2025)
Modded: No

When launching a dedicated server on a Windows 11 host system, the server starts properly and is visible in the server browser in game. Remote clients can connect to the server without incident, however, I cannot connect to it locally (from within the LAN). I've tried various combinations of bind addresses, ports, etc, nothing resolves the issue. I've used the server's NAT address as well as the public WAN address, same result. Correct ports are open in the router firewall as well as permissions granted in the Windows firewall.

This is happening with both Asus routers I've tried. The two routers are an RT-AX88U and a GT-AXE-16000. After doing some research online and in the Feedback Tracker here (see the referenced tickets below, they are the same symptoms), this seems to be an issue related to a security vulnerability in NAT which is addressed by something called "hair pinning". It was described as a solution in T165729 as follows:

"Enable NAT Reflection for 1:1 NAT" and "Enable automatic outbound NAT for Reflection". Your NAT reflection for the server must be Pure NAT.

The rather strange part about this, is apparently Asus router firmware has these things enabled by default. Additionally, there are no setting widgets in the administration interface to enable/disable/configure them in any way. As with the other two tickets, I have no issues with other games, including ArmA 3. This is specific to Reforger.

Details

Severity
None
Resolution
Open
Reproducibility
N/A
Operating System
Windows 11 x64
Category
General
Steps To Reproduce
  1. Install the Arma Reforger dedicated server via steamCMD
  2. Setup a basic configuration (I used Conflict Everon as the scenario)
  3. Launch the dedicated server
  4. Attempt to connect to the server from a machine located on same network (LAN) either from the in-game server browser or direct connect. Neither the NAT address nor the public IP will connect

Event Timeline

AtlasSix created this task.Wed, May 21, 4:18 AM