The port used by ThinMan Server are explained in this chapter Networking Configuration Requirements.
In some cases when ThinMan is installing or during the services starting the ThinMan processes could find a busy port. In particular there is a verification on port used by HTTPS protocol and on port used for HTTP protocol (default values are 443 and 20080: remind that this port can be changed during the installation or using the ThinMan Server Menu).
When the ports are occupied by other processes ThinMan will show this dialog error.
To analyze the problem you have to identify which processes are using the port.
To do that you can use the "Resource Monitor" software. To run it click on "Resource Monitor" button on the error dialog. You can also start it using the WIN + R hotkey and write "resmon" in the text field.
Select the "Network" tab then click on "Listening port" to show the list of processes and ports. Find the port showed in the error dialog (e.g. 443) and look at the process that occupy the port.
Typical processes that use the 443 ports are:
Microsoft IIS Server (the name of the process could be in this case "System")
Skype (the name of the process could be in this case "Skype.exe").
Possible solutions are:
This solution is quite simple to act but it has some side effects. Read the How to Setup ThinMan Address on Thin Client chapter for more information. Praim suggest to use other solutions.
Depending on the process search for related documentation to change the ports used by the process.
Praim Suggestions
If the port cannot be changed or it is difficult to change it, Praim suggests to install ThinMan software on another server.
In the case of Skype process you can use the menu "Tools" → "Connection options..." and disable the flag oon the specific parameter (see below).
Click on "Save" and restart Skype.
If processes cannot be deleted or ports cannot be changed Praim suggests to install ThinMan on another server/workstation.