Secure Global Desktop 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 application 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:

1. Log in to the application server as a Windows administrator or a member of the Administration group.
2. In Windows Control Panel, double-click Network.
3. Click Add Software.
4. In the Network Software list, click TCP/IP Protocol and Related Components.
5. In Components, select the TCP/IP Network Printing Support box.
6. Run Printer Manager on the application server to configure the new printer.
7. On the Printer Menu, click Create Printer.
8. In the Driver box, click the printer model and manufacturer that most closely matches the client device's default printer. If there's no close match, choose a PostScript printer.
9. Clear the Share This Printer On The Network box.
10. In the Print To box, click Other.
11. In the Available Print Monitors list, double-click LPR Port.
12. In Name Or Address Of Server Providing lpd, type the full DNS name of the primary Secure Global Desktop server in the array.
13. 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 Secure Global Desktop, change their default printer and then log in again.
• Print jobs may be deleted - when a print job is transferred from the application server to a Secure Global Desktop server, the user's Secure Global Desktop 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 Secure Global Desktop users. If Secure Global Desktop 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 a Secure Global Desktop array.

Copyright © 1997-2006 Sun Microsystems, Inc. All rights reserved.