ThinPrint GmbHAlt-Moabit 91 a10559 BerlinGermany/Alemania

Cortado, Inc.7600 Grandview AvenueSuite 200Denver, Colorado 80002USA/EEUU

Cortado Pty. Ltd.Level 12, Plaza Building, Australia Square95 Pitt StreetNSW 2000 SydneyAustralia

E-mail: info@thinprint.comWeb: www.thinprint.com

Issued: December 15, 2017 (v250)

ThinPrint Connection Service

Printing via DMZ and into masked networks (version 11)

Manual

Notes

2 Manual

© CopyrightThis 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.

® Registered trade marks All hardware and software names mentioned in this document are the registered trademarks of their respective companies or should be regarded as such.

Safety warningPlease 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.

© ThinPrint G

mbH

2017

Contents

Manual 3

© T

hinP

rint

Gm

bH 2

01

7

Introduction ................................................................................................................ 4

Connection Service scenarios ........................................................................................... 4

Standard ThinPrint scenario ........................................................................................ 4Printing via DMZ and into masked networks ................................................................. 5

Driver Free Printing and V-Layer ....................................................................................... 6

Technical requirements ......................................................................................... 7

Licensing ....................................................................................................................... 7

Technical restrictions for the Connection Service ................................................................ 7

Installation .................................................................................................................. 7

Sample configuration ............................................................................................ 11

Basic installation .......................................................................................................... 12

Basic configuration .................................................................................................. 13

Workstation ................................................................................................................. 13

Central print server under Windows ................................................................................ 16

Windows server with Connection Service ......................................................................... 18

Creating printers on the central print server ..................................................................... 21

Application server/host system ....................................................................................... 22

Example ................................................................................................................. 22

Print test ..................................................................................................................... 23

Appendix .................................................................................................................... 24

Customer service and technical support .......................................................................... 24

Updating the Connection Service .................................................................................... 24

Uninstalling the Connection Service ................................................................................ 24

Relevant registry keys ................................................................................................... 25

Registry keys of ThinPrint Client (Service) Windows for Connection Service .................... 25Registry keys of ThinPrint Engine for Connection Service Ports ...................................... 26Registry keys of Connection Service ........................................................................... 27

Troubleshooting ........................................................................................................... 27

Additional resources ..................................................................................................... 29

Abbreviations and acronyms .......................................................................................... 29

Introduction

4 Manual Connection Service.fm

© ThinPrint G

mbH

2017

IntroductionIn 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.

Connection Service scenariosStandard ThinPrint scenario

In a normal setting, ThinPrint Engine is installed on a terminal server, another appli-cation server, or a central (dedicated) print server. When a user initiates a print job, ThinPrint Engine compresses and encrypts the print data and streams it (in packets of some KB) across a preset bandwidth to the ThinPrint Client (Illus. 1). ThinPrint Client decompresses and decrypts the print data and forwards it to the correct print interface. If ThinPrint Output Gateway (Driver Free Printing) is used on the server, rather than an original printer driver, ThinPrint Client Windows feeds the print data

Introduction

Connection Service.fm Manual 5

© T

hinP

rint

Gm

bH 2

01

7

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)

Printing via DMZ and into masked networks

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 it1 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.

1 Under Windows, it can also render the data.

2 http://download.cortado.com/docu/ThinPrint/MC/en/2.2/

3 http://download.cortado.com/docu/ThinPrint/Tpms/en/1.0/

Introduction

6 Manual Connection Service.fm

© ThinPrint G

mbH

2017

Illus. 2

Illus. 2 ThinPrint Engine sends print jobs using Connection Services (arrows show directions of TCP communication)

Driver Free Printing and V-LayerThinPrint’s Driver Free Printing offers two main advantages:

• No (native) printer drivers have to be installed on the Windows application serv-ers.

• Print jobs can be compressed much more than when printing with native printer drivers.

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).

Technical requirements

Connection Service.fm Manual 7

© T

hinP

rint

Gm

bH 2

01

7

Technical requirementsLicensing

