ThinMan uses specific network ports to communicate with remote devices. When remote devices are behind either a firewall or a router, it may be necessary to configure those ports for ThinMan to get access to the remote devices. The following table describes the ports used by ThinMan (Incoming Ports are those listened by ThinMan software, Outgoing Ports are those connected on remote devices from ThinMan server).
Ports may vary depending also from other services such as the use of Remote Console, use of ThinMan Secondary Server, use of MySQL Server.
In the links below, you can find information specific to a particular kind of device, software or service that you are using.
There is also a generic table that collects all the ports for all types of devices and services (not recommended because it contains all the variety of devices and communication ports).
The ports must be open on the operating system firewall or on the network firewall or on both of them if both are present.
Specific Port Utilisation
Select the device operating system and version, or the ThinMan Feature you are currently using, to view which incoming and outgoing ports are used from the ThinMan perspective.
Convention: Incoming and Outgoing Port Definition
In the following dissertation they assuming the following mean for "Incoming" and Outgoing" connection port:
Incoming Ports: ThinMan <---- Devices
Outgoing Ports: ThinMan ----> Devices
Select your client operating system or software from this list.
Generic Port Utilisation
ALL PORTS SUMMARY
The table below shows all the ports needed by ThinMan to manage all the Praim products; it is a summary that gives a comprehensive view of used ports. Refer to the links above for the specific ports related to a single product.
|UDP||66, 67, 69, 4011||Various||Used by DHCP Relay, TFTP and PXE Service.|
|TCP||21||Various||Used for Teradici Thin Client firmware upgrade (FTP Server).|
|UDP||137, 138||Various||File sharing for ThinMan Repository (needed for Contextual Menu - Device Update - Capture Device Image and Apply Device Image for Windows Embedded, see more at https://technet.microsoft.com/en-us/library/cc731402.aspx)|
|TCP||139, 445||Various||File sharing for ThinMan Repository (needed for Contextual Menu - Device Update - Capture Device Image and Apply Device Image for Windows Embedded, see more at https://technet.microsoft.com/en-us/library/cc731402.aspx)|
XMLRPC from ThinClient to ThinMan Server (can be configured)
|TCP||1680||ThinManSupport||TCP Notify from Thin Client|
|TCP||1687||ThinManServer||For Remote Console Connection|
|TCP||2809||ThinManNaming||For Console and Remote Console Connection|
|TCP||5400, 5500||VNCviewerultra.exe||Remote Assistance XPe|
SOAP ThinMan Server Primary - Secondary (can be configured)
|TCP||50000||ThinManServer||Used to accept communication from Teradici Thin Clients.|
|UDP||161, 162||To make requests via SNMP Protocol|
|UDP||427||To Teradici Thin Client (P9002 and other manufacturer models) for SLP Protocol (see http://en.wikipedia.org/wiki/Service_Location_Protocol)|
|UDP||1680, 1684||For Thin Client WT, ThinOX, TwiNet, PrintOne administration|
|UDP||1683, 11683||For Thin Client XPe, WES7, TwiNetTC administration|
|TCP||21||To remote FTP Services|
|TCP||22||To SSH Port on Thin Client|
|TCP||443||To contact Praim servers on Internet for demo licenses request|
|TCP||80||To download from Praim servers on Internet the upgrades for the Device Images (see Device Images Manager Menu)|
|TCP||389||To LDAP Server (can be configured)|
|TCP||427||To Teradici Thin Client (P9002 and other manufacturer models) for SLP Protocol (see http://en.wikipedia.org/wiki/Service_Location_Protocol)|
|TCP||443||XMLRPC from ThinMan Server to Thin Client ThinOX (can be configured)|
|TCP||987||For Remote Assistance for Praim Ghibli series|
|TCP||1680||To Browse Thin Client using TCP transport|
XMLRPC from ThinMan Server to Thin Client XPe, WES7 Thin Client
|TCP||2121||To Thin Client using FTP Passive Mode|
|TCP||3306||To MySQL Server if used as external database (can be configured)|
|TCP||5800, 5900||To Remote Assistance Thin Client ThinOX, WT, WES7|
To make SOAP requests from/to ThinMan Server Primary - Secondary (can be configured)
|TCP||50xxx||Are dynamic ports that can be used by the thin client for FTP transfer. You can use FTP Passive mode to avoid this ports from being used.|
Interprocess Local Ports
|TCP||1685, 1686||ThinManSupport||Interprocess Communication from/to Services|
|TCP||2809||ThinManNaming||ThinMan Naming Service|