Client Gateway Windows En

8/3/2019 Client Gateway Windows En

http://slidepdf.com/reader/full/client-gateway-windows-en 1/16

White Paper

Windows computer as a .print Client GatewayPractice examples (.print version 7.6)

A .print Client Gateway is a local print server with an

installed .print Client. It can simplify the implementa-

tion of ThinPrint .print, because it can receive .print

print jobs for an entire group of client machines and

printers, decompress and decrypt them, and then dis-

tribute them conventionally in a local network – as a

local print server. The remote LAN, then, only needs a

single .print Client on a Client Gateway. Otherwise, a

.print Client must be installed on every end device on

the client side: on PCs, printers, thin clients, and inter-nal or external print servers of network printers, etc.

Mixed environments pose no problem, either. The

.print Client is installed on all end devices which allow

a simple installation, and all others are served by the

.print Client Gateway.

Sample configuration 1:

with terminal server■ Basic installation and configuration

■ Terminal client and .print Client Gateway

configuration

■ Terminal server configuration

■ Print test

Sample configuration 2:with central dedicated print server■ Basic installation and configuration

■ Dedicated print server and terminal server

configuration

■ print test

Appendix■ Special case: only one Client Gateway

per ThinPrint Port

■ How can I suppress incorrect print jobs?

■ Additional sources

Local print server (.print Client Gateway) receives .print print jobs

and distributes them to all printers in the client network



ThinPrint AG

Alt-Moabit 91 a/b

10559 BerlinGermany/ Alemania

ThinPrint Pty. Ltd.

L 10, 275 Alfred Street

North Sydney/NSW/2060

Australia

ThinPrint, Inc.

20006 Detroit Road, Suite 303

Cleveland, OH 44116

USA/ EEUU

ThinPrint, Inc.

7600 Grandview Avenue, Suite 200Denver, Colorado 80002

USA/ EEUU

© Copyright

This document is the intellectual property of ThinPrint AG. This document may be copied in wholeor 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.

E-mail: [email protected]: www.thinprint.com

Issued: October 13, 2009 (v48)

mailto:[email protected]

http://www.thinprint.com/


mailto:[email protected]



Contents

Client Gateway Windows White Paper 3

© T

h i n P r i n t

A G 2 0 0 9

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

Sample configuration 1: with terminal server ............................................... 4

Basic installation ............................................................................................................ 5

Basic configuration ......................................................................................................... 6

Client machine ............................................................................................................... 6

Client Gateway (local print server) ....... ....... ....... ........ ....... ....... ........ ....... ....... ....... ........ .... 6

Terminal server .............................................................................................................. 8

Print test ....................................................................................................................... 9

Sample configuration 2: with central print server ....................................... 9

Basic installation .......................................................................................................... 10

Basic configuration ....................................................................................................... 10

Central print server ....................................................................................................... 11

Terminal server ............................................................................................................ 12

Print test ..................................................................................................................... 13

Appendix .................................................................................................................... 13

Special case: only 1 Client Gateway per Port .... .... ....... .... .... ....... ....... .... .... ....... ....... .... .... 13

How can I suppress incorrect print jobs? ....... ........ ....... ....... ....... ........ ........ ....... ....... ....... 13

Environment ........................................................................................................... 13

Scenario ................................................................................................................. 14

Solution .................................................................................................................. 14

Procedure ............................................................................................................... 14

Additional sources ........................................................................................................ 16

Abbreviations ............................................................................................................... 16



Introduction

4 White Paper Client Gateway Windows

© T h i nP r i n t A

G2 0 0 9

IntroductionA .print Client Gateway can simplify the implementation of ThinPrint .print, because

it can receive .print print jobs for an entire group of client machines and printers,

decompress and decrypt

1

them, and then distribute them conventionally in a localnetwork – as a local print server. The remote LAN, then, only needs a single .print

Client on a Client Gateway. Otherwise, a .print Client must be installed on every end

device on the client side: on PCs, printers, thin clients, print servers of network print-

ers, etc. This means, for example, that thin clients could require a firmware or BIOS

update.

Mixed environments pose no problem, either. The .print Client is installed on all

end devices which allow a simple installation, and all others are served by the .print

Client Gateway.

The following two examples illustrate test installations of a .print Client Gateway.

Once you are convinced of the software’s functionality, the installation can be

adapted to your requirements.

