ASADS on Windows Server 2022 inside Hyper V on windows 10 won't even ping. LAN.

[Kanada]

The tittle says most of it. (LAN usage only) I have an Ark survival Ascended Dedicated server running inside a Windows Server 2022 Standard server on Windows 10 Pro Hyper V. I've opened Port 7777, 7778, 8888, and 27015 with TCP and UDP on the Windows Server fire wall manager. I also whitelisted the ArkAscendedServer.exe file in the firewall manager from C:\steamcmd\steamapps\common\ARK Survival Ascended Dedicated Server\ShooterGame\Binaries\Win64 I enabled ping on the windows server for testing.
I set up an internal switch on Hyper V that only the Windows 10 host and Windows server can use in addition to a pass through to NIC switch for internet access. Both NICs are set to privet network for relaxed security.

I lunch ASADS with the the batch file string start ArkAscendedServer.exe TheIsland_WP?SessionName=[♥♥♥♥♥♥♥♥♥]?ServerAdminPassword=[antisantism]?Port=27015?QueryPort=27015?MaxPlayers=[5]
Exit I have tried multiply versions including with the -NoBattleEye option.

I have populated C:\steamcmd\steamapps\common\ARK Survival Ascended Dedicated Server\ShooterGame\Saved\Config\WindowsServer\Game.ini with setting generated by the game it's self and copy/pasted right in.

The ASADS software starts without errors.

---

[2023.12.07-20.38.57:617][ 0]Log file open, 12/07/23 12:38:57
[2023.12.07-20.38.57:617][ 0]LogMemory: Platform Memory Stats for WindowsServer
[2023.12.07-20.38.57:617][ 0]LogMemory: Process Physical Memory: 170.60 MB used, 198.52 MB peak
[2023.12.07-20.38.57:617][ 0]LogMemory: Process Virtual Memory: 154.25 MB used, 159.98 MB peak
[2023.12.07-20.38.57:617][ 0]LogMemory: Physical Memory: 3155.71 MB used, 16843.21 MB free, 19998.92 MB total
[2023.12.07-20.38.57:617][ 0]LogMemory: Virtual Memory: 3054.95 MB used, 20399.97 MB free, 23454.92 MB total
[2023.12.07-20.38.58:061][ 0]ARK Version: 31.46
[2023.12.07-20.38.58:646][ 0]Primal Game Data Took 0.41 seconds
[2023.12.07-20.38.58:953][ 0]Server Initializing with BattlEye Anti-Cheat Protection. If you do not wish to use BattlEye, please launch with -NoBattlEye
[2023.12.07-20.38.58:955][ 0]BattlEye successfully started.
[2023.12.07-20.39.57:569][ 0]Server: "[♥♥♥♥♥♥♥♥♥]" has successfully started!
[2023.12.07-20.39.59:048][ 0]Commandline: TheIsland_WP?SessionName=[♥♥♥♥♥♥♥♥♥]?ServerAdminPassword=[antisantism]?Port=27015?QueryPort=27015?MaxPlayers=[5]
[2023.12.07-20.39.59:048][ 0]Full Startup: 61.67 seconds
[2023.12.07-20.39.59:048][ 0]Number of cores 4
[2023.12.07-20.40.03:357][ 2]wp.Runtime.HLOD = "1"

---

NETSTAT.EXE -a returns that port 27015 is open on all nics and listening.
...
UDP 0.0.0.0:27015 *:*
...

I have tested that the Windows Server instance is accessible over the virtual switch by the host via running a IIS web host on port 80 of the Windows Server instance and loading the demo page in the browser of the host computer by targeting the Server IP as the URL.

This is where everything stops making sense.

ASADS won't ping on the specified port on the loop back in the Windows Server instance or the Hyper V host. The server doesn't show in Steam --> View --> Game Servers ---> LAN or if I punch in the ip, even with the port number, in the add by IP in the favorites tab of the same window. Nor can I connect with the Console/cheat command in ASA with the open <ip-address>:27015 command.

For whatever reason the ASADS isn't talking to the LAN. Even with the firewall completely off on Windows Server.

If you know what might be going wrong here please help.

