I figured out how to connect to your own server

[Thorium]

As we know there is a issue that ARK allways tries to connect over the internet, even if we put in the local network ip. So if your router does not support NAT loopback you can't connect.

Well you can!
It's a bit complicated but you can set up your own loopback:

1.) Install the Microsoft loopback adapter: how to: https://technet.microsoft.com/en-us/library/cc708322%28v=ws.10%29.aspx
2.) Go to your network settings and choose "Change adapter Settings"
3.) Open the propertys of the second network connection (the loopback adapter connection).
4.) Open the propertys of "Internet Protocol Version 4 (TCP/IPv4)
5.) Select "Use the following IP address"
6.) You need to put your WAN IP address in there, you can find it here: http://whatismyipaddress.com/
7.) Put 255.0.0.0 in Subnet mask
8.) hit ok
9.) Start your server
10.) Start your Steam
11.) Go to View -> Servers -> Favorits
12.) Add a server
13.) Put your WAN IP in with the port like xxx.xxx.xxx.xxx:27015 It can take a few minutes until the server shows up.
14.) Double click your server in the favorite server list.
15.) ARK starts and connects to your server.

If your WAN IP changes you need to update the IP of the loopback adapter.

[Fei Long]

You brilliant son of a gun! I've tried so many things that failed. This worked! Thank you!

[Thorium]

Since i posted this, there was an update which added LAN support. It's working now if you connect by first starting ARK and then connecting with the LAN tab. No loopback needed anymore.

Connecting with the steam server list still needs NAT loopback.

[Fei Long]

Just an FYI. I couldn't see my server before even after the LAN update, but these steps made it work. Thanks again!

[ツ 𝔻𝕌ℂ𝕂 ツ]

Still cant connect

[Thorium]

That steps should not be necessary anymore. The problem was been fixed a long time ago in a patch.

[crimsondrac]

Necro'ed thread. Exactly the reason why people need to start new threads. Your issues may have the same symptoms but the cause is likely different. So, posting to an old thread that has already been solved will likely never get your problem fixed.

[ツ 𝔻𝕌ℂ𝕂 ツ]

oh well ty anyway

[BenlixFenix]

i used to just show up wich servers were on "lan" and my server show up but that was a long time a go i will save this amazing tutorial thkns ;)

[PantACRO4life]

Originally posted by Thorium:

As we know there is a issue that ARK allways tries to connect over the internet, even if we put in the local network ip. So if your router does not support NAT loopback you can't connect.

Well you can!
It's a bit complicated but you can set up your own loopback:

1.) Install the Microsoft loopback adapter: how to: https://technet.microsoft.com/en-us/library/cc708322%28v=ws.10%29.aspx
2.) Go to your network settings and choose "Change adapter Settings"
3.) Open the propertys of the second network connection (the loopback adapter connection).
4.) Open the propertys of "Internet Protocol Version 4 (TCP/IPv4)
5.) Select "Use the following IP address"
6.) You need to put your WAN IP address in there, you can find it here: http://whatismyipaddress.com/
7.) Put 255.0.0.0 in Subnet mask
8.) hit ok
9.) Start your server
10.) Start your Steam
11.) Go to View -> Servers -> Favorits
12.) Add a server
13.) Put your WAN IP in with the port like xxx.xxx.xxx.xxx:27015 It can take a few minutes until the server shows up.
14.) Double click your server in the favorite server list.
15.) ARK starts and connects to your server.

If your WAN IP changes you need to update the IP of the loopback adapter.

Hi buddy I found this post hopping that could fix my problem with those ark cluster ... I host on my own network (LAN) and everytime i want to move to one of my other server from the obelisk I have to use a VPN... can you help me

[Thorium]

Originally posted by PantACRO4life(Official):

Hi buddy I found this post hopping that could fix my problem with those ark cluster ... I host on my own network (LAN) and everytime i want to move to one of my other server from the obelisk I have to use a VPN... can you help me

Only if the server runs on the same PC as you play on. If it runs on another PC, check if you can activate NAT loopback on your router, if not, you need a new router that does support it.
This is a very old issue, that probably will not get fixed.

[Nutcutt3r]

Or just set network properties from public to private. There has never been a need to add your wan IP to a local network. It does not work that way.

[Thorium]

Originally posted by Nutcutt3r:

Or just set network properties from public to private. There has never been a need to add your wan IP to a local network. It does not work that way.

I think you misunderstand what the tutorial does. It does not add the WAN IP to your local network. It sets up a loopback on your PC, it's not on the network, only on the PC it's set up. It basicly just routes back to your own PC, so you can connect to your server running on the same PC using the WAN address, which is what cluster travel uses, it doesnt use the LAN address.
However, this is not needed anymore. It was a bug a long time ago and was fixed a long time ago. Thats why i suggest getting a router with NAT loopback.

Changing network properties as you suggest will not do anything.

[PantACRO4life]

Yes my 5 server clustered run on separate PC on same network and the rooter provide by my ISP doest support loopback XD so any suggestion

[淫神 Nafryti]

The tutorial provided by Thorium is to change your PC's IPv4 address from a DHCP provided IP from the router, to that which you define. This being your WAN IP in the tutorials case. THAT in its own respect can have a whole multitude of issues.
Easiest method would be to use a unique port for each server, and then use the direct connect method for each server.
I do understand that you can host multiple servers on the same computer, and what i find strange is some hosting companies do this easily without drastically changing the Port configuration, something i want to learn, something i consider magic lol.
most of the server ports are out of range of the normal server port list, you would have to add more than one port to the router's Port Forwarding for the computer hosting the multiple servers.
This is NOT new tech within the last 4 years, this is something that has been around for over the last 2 decades, its one of the limiting factors of IPv4.

My issue is similar but i have a 10Gbps link via SFP+, a completely different adapter and i can't seem to connect through that. Instead it tries to connect through the media bridge i use to connect across the house with. The issue has to be that the adapter isn't registered with the game engine or something along those lines. I've tried forcing it to join via the different adapter, steam recognizes it, but then the game fails to join. Could it be the 16348 jumbo frame? I'm at a loss.

[Thorium]

Originally posted by Nafryti:

The tutorial provided by Thorium is to change your PC's IPv4 address from a DHCP provided IP from the router, to that which you define. This being your WAN IP in the tutorials case. THAT in its own respect can have a whole multitude of issues.
Easiest method would be to use a unique port for each server, and then use the direct connect method for each server.

Thats not what it actually does. It only changes the IP of the loopback adapter, not your local network IP.
Also, as stated that tutorial is outdated and does not need to be used anymore. When ARK first came out, you could not direct connect to the local host, thats what the tutorial worked around. This issue has been fixed.