Configuring ThinPrint

364 views 0

In the ThinPrint Hub’s web console under the menu item ThinPrint, you will find the following options:

  • ThinPrint Port: Functions for configuring the integrated ThinPrint Client
  • Connection Service: Functions for using Connection Service to address the device via the ThinPrint Secure Tunnel

ThinPrint Port

The ThinPrint Port menu on the ThinPrint Hub’s web console offers the following functions for configuring the integrated ThinPrint Client:

Menu Function
TCP port TCP port, on which the ThinPrint Client listens default: 4000
checkbox Bandwidth con­trol enables client side bandwidth control
Bandwidth control (in kbit/s) • bandwidth value
• must be less than or equal to the value in the ThinPrint Engine
• if the value is higher, or the Client control on the server side has been disabled, the server value will be used
Printer timeout (in min) timeout if printing failed (canceling the printing process)
Save saves the entries
Cancel cancels the operation

Connection Service

This web console menu offers the following functions for using Connection Service to address the device via the ThinPrint Secure Tunnel:

Menu Function
checkbox Connection Ser­vice enables the ThinPrint Client’s Connection Service thread
Note: With disabling the Connection Service option and then enabling it directly you can trigger a connection from the Hub to the Connection Ser­vice. On this, see also the PowerShell cmdlet Set-TPHubThinPrintConSvc­Config.
Address the address of the server on which the Connection Service runs
TCP port TCP port, over which the ThinPrint Client connects with the Connection Service; default: 4001
Client ID the device’s identification number, for logging on to the Connection Service
Authentication key authentication key for logging on to the Connection Service
 Test Connection tests the connection to the Connection Service using the specified address
Save saves the entries
Cancel cancels the operation

Note! If the connection to the Connection Service was interrupted for more than one minute, the Hub takes five to six minutes to reconnect to the Con­nection Service automatically.

 

Previous Page
Next Page

Was this helpful?