In order to be able to work properly, ThinMan Suite requires some networking configurations intended to assure communication between ThinMan services, ThinMan console, ThinMan Update-License-Documentation Servers and managed clients.
Thus, we may split these requirements into three different groups based on ThinMan communication purpose:
- Allowing ThinMan to communicate with its managed devices (ThinMan connections to/from end points);
- Allowing ThinMan to communicate with Praim ThinMan Update-License Servers (ThinMan Connections to Praim Server);
- Allowing ThinMan Console (both Local and Remote) to access web contents linked in Console screen (ThinMan Console Connections).
¶ ThinMan Connections To/From End Points
ThinMan connections to/from end points include all communications established between ThinMan server and its managed devices. These communications may be achieved through connection initiated both from ThinMan server to end points and vice versa by connections rose from end points to ThinMan listening services. Furthermore they can involve TCD and UDP protocol connections.
¶ Port Utilisation
The ports involved on both side, ThinMan server and clients side, may change on basis of following factors:
- thin client type and related operating system version;
- ThinMan features enabled (e.g. ThinMan Login requires LDP protocol);
- ThinMan Architecture implemented (See ThinMan High Availability Software Architecture );
- ThinMan Operating Mode chosen (See ThinMan Operation Modes).
Due this, the networking configurations requirements may be very different depending on each specific installation.
For this reason refer to Port Utilisation page in order to configure your networking infrastructure to allow
communications through your local or geographical network towards ports and destinations (ThinMan server or end points) as listed in detail on basis of the specific hardware, features and architecture.
¶ ThinMan Connections Toward Praim Servers
ThinMan connections to Praim's servers are established between ThinMan Server and Praim ThinMan Update and Licensing Servers. Outbound connection to Praim server is necessary to activate the Platinum Trial License and to perform the ThinMan Online registration.
Furthermore, with a predefined frequency, ThinMan service enquires the Praim Update Servers in order to check if a ThinMan Server update is available. In the event an update is detected and recognized compatible with the ThinMan Server version actually installed, the update will be transferred on board the ThinMan Server. It remains in charge of ThinMan Administrator to run the ThinMan server software update.
Last, periodically a group of statistics are collected and transferred to Praim servers in order to perform a device assessment in term of licence, firmware and software versions installed, assuring the most prompt and adequate update service and allow and efficient improvement of Praim products.
IMPORTANT NOTE
On Praim server only technical data are collected, none customer data (username, password) or network and server data are collected in stats. The exported stats are the same generated and exported by the ThinMan menu Info → Send Information or Info → Export Information command.
In order to allow the above described communication the following networking configuration are required for outgoing connections:
| Port Type | Port Number | Destination | Description |
|---|---|---|---|
| TCP | 80 | packages.praim.com |
ThinMan software update check and deployment |
| TCP | 443 | packages.praim.com |
ThinMan software update check and deployment |
| TCP | 443 | stats.praim.com |
ThinMan configuration statistics collection |
¶ ThinMan Console Connections
Both Local and Remote ThinMan Console show inside their screens some link referring straight Praim servers for online documentation retrieving and license product registration.
For this reason is required to allow connection initiated from systems running local and remote console, towards following Praim servers:
| Port Type | Port Number | Destination | Description |
|---|---|---|---|
| TCP | 80 | www.praim.com |
Access to online documentation |
| TCP | 443 | www.praim.com |
Access to online documentation |
| TCP | 80 | my.cloud.praim.com |
Access to online documentation and registration |
| TCP | 443 | my.cloud.praim.com |
Access to online documentation and registration |
| TCP | 80 | wiki.praim.com |
Access to online documentation |
| TCP | 443 | wiki.praim.com |
Access to online documentation |
| TCP | 80 | link.praim.com |
Access to online documentation and registration |
| TCP | 443 | link.praim.com |
Access to online documentation and registration |
Furthermore the ThinMan Remote Console have to establish a connection towards ThinMan Server. This connection results as "incoming" from the point of view of the ThinMan server.
| Port Type | Port Number | Destination | Description |
|---|---|---|---|
| TCP | 1687 | ThinMan Server | Remote Console Connection to ThinMan Server |
¶ Firewall and Router Configuration
As described above, ThinMan suite (i.e. ThinMan server and ThinMan console) requires to iniziate some outbound connection from your network towards Praim update and registration servers.
If your firewall blocks these activities, the ThinMan could not give you information about the availability of new components.
For this reason, pay attention to configure your firewall in order to allow outgoing connections accordingly to the ones listed above.
For more details about outbound connections refer to paragraphs ThinMan Console Connections and ThinMan Connections Toward Praim Servers.
Even in a multi-branch company involving Praim end points placed in distinct location, routers interconnecting branches have to be configured in order to route communications between ThinMan Server and peripheral end points accordingly with specification quoted on paragraph ThinMan Connections To/From End Points.
¶ When a Proxy Server is present in your network
When in a network infrastructure is present a Proxy server to manage outgoing connections, you have to configure ThinMan in order it forwards outbound 80 and 443 port traffic toward the proxy server instead to the network default gateway.
Protocols and destination servers you have to enable on Proxy server are listed in detail on paragraph ThinMan Console Connections and ThinMan Connections Toward Praim Servers.
Through the proxy server configuration box, you can be aware ThinMan suite (ThinMan server, Local and Remote console) about your proxy server address and the port where it is listening to.
The proxy listening ports is, as default, set to 3128 value; anyway it is changeable.
Furthermore, if your proxy requires authentication credentials. Here you can insert a username and password in order to authenticate ThinMan by the proxy server.
The above Proxy server setting box is reachable in two different ways. Read below.
¶ Setting the Proxy from the Info Menu
The first way is to access through the Info Menu.
¶ Setting the Proxy when ThinMan cannot connect to the Praim Server
The proxy can also be configured whenever ThinMan cannot connect to the Praim Server. For example, if you try to access to the Menu Info -> ThinMan Online Registration and there is no connection. The window below will appear.
By clicking on "Set Proxy Server" you will access to the Proxy Server setting window.
Enter the required parameters and confirm by clicking on the "OK" button. The Proxy server configuration windows will close.
In order to check the effectiveness of the proxy server configuration just set, perform or repeat the ThinMan Online Registration, clicking on "OK" button.