that port is nowhere really fixed to 32400 - not if you look into remote PMSs.
that port was at one point added to the id to make sure to pick the correct PMS, even if it located far away… and potentially has a brother in the remote subnet with the same exact public ip.
that port is nowhere really fixed to 32400 - not if you look into remote PMSs.
that port was at one point added to the id to make sure to pick the correct PMS, even if it located far away… and potentially has a brother in the remote subnet with the same exact public ip.
It is easy.
If PMS is local the port is fixed to 32400 and if the server is not local and thus maybe only accessible by a different (public) port the admin has to specify it nonetheless.
Whatsoever, it’s not that important. I just don’t like incompatibilities and thus reported it