Sample configuration 1: with terminal serverWith this sample configuration all users should be able to print to both their local

(attached) printer and a network printer (via TCP/IP; Illus. 1). The components

required for this example are:

■ 1 client machine (Windows) with a locally installed printer

■ 1 Windows machine configured as a .print Client Gateway

incl. .print Client Service Windows

■ 1 network printer (with its own network card) without integrated .print Client

■ 1 terminal server2 including the .print Application Server Engine license (with

server-based licensing) or the .print Application Server Basic Pack license +

user licenses (with user-based licensing)

1 For installation of SSL/TLS certificates see the “Creating SSL certi ficates for printing with Thin-

Print .print” white paper or the “.print Server Engine” manual (Page 16).

Tip! There are many alternatives for .print Client Gateways, e.g., Windows

or Linux machines, print server appliances, and print servers from SEH or

Intermate. But for Driver Free Printing only Windows machines are usable.

And for Printer Virtualization Layer you need an additional central print server

(Windows); see “.print Server Engine” user manual (Page 16).

2 Windows Server 2003 /2008 (2003 x64 with Service Pack 1 or later)



Sample configuration 1: with terminal server


© T

h i n P r i n t

A G 2 0 0 9

Illus. 1

Notes 1. The .print Client Gateway only receives print jobs via the protocol TCP/IP(not via ICA or RDP).

2. Please refer to the “.print Application Server Engine” and “.print Client Service

Windows” user manuals for installations of .print Engine and .print Client not

detailed here (Page 16).

3. The following .print licenses are required for this sample configuration

(each of which offers a 30-day demo version):

Basic installation

Client machine – If necessary, install an RDP client (Remote Desktop Connection) or a Citrix ICAclient on a Windows PC.

Local print server

(Client Gateway)

– Install the .print Client Service Windows on another Windows machine

(Windows 2000 or later).

Terminal server – Install the .print Engine on a terminal server3 (required license: see above).

Il lus. 1 Sample configuration 1

License Location of installation

Either .print Application Server

Engine with server-based licensing

per terminal server

Or .print Application Server Basic

Pack + user licenses with user-

based licensing

.print Application Server Basic Pack

per terminal server; user licenses

have to be splitted

3 Windows Server 2003 or 2008 – with or without Citrix XenApp






G2 0 0 9

Basic configuration

Give all computers involved IP addresses in the same subnet; e.g.:

• for the client machine: 192.168.131.124• for the .print Client Gateway: 192.168.131.125

• for the network printer: 192.168.131.200

• for the terminal server: 192.168.131.126

In this example, a printer is connected to the client machine with the default printer

interface LPT1:; the client machine is named client1.

Client machine

– Create the printer HP DeskJet on the client machine (here: client1) and shareit (share name: DeskJet ; Illus. 2). (This printer share is necessary for Windows

clients only.)

Illus. 2

Client Gateway (local print server) – Create two printers on the local print server:

• One printer as a connection to the DeskJet share on client1 (Illus. 3)

• the network printer (with internal print server without .print Client)

HP Color Laser Jet 4700. To do so, create the new port

IP_192.168.131.200 as “Standard TCP/IP port” type (Illus. 3 and 4).

Tip! Use the same admin account for both client PC and local print server

(Client Gateway) administration.

Il lus. 2 Printer on the client machine





© T

h i n P r i n t

A G 2 0 0 9

Illus. 3

Illus. 4

– Right click the .print Client icon in the taskbar (Illus. 5). Choose RELOAD PRINT-

ERS; the newly installed printers will be detected.

Illus. 5

– Next, start .print Client Manager by choosing CONFIGURE (Illus. 5). The two

printers with their IDs are shown (Illus. 6). Set the checkmarks of both printers

for use with AutoConnect (arrows left).

Il lus. 3 Printers and Faxes folder on the local print server (.print Client Gateway)

Il lus. 4 Printer properties of the network printer

Il lus. 5 .print Client’s context menu

in the taskbar






G2 0 0 9

Illus. 6

– Close .print Client Manager with OK.

Terminal server

– From the client PC open a Remote Desktop or Citrix ICA session on the terminal

server.

– Open the Command Prompt, change to the .print Engine’s program directory4

and import the printer(s) with the following command5:

TPAutoConnect -a 192.168.131.125

The result is shown in (Illus. 7).

Illus. 7

