Port Forwarding

[Mikie]

My wife & I haven't played in about 6 months. We host our own server using "DedicatedServerLauncher 1.0.38". Today I launched the server and waited for it to update, but when I hit "Test Port Accessibility" I got the unsuccessful reply. Now I'm on Windows 10 and Windows Firewall has the ports still open for me (7777,7778,27015). I also logged into my router and it still has the port forwarding enabled as well. Now I tried an online "port checker" and it also shows closed for 7777. So I feel like something is amiss on my end, but if Windows Defender & my Router are clear, we should be good to go right? Any thoughts on a fix? I run MalwareBytes, but only at the "free" level so it shouldn't be blocking anything real-time.

[Solomon Hawk]

I've been hitting a dead end with exactly the same issue on the ports.
For the longest time I've been wondering if I'm the only one experiencing this.
It ran fine before when I was still on a DSL and was even able to see it on the server list.
But since then, I've switched to satellite internet (bad move anyway), but I noticed the Dedicated Server Launcher is a new version from what I had used previously.
So this has me wondering what's changed in the dedicated launcher that's mucked up port access.
I have the server on a dedicated machine apart from the one which I use for the game.

On a side note, it isn't necessary to run more than one AV software since Defender is comprehensive, made to order for windows 10.

[hades]

Have you checked the server machines local IP (ipconfig etc) to make sure it is still the same as the IP you port forwarded in your routers settings?

Sometimes your router will refresh the local IP's of the machines connected to it and you need to edit your routers settings again.

[Hanalyd]

Make sure to give your "server" a static IP address.
And make sure you reserve that IP address to your servers MAC address so only your server gets that IP address.
Or else there is a high chance if will get an alternate IP address.

Also make sure your ISP gave you an IPv4 instead of the new IPv6.
Since IPv6 doesn't support manual port forwarding.
Make sure your router has UPnP on also.

[Solomon Hawk]

FQYPW님이 먼저 게시:

Make sure to give your "server" a static IP address.
And make sure you reserve that IP address to your servers MAC address so only your server gets that IP address.
Or else there is a high chance if will get an alternate IP address.

Also make sure your ISP gave you an IPv4 instead of the new IPv6.
Since IPv6 doesn't support manual port forwarding.
Make sure your router has UPnP on also.

Now that you mention it, I recall now that my previous internet (DSL) had a static IP.
What I have to learn now is how to properly set up port forwarding.

[Sterling]

I used to run a server with the dedicated server tool, until one day I started getting an error where the tool couldn't reach my ports or some other stuff involving that and some red lights. Turned out my ISP reversed my port forwarding because "my internet pack didn't cover that feature". Maybe yours is pulling the same ♥♥♥♥♥♥♥♥.

[Solomon Hawk]

For me, a Satellite ISP is very problematic since it doesn't play well with online gaming.
So, I need to get creative in setting up a home network that my two rigs can communicate via switch (or something). I'm going to run into some problems because the two rigs are using different ISPs. The server is on the satellite network and the other (this one) is hooked up to wi-fi via different ISP to eliminate the latency.

[Mikie]

Mine was a dynamic IP issue. I should have even seen it in the stupid server launcher, it shows my network IP, but it didn't update the multihome/IP boxes. I changed my last two digits from .15 to .28 as shown in the server launcher, now I can join just fine. Ridiculous nonsense from Windows 10 or my router or whatever. Anywho I would launch the server launcher and ensure the IP Shown in the network config box matches the one in the field below it. Easy wins, thanks for the helps everyone!

[Solomon Hawk]

I gotta try that.