well, you can test by forwarding it, then disabling the forwarding.
even though you could enable forwarding only while playing the game, that port will still be open to anyone on the internet. so if there are any exploits in the network socket, well… also, as i said, some other application might be listening on that port, which might end up even worse.
so, at your own risk and use only for testing, to see if your firewall has an issue with forwarding these ports (don’t use it as a permanent solution).
also, you can use ‘netstat -an’ from command prompt. make sure there is an entry (after it connects to shift), or make sure there is nothing on that port before:
TCP 192.168.x.x:5000 220.127.116.11:443 ESTABLISHED
5000 is the port on your pc, 443 is the HTTPS (SSL) port for the server, and 54.86.x.x was it’s last known IP (which is actually amazon cloud hosting).
actually, if you use ‘netstat -abn’, it should display the executable name Launcher.exe, but the display is much more cluttered.
but honestly, in a home environment, this doesn’t seem like a likely cause of the problem.
you can check your windows firewall (or disable it for testing temporarily, if you’re using a router).
start > control panel > windows firewall > advanced settings > inbound rules.
make sure there are entries for Homeworld Remastered Collection. make sure they are ‘Enabled’. if not, dbl-click them, and enable them.
dbl-click them anyways, and go to the ‘Advanced’ tab. make sure ‘Domain’, ‘Private’, and ‘Public’ are checked. or whatever ones you want enabled, depending on what you set your network location profile to.
only other issues, are as stated, some coding in the client (maybe it didn’t pop eula, or something and is not configured correctly, no way of confirming). or some other random variables like double-NAT, which some apps do not like, or various specific router makes/models not handling specific traffic (but this is just HTTPS/SSL)… so i can’t see what the problem is.