Question about opening two servers using Server Manager

[skawlsfud55]

My friend opened two servers using Server Manager, and the server owner is my friend. I can travel to the second server through the Obelisk from the first server, but my friend, who is the server owner, cannot see the second server. Why is this happening?

I found online that sometimes server owners can't access the second server due to a game error, and I also read that if I install Server Manager on my computer and enter the same Cluster ID, it should work. So, I installed Server Manager on my PC, set up port forwarding, and disabled the firewall, but the server I created only shows up in the LAN. Why is this happening?

Is there a way for my friend and I to both use servers 1 and 2 together?

[Mathius]

"Server Manager" is a pretty generic term. Are you talking about Ark Server Manager?

Anyways, the problem you're running into almost certainly has nothing to do with ASM and has to do with your port forwarding and/or router.

It's possible you're getting something regarding something called, "Nat loopback" and your router may not support what you're trying to do, or more likely just the way you have something set up in your home network.

I would love to help you out more, but I had this issue, and eventually I had to enlist my friend who designed the network for a shipping company in this area to help me and it ended up being something simple I did wrong with my network settings.

I will say making sure you have the correct TCP/UDP settings in your port forwarding. (most routers seem to have a setting that allows both, but IIRC, you want UDP (don't quote me on that)).

Your server and peer port need to be separate ports. I made mine sequential to make it easier.

Then you want a Query port for each server. This allows your friends to find it on Steam's network software, and also allows you to use the RCON feature. My query ports are in a much higher range.

For example, you might have:

Server: 8888
Peer: 8889
Query: 26088

(Don't use these values, they're just an example) The ranges ASM defaults to are a good start, I think.

You should also allows shootergame access on your firewall.

I am by no means an expert though, and I had to set this stuff up once and it just works and if I want to start a new server I just setup a new set of ports on the router's port forwarding and copy the profile in ASM and update the ports.

So there's some network setup that I probably dont recall anymore.

[Mathius]

You might try either Twitchydigits videos:

https://www.youtube.com/watch?v=0MqYGXmbrrA
https://www.youtube.com/@TwitchyDigitsGaming

Or

MrBazibaz has a couple of videos on his channel that are helpful:
https://www.youtube.com/watch?v=sbqbiKevnCE
https://www.youtube.com/@MrBazibaz/videos

Both of them have discords you can ask questions on. I don't think either of them keep on on ASE these days (maybe ASA), but Twitchy's videos are more recent.

[Liralen]

It sounds like your friend's router or ISP does not allow NAT loopback.

In your case, it sounds like your ISP uses CGNAT.

I have had both these things happen while trying to run gaming servers. The NAT loopback issue was resolved by buying my own router and returning the ISP's rental, which saved money in the long run as well as being a much better router.

If the ISP uses CGNAT, you can probably pay an extra monthly fee for a static IP. That's what I'm currently doing.

[skawlsfud55]

Originally posted by Mathius:

"Server Manager" is a pretty generic term. Are you talking about Ark Server Manager?

Anyways, the problem you're running into almost certainly has nothing to do with ASM and has to do with your port forwarding and/or router.

It's possible you're getting something regarding something called, "Nat loopback" and your router may not support what you're trying to do, or more likely just the way you have something set up in your home network.

I would love to help you out more, but I had this issue, and eventually I had to enlist my friend who designed the network for a shipping company in this area to help me and it ended up being something simple I did wrong with my network settings.

I will say making sure you have the correct TCP/UDP settings in your port forwarding. (most routers seem to have a setting that allows both, but IIRC, you want UDP (don't quote me on that)).

Your server and peer port need to be separate ports. I made mine sequential to make it easier.

Then you want a Query port for each server. This allows your friends to find it on Steam's network software, and also allows you to use the RCON feature. My query ports are in a much higher range.

For example, you might have:

Server: 8888
Peer: 8889
Query: 26088

(Don't use these values, they're just an example) The ranges ASM defaults to are a good start, I think.

You should also allows shootergame access on your firewall.

I am by no means an expert though, and I had to set this stuff up once and it just works and if I want to start a new server I just setup a new set of ports on the router's port forwarding and copy the profile in ASM and update the ports.

So there's some network setup that I probably dont recall anymore.

Port forwarding is set up correctly without any issues. I have completed the TCP/UDP settings for the server port, query port, and RCON port. I’ve also double-checked the numbers several times. After completing all the settings in Ark Server Manager and starting the server, the "running" message appears, and there are no messages like "loopback" or "LAN only." So, I thought everything was fine. However, in the game, my friend cannot find my server, and I can only search for my server within LAN. The firewall settings you mentioned are also all allowed.
I'll give it a try after watching the video you linked. Thank you!

[Mathius]

If it's an issue with your ISP's modem as Liralen is suggesting, you can also see if your modem/router supports "IP Passthrough".

If it has that setting, you can buy a newer router, and set your modem in IP Passthrough mode and utilize the settings on the router.

[skawlsfud55]

Originally posted by Liralen:

It sounds like your friend's router or ISP does not allow NAT loopback.

In your case, it sounds like your ISP uses CGNAT.

I have had both these things happen while trying to run gaming servers. The NAT loopback issue was resolved by buying my own router and returning the ISP's rental, which saved money in the long run as well as being a much better router.

If the ISP uses CGNAT, you can probably pay an extra monthly fee for a static IP. That's what I'm currently doing.

My friend and I are using the same ISP and devices, but while my friend’s server 1 opens without any issues, even though I opened my server in the same way, it only shows up on LAN on my PC, even though the Ark Server Manager says it's 'running'.

[Liralen]

If your hardware is identical, then that implies that there are differences in the way each of you set up the server.

Although having the same ISP does not necessarily mean your services and routers are identical. I've been able to cure these problems by simply returning my router and buying my own, and now that CGNAT is a thing, by paying extra for a Static IP. CGNAT is a way for the ISP to avoid the problem of of limited IPv4 addresses, instead of upgrading their equipment to IPv6. IPv4 is running out of addresses.

If it's a NAT loopback issue with a router, it usually manifests as everybody else being able to access your server but you (and everyone else on your LAN) not being able to access your server. ISPs have a huge financial incentive to make you pay a monthly fee to rent you a piece of junk router that cannot be used to run a server that you can't access.

If you don't have a static IP, your server is only accessible by people on your LAN. My guess is that firewalls would also cause this issue. but those are like a black art to me, in that I have to follow instructions that makes about as much sense as casting a magic spell for my operating system and virus protection.

That's pretty much the extent of my knowledge. No change of ISP was required, but rather a change of the services they offer (or rejecting it, like their awful routers). I've had these problems before, cured it as I described, but have no idea what other things may cause the same issues.

I would be interested in how you cured it, just so I know when it happens to me the next time. :)

Edited Note: I also use Ark Server Manager. I have had no problems that it caused.