ThinPrint Connection Service Printing via DMZ and into masked networks (version 6.2.1) Manual ThinPrint GmbH Alt-Moabit 91 a 10559 Berlin Germany / Alemania Cortado, Inc. 7600 Grandview Avenue Suite 200 Denver, Colorado 80002 USA / EEUU Cortado Pty. Ltd. Level 20, The Zenith Centre, Tower A 821 Pacific Highway Chatswood, NSW 2067 Australia E-Mail: info@cortado.com Web: www.thinprint.
Notes © 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. ® 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 warning All ThinPrint products are pure software solutions.
Contents Introduction ................................................................................................................ 4 Connection Service scenarios ........................................................................................... 4 Standard ThinPrint scenario ........................................................................................ 4 Printing via DMZ and into masked networks .................................................................
Introduction Introduction The change from expensive leased or dedicated lines to inexpensive VPN connections – usually based on the economical DSL norm – is today a must for every IT manager. Printing across VPN connections, however, creates quite a few challenges for administrators.
Introduction data 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 © ThinPrint GmbH 2015 So that ThinPrint Client does not have to be installed on every end device in a remote office, it is enough to install it on a local print server or a gateway appliance (Illus. 2).
Introduction Illus. 2 Illus. 2 ThinPrint Engine sends print jobs using Connection Services (arrows show directions of TCP communication) Driver Free Printing and V-Layer ThinPrint’s Driver Free Printing offers two main advantages: • No (native) printer drivers have to be installed on the Windows application servers. • Print jobs can be compressed much more than when printing with native printer drivers.
Licensing Licensing 1. You need the ThinPrint Engine Premium type license (ThinPrint version 10). You enter this on the (to be installed) Cortado 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 24). 2. For Connection Service, you can also apply in Enterprise Portal3 for a for a THCG-0498-5 type license, free of charge.
Example configuration Tips 1. 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 24). 2. For this example configuration, you need the licenses referred to under Licensing (see above), of which 30 day demo versions are available. IP address (computer name) Installed on ... Component Central print server ThinPrint Engine 192.168.
Example configuration Basic installation Application server – Provide an application server; e.g., a Citrix XenApp server or a Microsoft Remote Desktop Session host (or terminal server). Central print server – Install ThinPrint Engine on a central print server. Please consult the ThinPrint Engine on print servers manual (Page 24). Workstation – Install a ThinPrint Client on a Windows Workstation (or on a local Windows print server). See the appropriate manual ThinPrint Client Windows (Page 24).
Example configuration Illus. 4 activat server role LPD SERVICE for UNIX Workstation On the workstations4 you can use Windows or a non Windows operation system.
Example configuration Illus. 5 Illus. 5 ThinPrint Client Manager: printer IDs 1 and 2 – Enable USE CONNECTION SERVICE on the ADVANCED tab (Illus. 6). Illus. 6 Illus. 6 Enable Connection Service – In the CONNECTION SERVICE tab, enter the following (Illus. 7): • Connection server address: • TCP port: • Client ID: • Authentication key: • Connection retry interval (s): • Keep alive interval: 192.168.149.
Example configuration Illus. 7 Illus. 7 Entering the IP address of the server where Connection Service is running and a client ID (see also Illus. 20) Central print server under Windows Creating printer ports (ThinPrint Engine) – Open the ThinPrint Engine port configuration. – Create a new printer port with the type “ThinPrint Connection Service port” (arrow in Illus. 8). Illus. 8 Illus. 8 Creating a new ThinPrint port for the Connection Service – In the next window, enter a port name (Illus. 9).
Example configuration Illus. 10 Illus. 10 Entering Connection Service’s IP 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 ThinPrint Management Center.
Example configuration Illus. 11 Illus. 11 Setting name convention of the Connection Service Port Windows server with Connection Service System requirements The following are the operating system requirements: • Windows Server 2003 or 2003 R2 with Service Pack 2 or higher (only x86), Windows Server 2008 (only x64) or 2008 R2 Installation Install the Connection Service on a separate Windows server as follows 5: – Unzip file TP10x64Bundle.zip.
Example configuration Illus. 12 Illus. 12 License Manager: entering a demo license key for the Connection Service (example) – Close License Manager. – Register the Connection Service from the command prompt in the same directory with: TPConnect -install If successful, you will receive the message shown in Illus. 13. Confirm with OK. Illus. 13 Illus.
Example configuration Field Explanation Entry/default value CLIENT TCP port number for connection to ThinPrint Clients 4001 CONNECTIONS – Close the configuration panel with OK. Illus. 14 Illus. 14 Configuring a client ID Connection Service: configuring the IP address of the central print server – Open the command prompt and change to the Connection Service installation directory. – Set up the Client ID that you previously set up in ThinPrint Client Manager. For the example in Illus.
Example configuration 2. Connect the printers with a Connection Service Port (here: CS_1, as an example) you created before (Page 12). The result is shown here: Illus. 15 Illus. 15 Connection Service: created printers on the central print server Application server/host system The application servers send their print jobs to the printers installed on a central print server.
Further configuration options Illus. 17 Illus. 17 Printers created on a Windows terminal server by AutoConnect - printing to Windows workstation (TP Output Gateway) The two printers in Illus. 17 can now be used for the duration of a terminal server session. Print test Now test the Connection Service installation. Print using the newly created printers (Illus. 17) on both network printers. The user who is printing must be enabled for ThinPrint on the license server (Page 24).
Further configuration options Illus. 18 Illus. 18 Setting timeout Connections The CONNECTIONS tab (Illus.
Further configuration options Illus. 19 Illus. 19 Configuring IP addresses and TCP ports – Close the configuration program by clicking OK. – Lastly, restart the TP CONNECTION SERVICE in the Windows Services folder. Client IDs A client ID including authentication key must be stored in the Connection Service access database for every end device that is allowed to use the ThinPrint Connection Service (see below). These two values must also be set up in each ThinPrint Client (Illus. 7).
Appendix – Close TPConnect.mdb. – Restart the TP CONNECTION SERVICE in the Windows Services folder. Illus. 20 Illus. 20 Connection Service’s database with client ID 99 and authentication key 111 (see also Illus. 7) Appendix Customer service and technical support www.thinprint.com/ → RESOURCES & SUPPORT www.thinprint.com/en-us/resourcessupport/supportrequest.
Appendix Name ThinPrint Client Manager Port Description Type Default value TCP PORT (Illus. 6) TCP port for communication with the ThinPrint Engine; be sure: same TCP port number as ThinPrint Engine’s “Port” in case of a normal ThinPrint Port reg_dword 4000 ConnServer CONNECTION SERVER ADDRESS (Illus. 7) IP address of the computer on which Connection Service is running reg_sz 127.0.0.1 ConnUID CLIENT ID (Illus.
Appendix Name Connection Service GUI Description Type Default value ClientPort CLIENT CONNECTIONS (Illus. 19) TCP port for communication with the ThinPrint Clients; be sure: same TCP port number as ThinPrint Clients “ConnPort”; Page 21 reg_dword 4001 FirstSessionTO MAX. TIME TO FIRST Max.
Appendix Additional resources Manuals and technical information The following documents (amongst others) are available at www.thinprint.
