Beruflich Dokumente
Kultur Dokumente
Manual
ThinPrint GmbH
Alt-Moabit 91 a
10559 Berlin
Germany / Alemania
Cortado, Inc.
7600 Grandview Avenue
Suite 200
Denver, Colorado 80002
USA / EEUU
© Copyright
This document is the intellectual property of ThinPrint GmbH. This document may be copied in whole or
in part, provided this Copyright notice is included in every copy.
Safety warning
Please note the safety warnings in the technical documentation from your hardware vendor and from the
manufacturer of each device and component.
Before beginning installation, we recommend closing all windows and applications and deactivating any
virus scanner.
2 Manual
Contents
Introduction ................................................................................................................ 4
Licensing ....................................................................................................................... 7
Installation .................................................................................................................. 7
Workstation ................................................................................................................. 13
Example ................................................................................................................. 22
Appendix .................................................................................................................... 24
Customer service and technical support .......................................................................... 24
Registry keys of ThinPrint Client (Service) Windows for Connection Service .................... 25
Registry keys of ThinPrint Engine for Connection Service Ports ...................................... 26
© ThinPrint GmbH 2017
Troubleshooting ........................................................................................................... 27
Manual 3
Introduction
Introduction
In contrast to the usual communication direction, ThinPrint Connection Service
builds a secure print tunnel from a ThinPrint Client in any branch office to the central
ThinPrint print system in the data center – the ThinPrint Secure Tunnel.
This clever design has an important advantage in that the central ThinPrint Engine
acting as a print server doesn’t need to know the IP addresses of the network printers
located in the branch offices. In most branch offices, masked networks are used and
a VPN tunnel is necessary to reach printers. With ThinPrint, this is not necessary as
the ThinPrint Secure Tunnel takes on this task, specifically for printing. Print jobs are
delivered to branch offices via this tunnel and then distributed to network printers via
the ThinPrint Client. A direct connection from the central ThinPrint Engine to the
printers is not necessary. In addition, print data can be securely transmitted thanks
to SSL encryption, an important feature as print data contains information just as
sensitive as on printed documents.
The easiest option to roll out the ThinPrint Client with Connection Service is with
ThinPrint Hub, a small, yet high-performance print hardware device from ThinPrint
upon which the ThinPrint Client is preinstalled. The ThinPrint Hub can be centrally
configured. Once sent to branch office, it needs only to be connected to a power sup-
ply and a network cable thanks to its plug-&-play design. There is no limit to the num-
ber of network printers that can be connected to the ThinPrint Hub. Additionally, four
USB printers can be connected and effectively turned into network printers.
Furthermore the Connection Service is the perfect DMZ component for printing.
TCP ports need only be opened towards the Connection Service (Illus. 2), and no
data is stored or spooled locally.
The example below illustrates a test installation of the Connection Service
(Page 11). Once you are convinced of the software's functionality, the installation can
be adapted to your requirements.
into the Windows print process so that the data is rendered on the client machine
with the original printer driver.
Illus. 1
Illus. 1 ThinPrint Engine sends print jobs to ThinPrint Clients (arrows show print data
direction)
Rather than having to install ThinPrint Client on every end device in a remote office,
it suffices to install it on a local print server or a gateway appliance (Illus. 2). The
ThinPrint Client installed there receives all print data, decompresses and decrypts it 1
and then distributes it conventionally through the office network. Here again, NAT
poses no problem as the Connection Service resolves any NAT related issues: The
ThinPrint Client connects to the Connection Service, therefore establishing a connec-
tion through which print jobs can be sent despite NAT.
This scenario can be used beyond just Windows environments. All required print-
ers are installed in V-Layer mode on a central print server. With these printers, it is
possible to print in any Unix, SAP, AS/400 or iSeries system. The ThinPrint Engine
installed on the central print server compresses and encrypts the print data and
sends it over controlled bandwidth to the ThinPrint Client.
In addition, the printers, including Connection Service Ports and drivers can be
created on the central print server, using the Management Center2 or Management
Services3.
© ThinPrint GmbH 2017
2 http://download.cortado.com/docu/ThinPrint/MC/en/2.2/
3 http://download.cortado.com/docu/ThinPrint/Tpms/en/1.0/
Illus. 2
Illus. 2 ThinPrint Engine sends print jobs using Connection Services (arrows show
directions of TCP communication)
Driver Free Printing requires that all participating computers (application servers,
central and local print servers) have Windows as operating system.
Only on the client side can other operating systems be used: for print servers, print
server devices, or appliances with non-Windows operating systems, V-Layer can be
avoided. All necessary native printer drivers are installed on the central print server.
Driver Free Printing and V-Layer can be used simultaneously: mixed environments are
therefore not a problem (see also Page 13).
Examples of print server devices and appliances that are suitable for use as Thin-
Print.
Connection Service is supported by ThinPrint Gateway TPG-25/65 and the Spool
Server ISD300/4x0 by SEH as well as the ThinPrint Hub (see also Page 29).
© ThinPrint GmbH 2017
Technical requirements
Licensing
Connection Service installation routines are available for the following operating sys-
tems:
The server can be a member of a domain. However, domain membership is not advis-
able for operation in the DMZ (Illus. 2).
Installation
© ThinPrint GmbH 2017
If you're installing an update, refer to the section Updating the Connection Service
(Page 24). For a new installation, proceed as follows.
Illus. 3
Illus. 4
Illus. 5
© ThinPrint GmbH 2017
5. Read and accept the license agreement, and click on NEXT (Illus. 6).
Illus. 6
Illus. 7
7. Select the installation path with CHANGE, and then confirm with NEXT (Illus. 8).
Illus. 8
Illus. 9
Illus. 10
© ThinPrint GmbH 2017
Sample configuration
This example shows how to configure an application server and a central print server
for printing with Connection Service in Windows. On the client side, the example
describes a workstation running Windows (a local print server could be used instead);
information for other operating systems and devices is found in the ThinPrint Client
Linux and ThinPrint Client Mac user manuals as well as in the documents SEH TPG
as a Client Gateway and SEH ISD as a Client Gateway (see Page 29).
The components required for this example (Illus. 11) are:
IP address
Installed on ... Component
(computer name)
Illus. 11
Basic installation
Application server – Provide an application server; e.g., a Citrix XenApp server or a Microsoft
Remote Desktop Session host (or terminal server).
ThinPrint server – Install ThinPrint Engine on a central print server. Please consult the ThinPrint
Engine on print servers manual (Page 29).
Workstation – Install a ThinPrint Client on a Windows workstation (or on a local Windows print
server). See the appropriate manual ThinPrint Client Windows (Page 29).
License Server – Install ThinPrint License Server on any Windows server. Enable at least one user
for ThinPrint. See the appropriate manual License Server (Page 29).
© ThinPrint GmbH 2017
Basic configuration
Illus. 12
Workstation
On the workstations4 you can use Windows or a non-Windows operation system. The
© ThinPrint GmbH 2017
only requirement is that the ThinPrint Client to be installed supports the Connection
Service; the following are appropriate:
• all print server devices and appliances with embedded ThinPrint Client
If you want to use Driver Free Printing to send print data from the central print server
to the workstations, you must use Windows machines for all participating computers
– application servers, ThinPrint Servers, workstations. If only the application servers
and the central print server have a Windows operating system, then you can use
V-Layer (see Page 6).
The following shows an example of how a Windows computer can be configured
with the ThinPrint Client Service Windows as local print server. For information on
Linux or Mac, refer to the ThinPrint Client Linux or ThinPrint Client Mac manual; for
print server devices and appliances see the SEH TPG120 as a ThinPrint Client Gate-
way and SEH ISD400 as a ThinPrint Client Gateway documentation (Page 29.
Creating printers – Create two printers (printer objects) on the workstation for:
• the network printer HP Color LaserJet 3600 (Illus. 13)
• the network printer Lexmark T644 (Illus. 13)
ThinPrint Client Install ThinPrint Client as described in the ThinPrint Client Windows manual
Service Windows (Page 29).
– Find the printer IDs for the HP Color LaserJet 3600 and the Lexmark T644
under ASSIGNMENT – here, 1 and 2, respectively (Illus. 13).
© ThinPrint GmbH 2017
Illus. 13
Illus. 14
Illus. 15
Illus. 15 entering the IP address of the server where Connection Service is running,
plus a client ID (see also Illus. 23)
Illus. 16
Illus. 17
© ThinPrint GmbH 2017
– Open the properties (in context menu) of the new printer port (Illus. 18) and
enter the following:
• CONNECTION SERVER ADDRESS: tp-proxy-04
Or:
• CONNECTION SERVER ADDRESS: 192.168.149.23
Illus. 18
For print jobs to travel from the Connection Service to the workstation and from there
to the correct printer, the address information needs to be entered into the printer
names. This can be done manually or with Management Center or Management Ser-
vices.
printer_name#client_ID:printer_ID
with hash mark (#) between the printer name and client ID (Illus. 15)
and with a colon (:) between client ID and printer ID (Illus. 13).
– Select the appropriate naming convention in the properties of the new ThinPrint
port (arrow in Illus. 19). Confirm with OK.
© ThinPrint GmbH 2017
Illus. 19
Illus. 20
2. To set up the server, select EDIT SETTINGS (lower arrow in Illus. 21).
Illus. 21
3. Select ADD to specify the addresses of the print servers that can communicate
with the Connection Service (right arrow in Illus. 22), or disable the LIMIT
ACCESS TO THE FOLLOWING PRINT SERVERS option (left arrow). Here, as an exam-
ple, the address 192.168.149.114 is specified. Click on OK and conclude by
restarting TP CONNECTION SERVICE, or select the option RESTART SERVICE
(Illus. 21).
Illus. 22
© ThinPrint GmbH 2017
Illus. 22 TCP ports for connecting the Connection Service and addresses of print serv-
ers and management computers
Note! If this option is enabled and other ThinPrint components such as Man-
agement Center or Management Services Agent are being used, then their
addresses must be specified here.
4. Under TCP PORTS, you can configure over which ports ThinPrint Clients and
ThinPrint Engines (or Management Center or Management Services Agent)
should connect with Connection Service. The port numbers must match those
of the connection partners.
5. To set up the clients, select CONFIGURE CONNECTIONS (upper arrow in Illus. 21).
6. Enter the client ID and the authentication key for ThinPrint Client (Illus. 23).
You get this from the ThinPrint Client Manager (Illus. 15). Connection Service
enters the client address automatically, as soon as ThinPrint Client has con-
nected. If the connection is not made automatically, then restart ThinPrint Cli-
ent; with ThinPrint Client as a Windows service, restart the TP CLIENT SERVICE
WINDOWS.
Illus. 23
Illus. 23 entering client IDs and authentication key for ThinPrint Clients
© ThinPrint GmbH 2017
7. The console then displays the established and, where applicable, connected
ThinPrint Clients (arrow in Illus. 24).
Illus. 24
Illus. 24 Connection Service console: print servers and ThinPrint Clients set up
You can use Management Center5 (which is a part of the ThinPrint Engine Premium
license) or Management Services6 for automatic printer creation. It simplifies the cre-
ation of printers and allows the transfer of finishing options to the created printers.
If Management Center or Management Services are not available create the printers
as follows:
2. Connect the printers with a Connection Service port (CS_1:, in this example)
that you created previously (Page 16).
© ThinPrint GmbH 2017
5 http://download.cortado.com/docu/ThinPrint/MC/en/2.2/
6 http://download.cortado.com/docu/ThinPrint/Tpms/en/1.0/
Illus. 25
Illus. 26
Illus. 26 example for a type-3 driver, in this example: Lexmark T644 (MS)
The application servers send their print jobs to printers installed on a central print
server. To print to these shares in a pure Windows environment, the terminal servers
(or desktops) only need to establish a connection to these shares. In contrast, for all
constellations using non-Windows servers, you use the LPR/LPD print protocol.
© ThinPrint GmbH 2017
Example
AutoConnect can automate the process whereby of printers are created when a ses-
sion is open on a Windows machine. In doing so, AutoConnect automatically creates
printer connections (Illus. 28) to the printers on the central print server (Illus. 25) for
the duration of the session.
To achieve this, AutoConnect must be installed on each participating machine,
such as terminal servers, for example. Use ThinPrint Engine for the installation of
AutoConnect on Remote Desktop Session Hosts. This extension is an option in the
Engine installation wizard. For desktops, use Desktop Agent.
– Then enter the shares from the central print server (in this example: HP Color
LaserJet 3600 and Lexmark T644) into the AutoConnect configuration on the
terminal server under MAP ADDITIONAL PRINTERS (Illus. 27).
Illus. 27
Illus. 27 ThinPrint AutoConnect: entering shares from the central print server
Illus. 28
The two printers in Illus. 28 can now be used for the duration of a terminal session.
Print test
Now test the Connection Service installation. Print using the newly created printers
© ThinPrint GmbH 2017
(Illus. 28) on both network printers. The user who is printing must be enabled for
ThinPrint on the license server (Page 29).
Appendix
Customer service and technical support
www.thinprint.com/→ RESOURCES & SUPPORT
https://www.thinprint.com/en/resources-support/support-request/
Should you already be using an older version of Connection Service on the same com-
puter, then proceed with the installation of version 11 as for a new installation; for
more on this, see Page 7. Then check in the configurations console whether all the
old settings have been adopted by the new version. If not, you will find them in the
Windows registry under:
hkey_local_machine\Software\Wow6432Node\ThinPrint\TPConnect
Most importantly, displayed here is the list of computers that may send data to the
Connection Service; their value is IPAccessDisabled. As an example, open this value
(Illus. 29), and copy its contents, to insert it into the new path.
You will find additional registry values for Connection Services in the section Rel-
evant registry keys (Page 25).
Illus. 29
Illus. 29 Windows registry: list of the computers that can send data to the Connection
Service
© ThinPrint GmbH 2017
To uninstall the Connection Service, open PROGRAMS AND FEATURES in the CONTROL
PANEL. Highlight Connection Service (lower arrow in Illus. 30) and select UNINSTALL
(upper arrow).
Illus. 30
ConnPort TCP PORT (Illus. 15) TCP port for communication with reg_dword 4001
the Connection Service; be sure:
same TCP port number as Con-
nection Service’s ClientPort;
Page 27
Port TCP PORT (Illus. 14) TCP port for communication with reg_dword 4000
the ThinPrint Engine; be sure:
same TCP port number as Thin-
Print Engine’s Port in case of a
normal ThinPrint Port
ADDRESS
ning
ConnUID CLIENT ID (Illus. 15) Client ID for the static mode – an reg_dword 0
unambiguous ID must be
assigned for all clients (TPUID)
ConnWait CONNECTION RETRY Wait time for connection retries if reg_dword 300
INTERVAL (Illus. 15) Connection Service is not reach-
able (in seconds)
MMC of Default
Name Description Type
ThinPrint Engine value
Port TCP PORT (Illus. 18) TCP port for communication with reg_dword 4000
the Connection Service; be sure:
same TCP port number as Con-
nection Service’s ServerPort;
Page 27
© ThinPrint GmbH 2017
ClientPort THINPRINT CLIENTS TCP port for communication with reg_dword 4001
(Illus. 22) the ThinPrint Clients; be sure:
same TCP port number as Thin-
Print Client’s ConnPort; Page 25
ServerPort THINPRINT SERVERS TCP port for communication with reg_dword 4000
(Illus. 22) the ThinPrint Engine; be sure:
same TCP port number as Thin-
Print Engine’s Port in case of a
ThinPrint Connection Service
Port; Page 26
Troubleshooting
• If the installer detects that on of both default TCP ports 4000 or 4001 is already
used by another program, it assigns the next free TCP port automatically – thus
normally 4002. In this case the ThinPrint Ports which are used for printing must
© ThinPrint GmbH 2017
also use this TCP port. This also applies to the Management Center as well as
to the Management Services.
• If you have configured the ThinPrint Client Service Windows (= client installa-
tion as a Windows service) for connecting to the Connection Service:
• When you try to start the Windows service TP Client Service Windows, you
receive the following error message: “The TP Client Service Windows service
on Local Computer started and then stopped. Some services stop automati-
cally if they are not in use by other services or programs.” the TCP port, the
client ID, or the authentication key for connecting to the Connection Service
may be incorrect or missing.
Additional resources
Further information about ThinPrint can be downloaded from our website.
Thin clients and Thin Clients or terminals with embedded ICA/RDP type of ThinPrint Client as well as
gateways ThinPrint gateway appliances can be found at
https://www.thinprint.com/en/resources-support/supported-devices/.
Print servers and The TPG-25, TPG-65 and TPG-125 ThinPrint Gateways are available at
Appliances www.seh.de, as well as the ISD300 and ISD4x0 spool server. They support the Con-
nection Service.