ASAManager is great and ASM also sees the server in the list! Still can't connect though.
![](https://asadedicatedmanager.eu/wp-content/uploads/user_registration_uploads/profile-pictures/output_3365279620_0_out-scaled.jpg)
Quote from Chaple on 04/07/2024, 10:12 PMThis is my first time posting in one of these threads anywhere, I've always been able to get my game servers running on my own with little to no Google search, but this one has completely stumped me. Any help even simple things are welcome. With that said, I'll go over the progressive steps in getting my server visible and what the home network looks like.
ASA Server Manager creates a server and it's visible in the ASA Server list. Small victory there. But the issue is I can't connect to it even through LAN direct open server.ip.here:7777.
When I go into Steam and browse for my servers, I am unable to find it running as LAN or even directly through favorites. I get an error for both, LAN says "There are no servers running on your local network." Even though I can see it in the Ark Survival Ascended unofficial list. When I try to connect through Steam servers using the external IP I get "Did not find any servers at that address." using port 7777 to connect, when I switch the server setting to MultiHome and then try the above using local IP for LAN I get the same messages.
Now when I go into the game client in the unofficial servers list, I see the server, but it fails to connect, wire shark says the packets are unreachable. When I open the console and use open external.server.address:7777 it times out, when I use local.server.address:7777 it says invalid password. I'm missing something here but for the life of me, I can't find it right now.
Any help would be appreciated.
Alright, let's start with the hardware:
I have a gateway that can't run bridge mode due to home automation equipment because the equipment runs through the gateway Wi-Fi and LAN ports.
I have a router that supplies a strong signal throughout the house.
I have a hardware firewall and switch that blocks traffic to select and guest devices.
I am running Windows 11 with Antivirus, Software Firewall, and Windows Firewall enabled.
I have properly routed traffic from the gateway for incoming and outgoing transit to and from the router.
I have properly opened ports for Steam games in the router correctly, as all other Steam game servers are working
(not ASA though)
I have added exception rules for my Antivirus.
I have added exception rules for my software firewall and Windows firewall.
Troubleshooting
# (individually and combined with the following)
I tested the gateway in DMZ and also bridge mode, and it made no difference.
I tested with all firewalls and antivirus shields down, made no difference.
I tested with the router in DMZ mode, made no difference.
I can see the ports listed in the listening ports for ArkAscendedServer.exe, but all HTTP port checkers fail to confirm open ports with the programs running.
Thank all!
This is my first time posting in one of these threads anywhere, I've always been able to get my game servers running on my own with little to no Google search, but this one has completely stumped me. Any help even simple things are welcome. With that said, I'll go over the progressive steps in getting my server visible and what the home network looks like.
ASA Server Manager creates a server and it's visible in the ASA Server list. Small victory there. But the issue is I can't connect to it even through LAN direct open server.ip.here:7777.
When I go into Steam and browse for my servers, I am unable to find it running as LAN or even directly through favorites. I get an error for both, LAN says "There are no servers running on your local network." Even though I can see it in the Ark Survival Ascended unofficial list. When I try to connect through Steam servers using the external IP I get "Did not find any servers at that address." using port 7777 to connect, when I switch the server setting to MultiHome and then try the above using local IP for LAN I get the same messages.
Now when I go into the game client in the unofficial servers list, I see the server, but it fails to connect, wire shark says the packets are unreachable. When I open the console and use open external.server.address:7777 it times out, when I use local.server.address:7777 it says invalid password. I'm missing something here but for the life of me, I can't find it right now.
Any help would be appreciated.
Alright, let's start with the hardware:
I have a gateway that can't run bridge mode due to home automation equipment because the equipment runs through the gateway Wi-Fi and LAN ports.
I have a router that supplies a strong signal throughout the house.
I have a hardware firewall and switch that blocks traffic to select and guest devices.
I am running Windows 11 with Antivirus, Software Firewall, and Windows Firewall enabled.
I have properly routed traffic from the gateway for incoming and outgoing transit to and from the router.
I have properly opened ports for Steam games in the router correctly, as all other Steam game servers are working
(not ASA though)
I have added exception rules for my Antivirus.
I have added exception rules for my software firewall and Windows firewall.
Troubleshooting
# (individually and combined with the following)
I tested the gateway in DMZ and also bridge mode, and it made no difference.
I tested with all firewalls and antivirus shields down, made no difference.
I tested with the router in DMZ mode, made no difference.
I can see the ports listed in the listening ports for ArkAscendedServer.exe, but all HTTP port checkers fail to confirm open ports with the programs running.
Thank all!
![](https://asadedicatedmanager.eu/wp-content/uploads/user_registration_uploads/profile-pictures/output_3365279620_0_out-scaled.jpg)
Quote from Chaple on 04/08/2024, 9:20 PMOK I've solved it. Due to the complexity of my network, I failed to point some of the traffic routes correctly. What I did was started at the access point and worked my way in to the server. Each step I verified my settings between the nodes static routes, port forwarding and security options. Once I had a complete path, I set up NAT passthrough with port forwarding through each of the firewalls. I think what it did was the network mapping, as I changed a few settings there that didn't make sense.
Cheers!
Chap
OK I've solved it. Due to the complexity of my network, I failed to point some of the traffic routes correctly. What I did was started at the access point and worked my way in to the server. Each step I verified my settings between the nodes static routes, port forwarding and security options. Once I had a complete path, I set up NAT passthrough with port forwarding through each of the firewalls. I think what it did was the network mapping, as I changed a few settings there that didn't make sense.
Cheers!
Chap