A logoff script can be used to remove the printers (with logging off).

– In the session, check ThinPrint port configuration (START¡ PROGRAMS¡ .PRINT

ENGINE¡ PORT MANAGER) to see that protocol and bandwidth are set correctly

(Illus. 8). Then close the port configuration.

Il lus. 6 .print Client Manager on Client Gateway: printer IDs 1 and 2

4 e.g. c:\Program Files\ThinPrint .print Engine

5 Or use a script in the user’s startup folder.

Il lus. 7 Printers and Faxes folder in the terminal session



Sample configuration 2: with central print server


© T

h i n P r i n t

A G 2 0 0 9

Illus. 8

Print test

Now test the .print Client Gateway installation. Print from within a terminal session

using the newly created printers.

Sample configuration 2: with central print serverIn this scenario an additional central print server is used ( Illus. 9). The components

required for this example are:

■ 1 Windows client machine with a locally installed printer

■ 1 Windows machine (Windows 2000 or later) configured as a .print ClientGateway (local print server incl. .print Client Service Windows)

■ 1 network printer with its own network card without integrated .print Client

■ 1 terminal server (Windows 2003/2008)

incl. .print AutoConnect and ThinPrint Output Gateway

■ 1 central print server (Windows 2003/2008) incl. .print Engine

Illus. 9

Il lus. 8 Port Configuration: printers on the terminal server assigned to a ThinPrint Port

Il lus. 9 Sample configuration 2: with a central (dedicated) print server






G2 0 0 9

Tips 1. The .print Client Gateway only works with the protocol TCP/IP.

2. Please refer to the “.print Application Server Engine” and “.print Client Service

Windows” user manuals for installations of .print Engine and .print Client not

detailed here (Page 16).

3. The following .print licenses are required for this sample configuration (each ofwhich offers a 30-day demo version):

Basic installation

Client machine – Install a terminal client (RDP or ICA client) on a Windows machine.

Client Gateway

(local print server)

– Install .print Client Service Windows on another Windows machine (Windows

2000 or later).

Terminal server – Have a terminal server ready.6 Install .print AutoConnect and ThinPrint Output

Gateway here (required license: .print Application Server Engine)

Central print server – Install .print Engine on a central print server (Windows 2003/2008). (Required

license: .print Server Engine.)

Basic configuration

– Assign all computers involved IP addresses in the same subnet; for example:

• for the client machine: 192.168.131.124

• for the .print Client Gateway: 192.168.131.125

• for the network printer: 192.168.131.200

• for the terminal server: 192.168.131.126• for the central print server: 192.168.131.127

Configure the client machine and .print Client Gateway as described in example 1

(starting Page 6). Continue as follows:

License Location

.print Server Engine Central print server

.print Application Server Engine Terminal server

6 Windows 2003/2008, 32bit or x64, with or without Citrix Xen Desktop





© T

h i n P r i n t

A G 2 0 0 9

Central print server

– Once .print Engine is installed, create the two Client Gateway printers on the

central print server. To do so, install either the original, native printer driver or

a ThinPrint Output Gateway. Connect these printers with the printer port“ThinPort:” .7

– So that the print jobs reach the correct client, the address of the .print Client

Gateway is included in printer object name. Therefore, rename the printer

objects with the following syntax:

printer_name#client_gateway_IP_address:printer_ID

For the shared printer on the terminal client in our example (Illus. 2) the result-

ing name would be:

HP DesktJet#192.168.131.125:2

and for the network printer (Illus. 3):

HP Color Laser Jet 4700#192.168.131.125:1

The IP address is the address of the Client Gateway and the printer ID is found in

.print Client Manager on the Client Gateway (Illus. 6). (The printer name before the

# is irrelevant for addressing print jobs; it only serves to differentiate between print-

ers.)

– Share both printers (Illus. 10).

Illus. 10

– Check ThinPrint port configuration in the MMC to see that both printers are cor-

rectly associated with a ThinPrint Port and that protocol and bandwidth are set

correctly (Illus. 11). Check the name convention. Do not change the settings of

the ThinPrint Port “ThinPort:”. Then close the port configuration.

7 Do not change the properties of the ThinPrint Port “ ThinPort:” after installation of

the .print Engine.

Illus. 10 Printers on the central print server






G2 0 0 9

Illus. 11

In this example, the central print server is named printserver1 .

Terminal server

