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

Networking Configuration Requirements


In this page you are going to find...


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 this requirements into three different groups on basis of ThinMan communication purpose:

  1. allowing ThinMan to communicate with its managed devices (ThinMan connections to/from end points);
  2. allowing ThinMan to communicate with Praim ThinMan Update-License Servers (ThinMan Connections to Praim Server);
  3. 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.

The ports involved on both side, ThinMan server and clients side, may change on basis of following factors:

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's 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

TCP80packages.praim.comThinMan software update check and deployment
TCP443packages.praim.comThinMan software update check and deployment
TCP443

stats.praim.com

ThinMan configuration statistics collection

ThinMan Console Connections

Both Local and Remote ThinMan Console show inside its 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

TCP80www.praim.comAccess to online documentation
TCP443www.praim.comAccess to online documentation
TCP80

my.cloud.praim.com

Access to online documentation and registration
TCP443

my.cloud.praim.com

Access to online documentation and registration
TCP80wiki.praim.comAccess to online documentation
TCP443wiki.praim.comAccess to online documentation
TCP80link.praim.comAccess to online documentation and registration
TCP443link.praim.comAccess 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

TCP1687ThinMan ServerRemote 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 you network towards Praim update and registration servers.

If your firewall  block 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 Toward/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 forward 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 way by the ThinMan Local Console.


The first way is pass trough Trial license activation.

When you have to activate the Platinum Trial license and a proxy server is already present in your network, click on "Activate Platinum Trial" button on "Welcome to ThinMan" box.


The "Activate ThinMan Platinum Trial" windows opens.

Flagging "Use a proxy server" option check box, the "Set Proxy" button will be enabled.

Clicking on it you will access the Proxy Server setting windows. Proxy server settings defined in this windows will remain effective even the Platinum Trial license activation procedure has ended .


When you need to configure ThinMan referring to a Proxy server in any other time, after Trial license has been activated, you can achieve the Proxy Server configuration windows through the ThinMan menu Info → ThinMan Online Registration

Flagging "Use a proxy server" option check box, the "Set Proxy" button will be enabled.

Clicking on it you will access the Proxy Server setting windows. Enter the settings and confirm them clicking on the "OK" button. The Proxy server configuration windows will close.

In order to check the effectiveness of proxy server configuration just set, perform or repeat the ThinMan Online Registration, clicking on "OK" button.

When the registration ends successfully without any error message, the Proxy settings are correct.