ThinPrint Engine • Getting Started
ThinPrint Engine Components
- High Availability and Load Balancing
- Printer Self Service
  - Using the Self Service
  - Windows Registry entries of ThinPrint Self Service
- ThinPrint Group Policies
- Connection Service aka Secure Tunnel
- ThinPrint Tracking
ThinPrint Clients
- ThinPrint Client Windows
- ThinPrint Client for VMware Horizon
- ThinPrint Client Mac
- ThinPrint Client Linux
- ThinPrint Client for HP Printers
ThinPrint Management Services
- Management Services • Overview
- Management Services • Installation
- Management Services • Practice
- Management Services • Cmdlets • Part 1
- Management Services • Cmdlets • Part 2
- Management Services • ScriptRunner
- Management Services • Appendix
Personal Printing
- Personal Printing • Introduction
  - About Personal Printing
  - How it works
- Installing Personal Printing
- Configuring Personal Printing server
- Personal Printing Release Station
- User self registration & JobViewer
- Smartphone authentication
- Personal Printing clients on network printers
- Options and supplemental information
Licensing, Certificates and Diagnostics
- ThinPrint licensing
- License server
- License server's PowerShell module
- Enterprise Portal
- Creating and installing certificates
- Ports
  - TCP ports used by ThinPrint
- ThinPrint Diagnostic Utility
ThinPrint Hub
- Intended use and safety information
  - Intended use, conformities and Dual-Use Regulation
  - Safety information
- Quickstart with ThinPrint Hub
- Hub web console
- ThinPrint Hub Finder
- Updating the Hub
  - Downloading and installing a firmware update
  - Firmware versions
- Hub PowerShell module
- Hub cmdlets • Part 1
- Hub cmdlets • Part 2
- Hub cmdlets • Part 3
- Hub cmdlets • Part 4
- Managing certificates on the Hub
- Logging and reset
  - Logging
  - Factory reset
ThinPrint Hub Remote Management
- Cloud management
  - Managing Hubs in the cloud
  - Connecting printers to the cloud
- On-premises remote management
FAQs
Troubleshooting
- Mapping issues
  - Duplicate Printers Map
- Encryption and certificate issues
  - Troubleshooting – Encryption & Certificates
- Fonts and formatting issues
  - Solving font problems
- Management Services issues
  - Troubleshooting of Management Services
- ThinPrint Client issues
  - Troubleshooting of ThinPrint Client Mac
  - Troubleshooting of HP and Xerox printers
- ThinPrint Hub issues
  - ThinPrint Hub troubleshooting

TCP ports used by ThinPrint

ThinPrint Engine on a print server

ThinPrint Engine on a remote desktop session host

ThinPrint License Server

ThinPrint TCP/IP Client

ThinPrint Connection Service

ThinPrint Tracking Service

Personal Printing

This guide gives you an overview of all TCP ports used by ThinPrint on-premise products.

ThinPrint Engine on a print server

Be sure that the TCP ports for communication and printing via TCP/IP are not being blocked by another program or by a server-side or client-side firewall. Default ports are:

Outbound:

4000 for print jobs
135 and 4005 for license requests

Inbound:

4100 for the AutoConnect high availability service
Dynamic RPC ports (at least for the TPPrintSvc.exe)

ThinPrint Engine on a remote desktop session host

Be sure that the TCP ports for communication and printing via TCP/IP are not being blocked by another program or by a server-side or client-side firewall.

Outbound:

135, 4004 (optional) and 4005 for license requests
4000 for printing
4100 to the ThinPrint HA service on print servers (RPC)

ThinPrint License Server

Be sure that the TCP ports for communication and printing via TCP/IP are not being blocked by another program or by a server-side or client-side firewall.

Inbound:

135 for RPC calls from other ThinPrint components
4004 (optional) for access to the web console of the ThinPrint License Server
4005 for license requests of ThinPrint components

ThinPrint TCP/IP Client

Be sure that the TCP ports for communication and printing via TCP/IP are not being blocked by another program or by a server-side or client-side firewall.

Inbound:

4000 for print jobs from the ThinPrint Engine

Outbound:

4001 in case you are using the ThinPrint Connection Service

ThinPrint Connection Service

Be sure that the TCP ports for communication and printing via TCP/IP are not being blocked by another program or by a server-side or client-side firewall.

Eingehend:

4000 for print jobs from a ThinPrint Engine
4001 for requests from a ThinPrint Client
4012 - 4014 (MultiCast) for traffic between several connection service hosts in a HA configuration

ThinPrint Tracking Service

Be sure that the TCP ports for communication and printing via TCP/IP are not being blocked by another program or by a server-side or client-side firewall.

Inbound on the SQL Server:

1434 (UDP)
1433 (TCP)

Personal Printing

Be sure that the TCP ports for communication and printing via TCP/IP are not being blocked by another program or by a server-side or client-side firewall.

Inbound:

https 443 for authentication method