Stand Alone Server Issues

[A101Wayz]

I'm just about at my wit's end.  This topic has been brought up several times but with no resolution posted...
I had to shut down my server back in the early summer because I did not have time to admin it at the time.

Flash forward to about 2 weeks ago.  I finally had the time to get back to the game, so I updated my server and launched it.
When I tried to join from a different machine (same subnet), the server wasn't listed in the game's server browser.
The server could be managed using the remote server admin tool, and the server could be joined thru IP - both local and external IPs.
But I just couldn't get the server to show up in the game's server browser, even tho all ports were open and firewall was set correctly.
Today, I uninstalled and completely reinstalled the Dedi Server...  But couldn't get it to even start up.
Uninstalled that, and installed the base game version (which was how my server was originally run (using --server --norender)).
Current status:
Can use the web admin to change server settings and such.
Can't see the server listed in the game's browser.
Can no longer join the game using an external IP address. (messages says "Address is unavailable)
Can only join the game using the server machine's local IP address (192.168.X.XXX)
Ports are correctly open and forwarded.

I should add that I am using the stable release version and NOT open beta.

What am I missing?

 

Edited December 30, 2020 by A101Wayz

[Maverick87Shaka]

On 12/30/2020 at 6:41 PM, A101Wayz said:

Current status:

Can use the web admin to change server settings and such.
Can't see the server listed in the game's browser.
Can no longer join the game using an external IP address. (messages says "Address is unavailable)
Can only join the game using the server machine's local IP address (192.168.X.XXX)
Ports are correctly open and forwarded.

I should add that I am using the stable release version and NOT open beta.

What am I missing?

 

 

 

It's normal behavior of DCS. Most of the "home grade" router/modem doesn't support out of the box the "loopback", and that's why you can use your public IP internet address to connect to your internal server. It's not a problem at all.
It's the same for your computer inside the LAN that doesn't see the server in the multiplayer list. Again, it's not a problem.

Just ask to a friend to confirm if he can see from outside the server in the list and if he can connect and you'll be ok. 
Don't worry if you don't see the server in the list from LABN

Regards

 

[A101Wayz]

16 hours ago, Maverick87Shaka said:

 

It's normal behavior of DCS. Most of the "home grade" router/modem doesn't support out of the box the "loopback", and that's why you can use your public IP internet address to connect to your internal server. It's not a problem at all.
It's the same for your computer inside the LAN that doesn't see the server in the multiplayer list. Again, it's not a problem.

Just ask to a friend to confirm if he can see from outside the server in the list and if he can connect and you'll be ok. 
Don't worry if you don't see the server in the list from LABN

Regards

 

Thanks for the response.  I know it's not a big issue, but I was able to see my server while being on the same subnet, and also I was able to join using the external IP.  That is, until one of the recent most updates.
However, like you said, everyone else seems to be able to see the server from outside my local network.  So, all is well. 

[Maverick87Shaka]

12 hours ago, A101Wayz said:

Thanks for the response.  I know it's not a big issue, but I was able to see my server while being on the same subnet, and also I was able to join using the external IP.  That is, until one of the recent most updates.
However, like you said, everyone else seems to be able to see the server from outside my local network.  So, all is well. 

Are you sure you've not change something in your internal configuration? Keep in mind that maybe just keep enable the IPV6 protocol on both server and client in the same network will populate the list.
For me the behavior is the same from at least one year, I suspect something changed on your internal configuration if you was able to see in the past the server in the list