As Connection Service is a premium component of ThinPrint Engine, it requires the ThinPrint Engine Premium type license (ThinPrint version 10 or later). You enter this on the (to be installed) License Server. The license server can be installed on any computer in the domain, e.g. the print server. This is not described in depth here, but details can be found in the License Server manual (Page 29).

All license keys are valid for 30 days after they have been entered. They must be activated within this time to continue printing. 30-day and demo license keys cannot be activated.

Once you have successfully tested ThinPrint, you can purchase a full license. You will receive new license keys, which are then entered in the License Manager. To acti-vate the license keys upload them together with their registration keys to the Cortado Enterprise Portal. For further information about the activation procedure see the Licensing manual (Page 29).

Technical restrictions for the Connection Service

Connection Service installation routines are available for the following operating sys-tems:

• Windows Server 2008 R2• Windows Server 2012• Windows Server 2012 R2

The server can be a member of a domain. However, domain membership is not advis-able for operation in the DMZ (Illus. 2).

Note! For installation of Connection Service, it is recommended to pre-install .NET Framework 3.5 (it's not a component of .NET Framework 4.0 or 4.5). If .NET Framework 3.5 is not present, the installer attempts to download it from the Microsoft server.

Installation

If you're installing an update, refer to the section Updating the Connection Service (Page 24). For a new installation, proceed as follows.

Installation

8 Manual Connection Service.fm

© ThinPrint G

mbH

2017

Note! Install the ThinPrint Engine’s ADMINISTRATION TOOLS on this machine beforehand if the Connection Service isn’t to be installed on a member server of the domain in which the ThinPrint Engine runs – e.g. with an installation in the DMZ. The Administration Tools are the MMC component of the ThinPrint Engine and are required for configuring the Connection Service.

1. Copy the installation routine from the relevant server.

2. Run the file Setup_ThinPrintConnectionService_x64.exe resp. Setup_ThinPrint-ConnectionService_x86.exe (Illus. 3).

Illus. 3

Illus. 3 running the Connection Service installer

3. Select your preferred language (Illus. 4).

Illus. 4

Illus. 4 selecting the language

4. Click on NEXT to confirm the welcome window (Illus. 5).

Illus. 5

Illus. 5 the installer welcome window

Installation

Connection Service.fm Manual 9

© T

hinP

rint

Gm

bH 2

01

7

5. Read and accept the license agreement, and click on NEXT (Illus. 6).

Illus. 6

Illus. 6 accepting the license agreement

6. Select the components to be installed. • ThinPrint Connection Service is the actual Windows service.• Connection Service Configuration is the MMC component for configuring

Connection Service (it requires .NET Framework 3.5).Confirm with NEXT (Illus. 7).

Illus. 7

Illus. 7 selecting the components to install

Installation

10 Manual Connection Service.fm

© ThinPrint G

mbH

2017

7. Select the installation path with CHANGE, and then confirm with NEXT (Illus. 8).

Illus. 8

Illus. 8 selecting the installation path

8. Start the actual installation by clicking INSTALL (Illus. 9).

Illus. 9

Illus. 9 starting the Connection Service installation

9. Confirm the completed installation by clicking on FINISH (Illus. 10).

Illus. 10

Illus. 10 click on FINISH to close the installer

Sample configuration

Connection Service.fm Manual 11

© T

hinP

rint

Gm

bH 2

01

7

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:

• 1 application server (e.g. a Citrix XenApp server in the domain)• 1 central Windows print server (in the domain) with ThinPrint Engine installed• 1 Windows server with Connection Service installed• 1 ThinPrint License Server (can be installed on any server of the domain)• 1 NAT router• 1 Windows workstation with ThinPrint Client Windows installed• 1 network printer with an internal or external print server (without embedded

ThinPrint Client)

Tips – The ThinPrint Connection Service only works with TCP/IP.

– Installation of the ThinPrint Engine on a central print server is not described in depth here. For the installation procedure, please consult the relevant manual (Page 29).

Installed on ... ComponentIP address (computer name)

central print server ThinPrint Engine 192.168.149.114 (cps47.ourdomain.local)

Additional Windows server ThinPrint Connec-tion Service

192.168.149.23 (tp-proxy-04)

Application server (e.g. XenApp)

ThinPrint Engine 192.168.149.200(ts074.ourdomain.local)

Workstation (or local print server)

ThinPrint Client 192.168.1.150(client701)

Sample configuration

12 Manual Connection Service.fm

© ThinPrint G

mbH

2017

Illus. 11

Illus. 11 example configuration

Basic installationApplication 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).

