ARK: Survival Evolved

ARK: Survival Evolved

View Stats:
(ASM) Server Inquiry
Trying to set up a dedicated server for my family and I using Ark Server Manager . I cannot forward port 27015-27030 as UDP. I can forward it as TCP but that's it. I get an error when trying to set for BOTH (TCP/UDP) that indicates "The Private port range is not correct".

Ports forwarded as follows. (As provided by various links on hosting Ark Server, and the ASM guide).

Router: Arris
Model: E31T2V1

TCP/UDP:
7777-7778
25147

TCP:
27015-27030 (guides indicate this should be UDP or BOTH if avail. Can only set as TCP)
27036-27037


UDP:
4380
27000-27031
27036


I can launch the server, and it says full start up 76.68 seconds. The only thing I'm seeing that might be a lead (one that I don't understand) is that in the CMD window it says

"SteamSocketOpenSource: gethostname failed()"
"gethostbyname failed ()"

I have verified that ASM did as it's supposed to and permitted access through the Windows firewall; and all ports are permitted as needed. I found this article with a similar issue, but their solution didn't seem to fix it either.

I've got 2 family members playing on Steam, and 2 from Epic Games Store. all have -crossplay launch option enabled and have all tried launching the game without battle eye but neither clients versions of the game display my server, despite ASM indicating that it's live.

I can host a non-dedicated session from in game, and I can invite my Steam family member and we have no issues playing together. But dedicated server does not appear in the servers list or in LAN for Steam client; or at all via EPIC.

open IP:Port command does not work either.

I think that just about sums up everything I've tried to do. I'm hoping someone more technically savvy than I can lend a hand. I've hosted dedicated servers from this machine before, but never had this much trouble.

EDIT: I seem to have made some progress. Using the open IP:Port command in game now brings me to a loading screen before kicking me with a "timed out/authentication" error. Likely due to not being able to set 27015-27030 to UDP?
Last edited by [KIN] AlphaObeisance; Dec 8, 2020 @ 2:43pm
< >
Showing 1-10 of 10 comments
Steam>View>Servers recognizes my server when adding it to favorites using the internal IP, but using the external IP shows not responding.

From steam I was able to connect using the "open IP:Port" from my steam client, but ran into fatal error when trying to distribute attribute points.

Not sure what I've done to make it this far. I'd reset the router to factory settings and added my ports. That DID fix my inability to add 27015-27030 as UDP port. I'm thinking I'd had a static IP i'd forgot about, and despite having removed it, didn't resolve the issue. So I decided to try a factory reset; I assume this fixed the issue.

I'm updating the maps on my wifes Epic Games Store edition of the game, once that's done I'll attempt to connect to the server on hers as well. I'll update thread accordingly.
saltia Dec 8, 2020 @ 8:01pm 
Unless you want to setup a cluster of multiple servers and do cross ark trevelling, you don't need to do any port forwardings as all your familiy members are in the same LAN of the server. All of you using internal IP would be sufficient.
Don't enter game through steam-view-servers, instead enter the game first then join game, change the filter to LAN.
What's more, you should add Servers\Server1\ShooterGame\Binaries\Win64\shootergameserver.exe to the firewall whitelist as well as ASM itself.

BTW: Your router probably doesn't support NAT loopback or you don't tweak this feature on .Then it won't allow you(within the LAN) to connect another device in the same LAN through public IP even you set all port forwadings correctly.
Last edited by saltia; Dec 8, 2020 @ 8:12pm
Originally posted by saltia:
Unless you want to setup a cluster of multiple servers and do cross ark trevelling, you don't need to do any port forwardings as all your familiy members are in the same LAN of the server. All of you using internal IP would be sufficient.
Don't enter game through steam-view-servers, instead enter the game first then join game, change the filter to LAN.
What's more, you should add Servers\Server1\ShooterGame\Binaries\Win64\shootergameserver.exe to the firewall whitelist as well as ASM itself.

BTW: Your router probably doesn't support NAT loopback or you don't tweak this feature on .Then it won't allow you(within the LAN) to connect another device in the same LAN through public IP even you set all port forwadings correctly.


Thanks for your reply!

Unfortunately I got family all over the states haha! And unfortunately half of them own Ark on EGS.

I'm not entirely certain how, but I managed to solve the issue! My father in law in Idaho was able to join with no problem. Said all he had to do was search in the unofficial servers list for my server and it finally came up.

He was able to play about half an hour before he had to go.

My wife on the other hand, is not so fortunate. Oddly enough, the server does NOT appear in the servers list when searching; but she IS able to join using the "open IP:PORT" command, but upon entering she's unable to access inventory as it opens and closes almost immediately. After about 5 minutes battleeye kicks her from the session.

I have battleye enabled on the server (father in law had it enabled on his epic client as well). So I'm thinking there's some kind of conflict with her battleye. I did find the NAT option on the router you'd mentioned but it's not something I'd modified in any way.

Turns out Wife's issue was that she needed to port forward on her windows firewall in order to join! Problem solved!

Did my best to document all my steps just in case some other poor soul ends up having these troubles lol!
saltia Dec 8, 2020 @ 9:54pm 
Originally posted by AlphaObeisance:
Originally posted by saltia:
Unless you want to setup a cluster of multiple servers and do cross ark trevelling, you don't need to do any port forwardings as all your familiy members are in the same LAN of the server. All of you using internal IP would be sufficient.
Don't enter game through steam-view-servers, instead enter the game first then join game, change the filter to LAN.
What's more, you should add Servers\Server1\ShooterGame\Binaries\Win64\shootergameserver.exe to the firewall whitelist as well as ASM itself.

