. I forwarded port 5655 to my dedicated server as it was before but now when I am connected to the same network on the Viewer the clients all appear offline.
This might mean that the Viewer PC cannot reach/communicate with your server PC. You should check if the DNS name of server can actually resolved on the Viewer side. Or, if you use an IP address, then there should be a direct route between Viewer and Server.
I found when configuring a host to use Custom Server Security, the capitalization of the username matters. For example, logging on with username "johndoe" will fail if the username on the server is "JohnDoe".
If case-sensitivity is by design, more clarity is needed through the documentation and app dialogues to remind users.
Yes, it is by design. We will mention that in the documentation and possibly also in the interface itself. Alternatively, we will consider following the Windows scheme instead.
Unsuccessful logons should be prefixed by something more meaningful, eg "RU Server Authorization Failed"
Yes, this is a known issue. We will add a message in case of a failed logon attempt.
The license count column just shows your total available number of allowed entries in your address book. Besides, there is no such thing as unregistering a Host - you just delete the records you no longer need from your address book and that's it.