Sample configuration

Connection Service.fm Manual 13

© T

hinP

rint

Gm

bH 2

01

7

Basic configuration

– Assign all computers and devices involved IP addresses in the headquarters’ subnet (192.168.149.0/24) and in the local, masked subnet (192.168.1.0/24); for example:

• For the application server: 192.168.149.200• For the central print server: 192.168.149.114• For the server with Connection Service:192.168.149.23• For the local print server: 192.168.1.150• For the network printer: 192.168.1.50

– If you are running non-Windows servers as host systems (application servers) but the central print server is nevertheless a Windows server, please activate the server role LPD SERVICE on the central print server (SERVER ROLES→ PRINT AND DOCUMENT SERVICES→ LPD SERVICE, Illus. 12) or else install alternative software such as SAPSprint.

Illus. 12

Illus. 12 activate server role LPD SERVICE for UNIX

Workstation

On the workstations4 you can use Windows or a non-Windows operation system. The only requirement is that the ThinPrint Client to be installed supports the Connection Service; the following are appropriate:

• ThinPrint Client Windows

Sample configuration

14 Manual Connection Service.fm

© ThinPrint G

mbH

2017

• ThinPrint Client Service Windows

• ThinPrint Client Linux

• ThinPrint Client Mac

• 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)

– For this create new Standard TCP/IP ports.

ThinPrint Client Service Windows

Install ThinPrint Client as described in the ThinPrint Client Windows manual (Page 29).

– Start the ThinPrint Client Manager (via START menu).

– Find the printer IDs for the HP Color LaserJet 3600 and the Lexmark T644 under ASSIGNMENT – here, 1 and 2, respectively (Illus. 13).

4 The client can also be installed on a local print server.

Sample configuration

Connection Service.fm Manual 15

© T

hinP

rint

Gm

bH 2

01

7

Illus. 13

Illus. 13 ThinPrint Client Manager: printer IDs 1 and 2

– Enable USE CONNECTION SERVICE on the ADVANCED tab (Illus. 14).

Illus. 14

Illus. 14 enable Connection Service

– In the CONNECTION SERVICE tab, enter the following (Illus. 15):

• Connection server address: 192.168.149.23• TCP port: 4001• Client ID: 99 (here as example)• Authentication key: 111 (here as example)• Connection retry interval (s): 300 (here as example)• Keep alive interval: 60 (if displayed)

– Close ThinPrint Client Manager with OK.

– Restart the THINPRINT CLIENT in the Windows Services folder.

Sample configuration

16 Manual Connection Service.fm

© ThinPrint G

mbH

2017

Illus. 15

Illus. 15 entering the IP address of the server where Connection Service is running, plus a client ID (see also Illus. 23)

Central print server under WindowsCreating printer ports (ThinPrint Engine)

– Open the ThinPrint Engine port configuration.

– Create a new printer port of the type ThinPrint Connection Service Port (arrow in Illus. 16).

Illus. 16

Illus. 16 creating a new ThinPrint port for the Connection Service

– In the next window, enter a port name (Illus. 17).

Illus. 17

Illus. 17 entering a port name (example)

Sample configuration

Connection Service.fm Manual 17

© T

hinP

rint

Gm

bH 2

01

7

– Open the properties (in context menu) of the new printer port (Illus. 18) and enter the following:• CONNECTION SERVER ADDRESS: tp-proxy-04Or:• CONNECTION SERVER ADDRESS: 192.168.149.23

Illus. 18

Illus. 18 entering Connection Service’s address

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.

The resulting printers then have the following syntax:

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.

Sample configuration

