[SOLVED] Ark dedicated server/port forwarding issue

[Loetke]

I hope I'm asking this in the right place. I have set up a dedicated server for Ark: Survival Evolved so far no one has been able to locate it from the internet. It works perfectly fine on LAN. I have followed numerous setup guides to no avail. I have forwarded the required ports (7777, 27015, 27016) and have even gone as far as turning off my firewall completely just for the sake of trying to get this working. At this point I have a feeling it's my crappy AT&T router/modem.

To the details. My modem and router is an Arris NVG599. I am using a hard wired connection with a dlink switch being the only thing between my PC and the router. I have set a static IP for my PC. I doubt this matters, but the instructions say to include PC specs, so here you go:

MSI X99S Gaming 7
Core i7 5930K
32GB Gskill DDR4
Dual GTX 980
2x Samsung 500GB SSD RAID 0

 

[failboat]

When you connect to it locally you use the private ip address, but when remotely use the public ip address. On the forwarded ports make sure that you also picked the correct protocol. It's likely UDP or TCP.

If you can get to it locally it's probably not the firewall on your server.

For port forwarding it's possible that the FW rule isn't generated with the port forward. If there is a firewall section for WAN in your router you can see if there are any rules for Source (any) ->Dest LAN net (port 7777) ect.

 

[Loetke]

Alright, so I had assumed my public IP address was what I needed to be using, but it's not an option on my router. It only allows local addresses that I have to pick from a dropdown menu. I attached a picture to show what I mean. I attached a second picture to make sure I'm doing this correctly as I've never set up a server before.

 

[failboat]

The port forward should be your private ip. like 192.168.x.x
When you connect to the server from outside your home you have to type in your public ip address and the router forwards it to the server.

 

[Loetke]

The port forward should be your private ip. like 192.168.x.x
When you connect to the server from outside your home you have to type in your public ip address and the router forwards it to the server.

I have been using my private IP for this. It's in the image as 192.168.1.160. The server doesn't show up in the game's server selection screen. When I try to manually connect to the server from steam with the Run command "steam://connect/45.x.x.x:7777" I just get the message "server not responding." When friends try to join my game through steam they get the same message.

I'm at the end of my knowledge when it comes to routers. Does a public subnet have anything to do with this? I assume IP Passthrough is completely unrelated? Is there a way I can find out what the real culprit is?

 

[failboat]

The port forward should be your private ip. like 192.168.x.x
When you connect to the server from outside your home you have to type in your public ip address and the router forwards it to the server.

I have been using my private IP for this. It's in the image as 192.168.1.160. The server doesn't show up in the game's server selection screen. When I try to manually connect to the server from steam with the Run command "steam://connect/45.x.x.x:7777" I just get the message "server not responding." When friends try to join my game through steam they get the same message.

I'm at the end of my knowledge when it comes to routers. Does a public subnet have anything to do with this? I assume IP Passthrough is completely unrelated? Is there a way I can find out what the real culprit is?

Are you using a linux machine to host? you can monitor the interface with iftop. you can filter for destination port and see everything trying to get to the game server.

Also you should restart your router after adding the rules if you haven't. It might not load them into the firewall right away.

Windows machines have a firewall on by default. It's going to block all inbound connections. You might need a pass rule or just disable it while testing. If it works on LAN it shouldn't be this.