BTW: Your router probably doesn't support NAT loopback or you don't tweak this feature on .Then it won't allow you(within the LAN) to connect another device in the same LAN through public IP even you set all port forwadings correctly.


Thanks for your reply!

Unfortunately I got family all over the states haha! And unfortunately half of them own Ark on EGS.

I'm not entirely certain how, but I managed to solve the issue! My father in law in Idaho was able to join with no problem. Said all he had to do was search in the unofficial servers list for my server and it finally came up.

He was able to play about half an hour before he had to go.

My wife on the other hand, is not so fortunate. Oddly enough, the server does NOT appear in the servers list when searching; but she IS able to join using the "open IP:PORT" command, but upon entering she's unable to access inventory as it opens and closes almost immediately. After about 5 minutes battleeye kicks her from the session.

I have battleye enabled on the server (father in law had it enabled on his epic client as well). So I'm thinking there's some kind of conflict with her battleye. I did find the NAT option on the router you'd mentioned but it's not something I'd modified in any way.

Tick off battleye of your server(since it is a pravite family server you don't need to find out potential cheaters). Or any EPIC client joined by open command will be kicked out in about every 10 mins.

Epic client joining by open command would not activate its battleye correctly(unless they join through server list) so that they would be treated as non-battleye users(even they do activate battleye when opening game) by the server and kicked.
Last edited by saltia; Dec 8, 2020 @ 9:55pm
Liralen Dec 8, 2020 @ 11:14pm 
Originally posted by AlphaObeisance:
Originally posted by saltia:
Unless you want to setup a cluster of multiple servers and do cross ark trevelling, you don't need to do any port forwardings as all your familiy members are in the same LAN of the server. All of you using internal IP would be sufficient.
Don't enter game through steam-view-servers, instead enter the game first then join game, change the filter to LAN.
What's more, you should add Servers\Server1\ShooterGame\Binaries\Win64\shootergameserver.exe to the firewall whitelist as well as ASM itself.

BTW: Your router probably doesn't support NAT loopback or you don't tweak this feature on .Then it won't allow you(within the LAN) to connect another device in the same LAN through public IP even you set all port forwadings correctly.


Thanks for your reply!

Unfortunately I got family all over the states haha! And unfortunately half of them own Ark on EGS.

I'm not entirely certain how, but I managed to solve the issue! My father in law in Idaho was able to join with no problem. Said all he had to do was search in the unofficial servers list for my server and it finally came up.

He was able to play about half an hour before he had to go.

My wife on the other hand, is not so fortunate. Oddly enough, the server does NOT appear in the servers list when searching; but she IS able to join using the "open IP:PORT" command, but upon entering she's unable to access inventory as it opens and closes almost immediately. After about 5 minutes battleeye kicks her from the session.

I have battleye enabled on the server (father in law had it enabled on his epic client as well). So I'm thinking there's some kind of conflict with her battleye. I did find the NAT option on the router you'd mentioned but it's not something I'd modified in any way.

My understanding of NAT loopback (aka hairpinning), which isn't great to be honest, is that it's only a problem for members of your household trying to use an external IP when your router does not support it. They could use an internal IP just fine. But then others outside of your home would not be able access your server. You can test that by changing the IP to your server's internal IP.

And yeah, avoid battleye unless you have a desire to enforce all of your players to play by official rules.

Edited Note: I bought an Arris router specifically to get rid of my ISP's provided router, researched it to ensure NAT loopback wouldn't be a problem, and it hasn't been a problem.

Last edited by Liralen; Dec 8, 2020 @ 11:24pm
Thanks ya'll! We been playing a couple hours now without issue! What a day (yea it took me all day to figure it out lol!). I do see my router has NAT options and is set to RoutedWithNAT by default?

Though my wife was finally able to find the server in the list once I disabled Battleye!
Do you have discord. if so im KillerDelta#2112.

Would be more than glad to assist.

I managed to setup 19 Maps using ASM with out an issue with port forwarding on mikrotik.and battle eye running..
Originally posted by Kalgat Gamer dude:
Do you have discord. if so im KillerDelta#2112.

Would be more than glad to assist.

I managed to setup 19 Maps using ASM with out an issue with port forwarding on mikrotik.and battle eye running..

I appreciate the offer my dude! But all is good and gravy now! I spent about two days messing around and I think it had something to do with a static IP i tried setting up some time ago for another game and had forgot about it. I did a factory reset on the router and re-applied the port forwarding, disabled battleye (family VIP server crossplay between steam/epic) and after that everything seemed to work just fine! Going on day 30 or so in game!

Really love this ASM Tool! I'm still trying to get the hang of it. My son is 10 years old and I'm trying to balance the game to challenge him but not ruin the fun for him lol! So many great features and a fantastic GUI!
The GUI has everything one needs for a setup..

The only issues i have are restart times and thats because of windows.. but honestly i looked at other options like TC Admin and open game panel and was like nope im sticking to ASM

I still want to get another 3 servers running in other parts of the county and get them clustered over the net.. next goal lol
< >
Showing 1-10 of 10 comments
Per page: 1530 50

Date Posted: Dec 8, 2020 @ 1:15pm
Posts: 10