Secure Global Desktop 4.40 Administration Guide
> Printing
> Printing From a Microsoft Windows NT 3.51 Application Server
Printing From a Microsoft Windows NT 3.51 Application Server
You can only print from a Microsoft Windows NT 3.51 application server
if the Windows application object is configured to use the Citrix ICA Windows Protocol.
You also have to configure an LPR-compatible TCP/IP printer on the application server as follows:
- Log in to the application server as a Windows administrator or a member of the
Administration group.
- In Windows Control Panel, double-click Network.
- Click Add Software.
- In the Network Software list, click TCP/IP Protocol and Related Components.
- In Components, select the TCP/IP Network Printing Support check box.
- Run Printer Manager on the application server to configure the new printer.
- On the Printer Menu, click Create Printer.
- In the Driver box, click the printer model and manufacturer that
most closely matches the client device's default printer. If there is
no close match, choose a PostScript printer.
- Deselect the Share This Printer On The Network check box.
- In the Print To box, click Other.
- In the Available Print Monitors list, double-click LPR Port.
- In Name Or Address Of Server Providing lpd, type the full DNS name of the primary SGD server in the array.
- In Name Of Printer Or Print Queue On That Server, type
tta_printer
.
Limitations
Printing from a Windows NT 3.51 application server has the following limitations:
- No multiple printer support - you can only print
to the client device's default printer. It is not possible for users to select a printer.
If a user needs to print to a different printer, they have to log out of SGD,
change their default printer, and then log in again.
- Print jobs might be deleted - when a
print job is transferred from the application server to an SGD
server, the user's SGD name is needed to identify which
client device to sent the print job to. With Windows NT 3.51 there is no direct way
to associate print jobs with SGD users. If SGD
cannot identify which user has printed a particular job, the print job is deleted.
This might happen, for example, if two users log in to the application server with the same name.
- Distributed printing is not available - all print jobs
are directed through the primary server in an SGD array.
Copyright © 1997-2007 Sun Microsystems, Inc. All rights reserved.