18 Manual Connection Service.fm

© ThinPrint G

mbH

2017

Illus. 19

Illus. 19 checking/setting naming convention of the Connection Service Port

Windows server with Connection Service

1. Start the Connection Service configuration (Illus. 20).

Illus. 20

Illus. 20 opening the Connection Service configuration console

Sample configuration

Connection Service.fm Manual 19

© T

hinP

rint

Gm

bH 2

01

7

2. To set up the server, select EDIT SETTINGS (lower arrow in Illus. 21).

Illus. 21

Illus. 21 Connection Services configuration console

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

Illus. 22 TCP ports for connecting the Connection Service and addresses of print serv-ers and management computers

Sample configuration

20 Manual Connection Service.fm

© ThinPrint G

mbH

2017

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

Sample configuration

Connection Service.fm Manual 21

© T

hinP

rint

Gm

bH 2

01

7

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

Creating printers on the central print server

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:

1. Create printers with the following syntax:HP Color LaserJet 3600#99:1Lexmark T 644#99:2,where, 99 represents the client ID (see Illus. 15), and 1 (or2) is the printer ID in ThinPrint Client Manager (see Illus. 13). Note the syntax, using the hash key (#) and colon (:).

2. Connect the printers with a Connection Service port (CS_1:, in this example) that you created previously (Page 16).

5 http://download.cortado.com/docu/ThinPrint/MC/en/2.2/

6 http://download.cortado.com/docu/ThinPrint/Tpms/en/1.0/

Sample configuration

22 Manual Connection Service.fm

© ThinPrint G

mbH

2017

The result is shown here:

Illus. 25

Illus. 25 Connection Service: created printers on the central print server

Note! From Windows 2012 R2 type-4 drivers can’t be connected to third-party printer ports. Consequently type-3 drivers are used with ThinPrint Connection Service ports (Illus. 26) – e.g. TP Output Gateway.

Illus. 26

Illus. 26 example for a type-3 driver, in this example: Lexmark T644 (MS)

Application server/host system

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.

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

Sample configuration

Connection Service.fm Manual 23

© T

hinP

rint

Gm

bH 2

01

7

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

Illus. 28 printers on a Windows terminal server connected by AutoConnect – printing to a Windows workstation (TP Output Gateway used as driver)

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 (Illus. 28) on both network printers. The user who is printing must be enabled for ThinPrint on the license server (Page 29).

Appendix

24 Manual Connection Service.fm

© ThinPrint G

mbH

2017

AppendixCustomer service and technical supportwww.thinprint.com/→ RESOURCES & SUPPORT https://www.thinprint.com/en/resources-support/support-request/

Updating the Connection Service

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

– Simply copy the missing settings to: hkey_local_machine\Software\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

Uninstalling the Connection Service

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).

Appendix

Connection Service.fm Manual 25

© T

hinP

rint

Gm

bH 2

01

7

Illus. 30

Illus. 30 uninstalling Connection Service

Relevant registry keysRegistry keys of ThinPrint Client (Service) Windows for Connection Servicehkey_local_machine\software\thinprint\client:

NameThinPrint Client Manager

Description TypeDefault value

ConnAuthKey AUTHENTICATION KEY (Illus. 15)

Value is used for authentication – like a password.

reg_dword 0

ConnMode USE CONNECTION SERVICE (Illus. 14)

0 = Listen mode3 = Static mode1 = 0 + 3

reg_dword 0

ConnPort TCP PORT (Illus. 15) TCP port for communication with the Connection Service; be sure: same TCP port number as Con-nection Service’s ClientPort; Page 27

reg_dword 4001

Port TCP PORT (Illus. 14) TCP port for communication with the ThinPrint Engine; be sure: same TCP port number as Thin-Print Engine’s Port in case of a normal ThinPrint Port

reg_dword 4000

ConnServer CONNECTION SERVER ADDRESS (Illus. 15)

IPv4 address of the computer on which Connection Service is run-ning

reg_sz 127.0.0.1

Appendix

26 Manual Connection Service.fm

© ThinPrint G

mbH

