I am running two remote servers. Every time I loose power (which unfortunately happens too frequently), one of the servers refuses to reconnect for remote access. I am not sure why, but one will always connect via the specified 32400 port. The other server has to be manually configured. The only way I can get the new port number is by looking at the server mapping of the connected server. The last public port was 24094.
Private 192.168.1.24:32400 <-- Public 174.45.152.239:24094
I have to always manually specify the public port and the only way I can figure out how to get the port number is through the server that is connecting.
I have two servers: one for ‘production’ (runs all the time) and a ‘development’ server.
In situations such as yours (which mine is like as well), manual port mapping was the only stable, predictable solution.
I did ‘manually specify port’ and set it 32400 (Production), complete with manual port-forwarding rule through the modem & its firewall. I next added 32401 and repeated the process.
I no longer have conflicts or have to ‘dig’ when either goes though a reboot or power cycle.
For my machines:
PublicIP:32401 ----> modem/firewall ------> (redirect to LAN IP of development server)
PublicIP:32400 ----> modem/firewall ------> (redirect to LAN IP of production server)
This configuration lets everything in the house default to 32400 automatically. Clients which search (e.g. Roku Plex) find both and keep both properly identified.