[antoine.lc.alc]

Hello

I've got exactly the same problem !
Did you manage to solve it ?

I'm trying to host ASA on a Windows Server 2022 on a Hyper-V VM.
The server starts up, the port is listening; but the other machines on the network can't see it, even with all the firewalls disabled.

[Gibs]

Have same issue since last update they did, noone can see the server in the list anymore despite it starts correctly. People said you could solve it by starting a single game and then (from console) connect over to your server via console command, simply as you then are already in game and dont need to find the server in any list as you enter it via Console command.

For me, that didn't work tho so I'm waiting for Ark to get a proper patch for us that run from a server! :(

[Evren]

Default port is 7777 and ASA does NOT use a Steam query port.

[antoine.lc.alc]

Originally posted by Kanada:

The tittle says most of it. (LAN usage only) I have an Ark survival Ascended Dedicated server running inside a Windows Server 2022 Standard server on Windows 10 Pro Hyper V. I've opened Port 7777, 7778, 8888, and 27015 with TCP and UDP on the Windows Server fire wall manager. I also whitelisted the ArkAscendedServer.exe file in the firewall manager from C:\steamcmd\steamapps\common\ARK Survival Ascended Dedicated Server\ShooterGame\Binaries\Win64 I enabled ping on the windows server for testing.
I set up an internal switch on Hyper V that only the Windows 10 host and Windows server can use in addition to a pass through to NIC switch for internet access. Both NICs are set to privet network for relaxed security.

I lunch ASADS with the the batch file string start ArkAscendedServer.exe TheIsland_WP?SessionName=[♥♥♥♥♥♥♥♥♥]?ServerAdminPassword=[antisantism]?Port=27015?QueryPort=27015?MaxPlayers=[5]
Exit I have tried multiply versions including with the -NoBattleEye option.

I have populated C:\steamcmd\steamapps\common\ARK Survival Ascended Dedicated Server\ShooterGame\Saved\Config\WindowsServer\Game.ini with setting generated by the game it's self and copy/pasted right in.

The ASADS software starts without errors.

---

[2023.12.07-20.38.57:617][ 0]Log file open, 12/07/23 12:38:57
[2023.12.07-20.38.57:617][ 0]LogMemory: Platform Memory Stats for WindowsServer
[2023.12.07-20.38.57:617][ 0]LogMemory: Process Physical Memory: 170.60 MB used, 198.52 MB peak
[2023.12.07-20.38.57:617][ 0]LogMemory: Process Virtual Memory: 154.25 MB used, 159.98 MB peak
[2023.12.07-20.38.57:617][ 0]LogMemory: Physical Memory: 3155.71 MB used, 16843.21 MB free, 19998.92 MB total
[2023.12.07-20.38.57:617][ 0]LogMemory: Virtual Memory: 3054.95 MB used, 20399.97 MB free, 23454.92 MB total
[2023.12.07-20.38.58:061][ 0]ARK Version: 31.46
[2023.12.07-20.38.58:646][ 0]Primal Game Data Took 0.41 seconds
[2023.12.07-20.38.58:953][ 0]Server Initializing with BattlEye Anti-Cheat Protection. If you do not wish to use BattlEye, please launch with -NoBattlEye
[2023.12.07-20.38.58:955][ 0]BattlEye successfully started.
[2023.12.07-20.39.57:569][ 0]Server: "[♥♥♥♥♥♥♥♥♥]" has successfully started!
[2023.12.07-20.39.59:048][ 0]Commandline: TheIsland_WP?SessionName=[♥♥♥♥♥♥♥♥♥]?ServerAdminPassword=[antisantism]?Port=27015?QueryPort=27015?MaxPlayers=[5]
[2023.12.07-20.39.59:048][ 0]Full Startup: 61.67 seconds
[2023.12.07-20.39.59:048][ 0]Number of cores 4
[2023.12.07-20.40.03:357][ 2]wp.Runtime.HLOD = "1"

---

NETSTAT.EXE -a returns that port 27015 is open on all nics and listening.
...
UDP 0.0.0.0:27015 *:*
...

I have tested that the Windows Server instance is accessible over the virtual switch by the host via running a IIS web host on port 80 of the Windows Server instance and loading the demo page in the browser of the host computer by targeting the Server IP as the URL.

This is where everything stops making sense.

ASADS won't ping on the specified port on the loop back in the Windows Server instance or the Hyper V host. The server doesn't show in Steam --> View --> Game Servers ---> LAN or if I punch in the ip, even with the port number, in the add by IP in the favorites tab of the same window. Nor can I connect with the Console/cheat command in ASA with the open <ip-address>:27015 command.

For whatever reason the ASADS isn't talking to the LAN. Even with the firewall completely off on Windows Server.

If you know what might be going wrong here please help.

I think i found the issue !
The Default vSwitch on a Windows 10 host running Hyper-V is NAT-type so the udp cannot be managed (the ASA server is UDP based).
I've just done exactly the same installation on a dedicated host (not a VM) and everything works.

[Kanada]

Alright. Thank you for your input. I will troubleshoot from that angle for a while and see what I find.

[Mr. Scoot]

ASA does not use the query port and you need to set the game port with

 -port=

the same goes with maxplayers

-WinLiveMaxPlayers=

as an argument and not part of the launch URL.

[Kanada]

Originally posted by antoine.lc.alc:

Originally posted by Kanada:

The tittle says most of it. (LAN usage only) I have an Ark survival Ascended Dedicated server running inside a Windows Server 2022 Standard server on Windows 10 Pro Hyper V. I've opened Port 7777, 7778, 8888, and 27015 with TCP and UDP on the Windows Server fire wall manager. I also whitelisted the ArkAscendedServer.exe file in the firewall manager from C:\steamcmd\steamapps\common\ARK Survival Ascended Dedicated Server\ShooterGame\Binaries\Win64 I enabled ping on the windows server for testing.
I set up an internal switch on Hyper V that only the Windows 10 host and Windows server can use in addition to a pass through to NIC switch for internet access. Both NICs are set to privet network for relaxed security.

I lunch ASADS with the the batch file string start ArkAscendedServer.exe TheIsland_WP?SessionName=[♥♥♥♥♥♥♥♥♥]?ServerAdminPassword=[antisantism]?Port=27015?QueryPort=27015?MaxPlayers=[5]
Exit I have tried multiply versions including with the -NoBattleEye option.

I have populated C:\steamcmd\steamapps\common\ARK Survival Ascended Dedicated Server\ShooterGame\Saved\Config\WindowsServer\Game.ini with setting generated by the game it's self and copy/pasted right in.

The ASADS software starts without errors.

---

[2023.12.07-20.38.57:617][ 0]Log file open, 12/07/23 12:38:57
[2023.12.07-20.38.57:617][ 0]LogMemory: Platform Memory Stats for WindowsServer
[2023.12.07-20.38.57:617][ 0]LogMemory: Process Physical Memory: 170.60 MB used, 198.52 MB peak
[2023.12.07-20.38.57:617][ 0]LogMemory: Process Virtual Memory: 154.25 MB used, 159.98 MB peak
[2023.12.07-20.38.57:617][ 0]LogMemory: Physical Memory: 3155.71 MB used, 16843.21 MB free, 19998.92 MB total
[2023.12.07-20.38.57:617][ 0]LogMemory: Virtual Memory: 3054.95 MB used, 20399.97 MB free, 23454.92 MB total
[2023.12.07-20.38.58:061][ 0]ARK Version: 31.46
[2023.12.07-20.38.58:646][ 0]Primal Game Data Took 0.41 seconds
[2023.12.07-20.38.58:953][ 0]Server Initializing with BattlEye Anti-Cheat Protection. If you do not wish to use BattlEye, please launch with -NoBattlEye
[2023.12.07-20.38.58:955][ 0]BattlEye successfully started.
[2023.12.07-20.39.57:569][ 0]Server: "[♥♥♥♥♥♥♥♥♥]" has successfully started!
[2023.12.07-20.39.59:048][ 0]Commandline: TheIsland_WP?SessionName=[♥♥♥♥♥♥♥♥♥]?ServerAdminPassword=[antisantism]?Port=27015?QueryPort=27015?MaxPlayers=[5]
[2023.12.07-20.39.59:048][ 0]Full Startup: 61.67 seconds
[2023.12.07-20.39.59:048][ 0]Number of cores 4
[2023.12.07-20.40.03:357][ 2]wp.Runtime.HLOD = "1"

---

NETSTAT.EXE -a returns that port 27015 is open on all nics and listening.
...
UDP 0.0.0.0:27015 *:*
...

I have tested that the Windows Server instance is accessible over the virtual switch by the host via running a IIS web host on port 80 of the Windows Server instance and loading the demo page in the browser of the host computer by targeting the Server IP as the URL.

This is where everything stops making sense.

ASADS won't ping on the specified port on the loop back in the Windows Server instance or the Hyper V host. The server doesn't show in Steam --> View --> Game Servers ---> LAN or if I punch in the ip, even with the port number, in the add by IP in the favorites tab of the same window. Nor can I connect with the Console/cheat command in ASA with the open <ip-address>:27015 command.

For whatever reason the ASADS isn't talking to the LAN. Even with the firewall completely off on Windows Server.

If you know what might be going wrong here please help.

I think i found the issue !
The Default vSwitch on a Windows 10 host running Hyper-V is NAT-type so the udp cannot be managed (the ASA server is UDP based).
I've just done exactly the same installation on a dedicated host (not a VM) and everything works.

So I set up an "internal switch" and a DHCP server facing out of it towards the host OS and had no luck. I have an "external switch" directed to a dedicated USB WiFi dongle for bandwidth reasons. The WIFI network comes with the room and everything connected is on it own throttled VLAN. In a vain act of desperation I set up a USB Ethernet adapter as an "external switch" under the management of a Windows Server DHCP server and plugged a cable from the USB adapter into the motherboards Ethernet jack. No dice. Do you know if Windows 10 Pro Hyper V just blocks all UDP or NATs every connection through it's switches?

Oh. You maybe asking yourself how I intend to play on "LAN" when my WiFi is VLANed. I've already set up a Pritunl VPN on a VPS hosting service. I can put as many people as I want on one VLAN and enable port forwarding to connect console players directly to the ASADS via IP. I've tested it with other ports and services and it works. This is why I need it in a VM though. I can't expose my host computer to the WWW with port forwarding. The computer I am using has enough power to run the game and a modestly sized ASADS. I don't have the money and space for a second computer.

Originally posted by Mr. Scoot:

ASA does not use the query port and you need to set the game port with

 -port=

the same goes with maxplayers

-WinLiveMaxPlayers=

as an argument and not part of the launch URL.

Do you know if there is a command to tell the ASADS what network interface/s to use when there a multiple to choose from. Should it be answering on all of them by default. I'm wondering if that's my problem or at least a problem. Oh and thank you. Your commands worked.

Originally posted by antoine.lc.alc:

Hello

I've got exactly the same problem !
Did you manage to solve it ?

I'm trying to host ASA on a Windows Server 2022 on a Hyper-V VM.
The server starts up, the port is listening; but the other machines on the network can't see it, even with all the firewalls disabled.

Still cracking away at it. I'll post if I find a work around. Please do the same.

[123]

This seems to be related to the system. I have three devices in the same LAN, namely, win11, windows server 2019, windows server 2022, win11 and 2019, which start ASADS normally, but 2022 has the same problem as you.

[123]

Originally posted by 123:

This seems to be related to the system. I have three devices in the same LAN, namely, win11, windows server 2019, windows server 2022, win11 and 2019, which start ASADS normally, but 2022 has the same problem as you.

In windows server 2022, if I add a MOD, the server crashes on startup with the crash error: Requested mods failed to load on server.

[123]

Originally posted by 123:

Originally posted by 123:

This seems to be related to the system. I have three devices in the same LAN, namely, win11, windows server 2019, windows server 2022, win11 and 2019, which start ASADS normally, but 2022 has the same problem as you.

In windows server 2022, if I add a MOD, the server crashes on startup with the crash error: Requested mods failed to load on server.

Yeah, me too, this problem has been identified, and it is not a problem with windows server 2022, because I re-installed the server to windows server 2019, and this computer still cannot normally start the dedicated server, And it's worth noting that the computer that failed to boot will say "Couldn't load mods library from disk", If any mod is added, this will cause the program to crash and exit, My computer in question is AMD 7900x CPU, and the other two computers are completely normal, they are Intel cpus, I don't know what has to do with this.

[Kanada]

What I did that worked.

First off the software environment I am using is almost completely different now.

I am using:

Ubuntu Studio 22.04 [ubuntustudio.org] for the host OS. It's what I had on hand. If you want to replicate my set up point for point then use 22.04 but Ubuntu Studio 24.04[ubuntustudio.org] Should work just as well if not better as 22.04 has some bugs in it log in and lock screen that can cause random lock ups. If you use 22.04 enable the auto log in and disable the lock screen. It's also note worthy that in theory any recent Ubuntu flavor[ubuntu.com] should work as it only needs support for the virtual machine in use.

For the virtual environment I am using Oracle's VirtualBox. [www.virtualbox.org] This I believe to be the key change not the host environment. The installation in Ubuntu Studio is not entirely painless as you have to add your user name to the "vboxusers" group in order for VirtualBox to run correctly. The command string "sudo adduser yourusername vboxusers" will do this for you in Ubuntu. You will have to restart after you make the change for the change to take effect.

You will want to install VirtualBox Extention Pack[www.oracle.com] before continuing.

There is a means to import Disk Images from Microsoft's Hyper-V format of .VHDX to Oracle's VirtualBox's native .VDI format. The easiest method is to simply add the .VHDX image to the VirtualBox Media manager under the "Hard Disk" tab. The select the image and select "Copy" from the icons at the top of the window. There you can select the desired format in the wizard that is brought up. While converting the Windows Server 2022 Standard is possible. it may void the OS's Product Key.

Windows Server 2022 Standard is still what I am using to host ASADS.
The Windows Server disk image will not want to start in VirtualBox before making some changes to the virtual machine environment. Regardless of weather you are converting an existing Hyper-V installation or installing from scratch the default virtual machine settings are not sufficient for Windows Server 2022 Standard. You will need to enable "Enable EFI" in the "System" Section on the "Motherboard" tab. Uncheck the "Enable Hardware Clock in UTC Time" option if it is checked. Under the "Processor" tab of the "System" Section make sure "Enable PAE/NX" is checked. As far as I recall these where the only changes I made before Windows server began booting. My attempt at converting the Hyper-V machine to VirtualBox took several reboots to straiten it's self out. As I had accidentally saved the wrong back up of my Hyper-V installation of Windows Server all my previous work was lost do to this error. So I installed Windows Server 2022 Standard again on a fresh VirtualBox virtual machine. Went through the activation process. Downloaded and installed the first round of updates. Then install the "VitualBox Guest Additions" [www.virtualbox.org]

It's worth stating that you can always run Windows Server 2022 Standard on bare metal and not mess with virtualization. Out side specific use cases bare metal installation is probably the best option. Moving on.

Next is is the installation of SteamCMD and ARK: Survival Ascended Dedicated Server[steamdb.info]. There are too many guides for this but This one looks fine[ark-unity.com]. However it is missing a step. Windows Server 2022 does not ship with Microsoft Visual C++ Redistributable[learn.microsoft.com]. I don't know why but it doesn't and you need to download and install it before ASADS will run on Windows Server 2022 Standard.

Next is exposing my server to the internet. I choose to use Pritunl[pritunl.com] on a virtual machine running in the cloud on Linode/Akamai[www.linode.com] provider. Pritunl has built in support for Let's Encrypt[letsencrypt.org]. You're gonna need to look at some tutorials and documentation as well as shell out some cash on a URL and Pritunl Premium subscription on top of the virtual machine instance running in the cloud. Again. outside specific use cases this is probably excessive. If you are running on bare metal or configure VirtualBox network setting correctly you can simply log into your internet router and configure a DMZ to connect to the internet.

I hope I have provided some helpful information here.