User manual

Introduction

Connection Service.fm Manual 5

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

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

The ThinPrint Client installed there receives all print data, decompresses and

decrypts it

and then distributes it conventionally through the office network. Here

again, NAT poses no problem. The Connection Service resolves that issue: The Thin-

Print Client connects to the Connection Service, therefore establishing a connection

through which print jobs can be sent despite NAT.

This scenario can be used in more than just the Windows world. All necessary

printers 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 cre-

ated on the central print server using the ThinPrint Management Center.

2 Under Windows, it can also render the data.