Dedicated Server - Ports not listening

[luckymod13]

Preface: I'm a network admin and server admin by profession.
All ports are forwarded. IP is static. LAN IP reserved outside of scope bound to server MAC. Tried disabling all firewalls and security (temporarily of course), Ports and apps are all allowed in server firewall. Server side and client side software fully updated. All drivers fully updated on modern equipment. All OS updated to most recent stable versions and releases.

When I run my dedicated server, it shows in the game list. I can join, enter password, but then it shows connecting 5/5 followed by a connection error. I have the same experience attempting to join it while local with it's local LAN IP and when connecting externally with the static WAN IP.

To test, I've run powershell "test-netconnection -p" for both of the TCP ports (udp is testing not supported by that test-netconnection), I've also used external / remote port testing. I can ping my server IP without any issue.

What is interesting is a "netstat -a" does not show ANY of the VRising ports "listening" or established. They aren't listed at all.

I've got the suspicion that the SteamCMD method of server hosting is busted, shouldn't the ports be listening? I have other open ports listening for other services and they test good.

Anyone else having this issue? Thoughts?

[Krizzleybear]

I may have something, I'm hoping its not circumstantial. i was experiencing similar issues, until I checked another guide.

The guide over at "Rock Paper Shotgun" said to make sure the server name and save name in .bat have to match the server settings .json.

I had a mismatch, thinking the .json overrides the .bat, but it doesn't.

Once I changed it to match, my default settings with simple port forward as per settings/guides allowed for direct connection via fixed IP. I think maybe having a mismatch between the server .bat and the server settings .json silently errors when initialising the server, and in order to successfully setup the listen/network, they both need to reference the same server name/save name due to some files, etc.

Worth a shot ¯\_(ツ)_/¯

[Kunogi]

Make sure to set all the JSON settings on the copy you throw on the save-data accordingly to your network, also try setting the server name by the JSON instead of from command line to start the server, i did not use steamcmd tho, as its not needed to have it connected to any steam client to host servers, also, just to make sure, the game uses (by default) 9876 in UDP and TCP, 9877 in UDP, the 9876 is game and man. connection (udp / tcp) and 9877 query port (udp), make sure it matches on json what is on the router.