2017

Registry keys of ThinPrint Engine for Connection Service Portshkey_local_machine\system\CurrentControlSet\Control\Print\Monitors\ThinPrint Port\<port name>:

ConnUID CLIENT ID (Illus. 15) Client ID for the static mode – an unambiguous ID must be assigned for all clients (TPUID)

reg_dword 0

ConnWait CONNECTION RETRY INTERVAL (Illus. 15)

Wait time for connection retries if Connection Service is not reach-able (in seconds)

reg_dword 300

NameThinPrint Client Manager

Description TypeDefault value

NameMMC of ThinPrint Engine

Description TypeDefault value

Host CONNECTION SER-VICE ADDRESS (Illus. 18)

address of the computer on which Connection Service is running

reg_sz —

IsCSvcPort NEW THINPRINT CONNECTION SER-VICE PORT/NEW THINPRINT PORT

0 = ThinPrint Engine prints directly to ThinPrint Clients or LPD devices1 = ThinPrint Engine prints to the Connection Service

reg_dword —

Port TCP PORT (Illus. 18) TCP port for communication with the Connection Service; be sure: same TCP port number as Con-nection Service’s ServerPort; Page 27

reg_dword 4000

Appendix

Connection Service.fm Manual 27

© T

hinP

rint

Gm

bH 2

01

7

Registry keys of Connection Servicehkey_local_machine\software\thinprint\tpconnect:

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 also use this TCP port. This also applies to the Management Center as well as to the Management Services.

NameConnection Service GUI

Description TypeDefault value

ClientPort THINPRINT CLIENTS (Illus. 22)

TCP port for communication with the ThinPrint Clients; be sure: same TCP port number as Thin-Print Client’s ConnPort; Page 25

reg_dword 4001

IPAccess ADDRESSES OF THIN-PRINT SERVERS THAT ARE ALLOWED TO USE CONNECTION SER-VICE (Illus. 22)

Allowed addresses of ThinPrint Engines, Management Center or Tpms.Agent (of Management Ser-vices)

reg_mul-ti_sz

—

IPAccessDis-abled

LIMIT ACCESS TO THE FOLLOWING PRINT SERVERS (Illus. 22)

1 = All addresses are allowed reg_sz 0

KeepAliveTO — Interval for refreshing the connec-tion (in seconds)

reg_dword 70

ReconnectTO — Max. client reconnect time (in seconds)

reg_dword 80

ServerPort THINPRINT SERVERS (Illus. 22)

TCP port for communication with 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

reg_dword 4000

Standalone — Key has to be exist and set to 1 reg_dword —

Appendix

28 Manual Connection Service.fm

© ThinPrint G

mbH

2017

• 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.

Appendix

Connection Service.fm Manual 29

© T

hinP

rint

Gm

bH 2

01

7

Additional resourcesFurther information about ThinPrint can be downloaded from our website.

Manuals and descriptions

Manuals and other technical information are available at https://www.thinprint.com/en/resources-support/guides-manuals/.

Thin clients and gateways

Thin Clients or terminals with embedded ICA/RDP type of ThinPrint Client as well as ThinPrint gateway appliances can be found at https://www.thinprint.com/en/resources-support/supported-devices/.

Software downloads

The current version of ThinPrint Engine, can be downloaded at: www.thinprint.com/demo.

ThinPrint Clients as well as tools like Finishing Detector and ThinPrint Preview (TPView.exe) can be found at https://www.thinprint.com/en/resources-support/software/clientsandtools/.

Print servers and Appliances

The TPG-25, TPG-65 and TPG-125 ThinPrint Gateways are available at www.seh.de, as well as the ISD300 and ISD4x0 spool server. They support the Con-nection Service.

Abbreviations and acronyms

ID Identification (number)

IP Internet Protocol (see also TCP/IP)

LPD Line Printer Daemon

LPR Line Printer Remote

MMC Microsoft Management Console

NAT Network Address Translation (also known as: IP masking)

s Second(s)

TCP/IP Transmission Control Protocol over Internet Protocol

TP ThinPrint