Page tree

 

Praim ThinMan Latest – This documentation is related to "Praim ThinMan" software version 7.8.16.
For documentation on a former version of Praim ThinMan or for other software documentation, see Wiki Praim.

 

Skip to end of metadata
Go to start of metadata

Port Utilisation

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.

Ports for Active Directory

Ports for Teradici

Ports for ThinMan Secondary Server

Ports for ThinOX 8.x, 9.x, 10.0.x

Ports for ThinOX 10.1.x or greater

Ports for WES7 2.x.y or greater - WES8

Ports for WES 7 1.x.y

Ports for Windows 10 IoT - WES7 4.x.y or greater - Agile

Ports for XP Embedded



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.

Incoming Ports

Port
Type

Port
Number

Service or
Process

Description

UDP66, 67, 69, 4011VariousUsed by DHCP Relay, TFTP and PXE Service.
UDP1680ThinManSupport

Devices Browsing

TCP21VariousUsed for Teradici Thin Client firmware upgrade (FTP Server).
UDP137, 138VariousFile 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)
TCP139, 445VariousFile 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)
TCP443ThinManServer

XMLRPC from ThinClient to ThinMan Server (can be configured)

TCP1680ThinManSupportTCP Notify from Thin Client
TCP1687ThinManServerFor Remote Console Connection
TCP2809ThinManNamingFor Console and Remote Console Connection
TCP5400, 5500VNCviewerultra.exeRemote Assistance XPe
TCP20080ThinManServer

SOAP ThinMan Server Primary - Secondary (can be configured)
HTTP Server for Firmware Upgrading

TCP50000ThinManServerUsed to accept communication from Teradici Thin Clients.

Outgoing Ports

Port
Type

Port
Number

Description

UDP161, 162To make requests via SNMP Protocol
UDP427To Teradici Thin Client (P9002 and other manufacturer models) for SLP Protocol (see http://en.wikipedia.org/wiki/Service_Location_Protocol)
UDP1680, 1684For Thin Client WT, ThinOX, TwiNet, PrintOne administration
UDP1683, 11683For Thin Client XPe, WES7, TwiNetTC administration
TCP21To remote FTP Services
TCP22To SSH Port on Thin Client
TCP443To contact Praim servers on Internet for demo licenses request
TCP80To download from Praim servers on Internet the upgrades for the Device Images (see Device Images Manager Menu)
TCP389To LDAP Server (can be configured)
TCP427To Teradici Thin Client (P9002 and other manufacturer models) for SLP Protocol (see http://en.wikipedia.org/wiki/Service_Location_Protocol)
TCP443XMLRPC from ThinMan Server to Thin Client ThinOX (can be configured)
TCP987For Remote Assistance for Praim Ghibli series
TCP1680To Browse Thin Client using TCP transport
XMLRPC from ThinMan Server to Thin Client  XPe, WES7 Thin Client
TCP2121To Thin Client using FTP Passive Mode
TCP3306To MySQL Server if used as external database (can be configured)
TCP5800, 5900To Remote Assistance Thin Client ThinOX, WT, WES7
TCP20080

To make SOAP requests from/to ThinMan Server Primary - Secondary (can be configured)

TCP50xxxAre 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

Port
Type

Port

Service or
Process

Description

TCP1685, 1686ThinManSupportInterprocess Communication from/to Services
TCP2809ThinManNamingThinMan Naming Service