
ThinPrint Connected Gateway
SEH TPG as a ThinPrint Gateway Technical Information 15
© Cortado AG 2012
■ Print data with the ID 1 is for Lexmark T644 and is sent from the central print
server to the TPG60 without encryption because its server-side printer (Lex-
mark T644#192.168.149.62:1) is connected to the “ThinPort” (Illus. 15).
■ Print data with the ID 2 is for HP Color LaserJet and is sent from the central
print server to the TPG60 with encryption because the server-side printer (HP
Color LaserJet 3600#192.168.149.62:2) is connected to the “SSL” port
(Illus. 15).
Done!
Next step? Try renaming the printers on the central print server by replacing the
IP address with the TPG’s host name (see also Illus. 4, Page 7
). First, though, you
must disable V-Layer for both printers (Illus. 12) and enable V-Layer after this con-
figuration.
ThinPrint Connected Gateway
As an option, you could use the ThinPrint Connection Service with your TPG. This
can be useful in masked networks
4
and certain firewall restrictions.Unlike the usual
direction of communication, the Connected Gateway also allows connections from a
remote location to the central server and therefore enables the TPG60 to be
addressed via TCP/IP, even in masked networks. The Connected Gateway also stabi-
lizes the transmission of print data, even during connection breaks of up to 90
seconds. It is a separate product; on the server, a Connection Service installation is
necessary. On the client side, a ThinPrint Client is assumed, such as is integrated in
the TPG.
In the ThinPrint configuration of the TPG, you can select C
ONNECTION SERVICE from
the menu (Illus. 20).
Printer
Printer ID in
the TPG60
Name of the native printer
on the server
Lexmark T644 1 Lexmark T644#192.168.149.62:1
HP Color LaserJet 3600 2 HP Color LaserJet 3600
#192.168.149.62:2
4 = Networks with Network Address Translation (NAT), which is mainly supported by routers
Comentários a estes Manuais