With terminal session logon the users shall get the printers on the central print server.

This is done by .print AutoConnect.

– On the terminal server open the AutoConnect configuration with

START¡ PROGRAMS¡ .PRINT ENGINE¡ AUTOCONNECT and enter the following

settings in the MAP ADDITIONAL PRINTERS tab (Illus. 12):

* * \\printserver1\DeskJet

* * \\printserver1\HPColor

printserver1 is the print servers name. DeskJet and HPColor are the printer

share names.

– Confirm with APPLY.

Illus. 12

Illus. 11 MMC: printers on the central print server assigned to a ThinPrint Port

Illus. 12 AutoConnect configuration on the terminal server:

printer shares to be connected



Appendix


© T

h i n P r i n t

A G 2 0 0 9

The users will see the printers in Illus. 13 in their terminal sessions.

Illus. 13

Print test

Now test the .print Client Gateway installation. Print from within a terminal session

using the printers created by AutoConnect.

Appendix

Special case: only 1 Client Gateway per Port

If only one Client Gateway per ThinPrint Port is used of printing, that Gateway can

be set in the registry for each ThinPrint Port. In this case, the printer name no longer

needs the IP address and/or client name; the ID is sufficient. For example:

HP DeskJet#:1

– To do this, open the registry key on the central print server

hkey_local_machine\ system \ currentcontrolset \ control \ print \ monitors\

thinprint port

and then the key with the name of each ThinPrint Port.

Add the value Host with the data type REG_SZ and enter the IP address of

each respective ThinPrint Client Gateway as value data – in our example:

192.168.131.125

How can I suppress incorrect print jobs?

Environment

■ Server central

■ Satellite offices with local print server (and own administrator)

■ Local print server serves as .print Client Gateway

Illus. 13 Printers in a terminal session



Appendix



G2 0 0 9

Scenario

The local administrator deletes printers on the local print server without informing the

central administrator; or, a printer is configured with an incorrect printer ID on the

central server.

What happens? .print print jobs that are sent to a printer which no longer existsor to an incorrect printer ID on the .print Client Gateway are rerouted to the “current

printer” listed in .print Clients Service Windows. If printout of the “wrong documents”

from the “current printer” is not desired, unwanted print jobs can be deleted auto-

matically.

Solution

Create a printer that refers to nul: on the .print Client Gateway and set it as “current

printer”.

Procedure8

1. Open the Printers panel from START(¡ CONTROL PANEL)¡ PRINTERS AND FAXES.

2. Do not select a printer. Select FILE¡ SERVER PROPERTIES.

This opens the window PRINT SERVER PROPETIES (Illus. 14).

3. All available printer ports are listed on the PORTS tab. If a “NUL:” port is

already available, the panel can be closed. Otherwise, the port must be cre-

ated using the ADD PORT button (Illus. 15).

4. Mark the LOCAL PORT, and click NEW PORT.

Illus. 14

8 with Windows 2003 as example

Illus. 14 Adding a printer port



Appendix


© T

h i n P r i n t

A G 2 0 0 9

Illus. 15

5. Enter NUL as port name (Illus. 16).

Illus. 16

6. Associate an unused printer with the port “NUL:” - for example, LEXMARK

OPTRA (Illus. 17).

7. Close all dialogues with OK/CLOSE.

Illus. 17

8. Set this unused printer as “current printer” in .print Client (Illus. 18).

Illus. 15 New “local-

port” port

Illus. 16 Port name: NUL:

Illus. 17 Associating an unused printer with the NUL: port



Appendix



G2 0 0 9

Illus. 18

Addit ional sources

■ At www.thinprint.com/ ¡ PRODUCTS¡ OVERVIEW¡ < product name> you will

find the user manuals for the server and client components of ThinPrint .print.

■ At www.thinprint.com/ ¡ SUPPORT¡ WHITE PAPER DOWNLOAD you will find

additional documentation on ThinPrint.

Abbreviations

ID Identification (number)

IT Information technology

LAN Local Area Network

LPT Windows Lineprinter port

NAT Network Address Translation (“IP masking”)

Output Gateway ThinPrint Output Gateway

TCP/IP Transport Control Protocol / Internet Protocol

TP ThinPrint

WAN Wide Area Network

Win32 Windows 2000, XP, 2003, and Vista

Illus. 18 Defining an unused printer as “current printer”





Documents

Client Gateway Windows En