Tarantella Administration Guide
> Printing
> Printing from a Microsoft Windows NT 4 application server
Printing from a Microsoft Windows NT 4 application server
The configuration needed to let users print from a Windows NT 4
application server depends on which of the following Windows
protocols you are using:
- Citrix UNIX Integration Services (UIS).
- Windows Terminal Services, or
- WinFrame/MetaFrame.
The configuration required for each of these protocols is described below.
Printing using the Citrix UIS or Windows Terminal Services Windows protocols
To print from an Windows NT 4 application server using either the Citrix UIS or
the Windows Terminal Services Windows protocol,
you have to configure an LPR-compatible TCP/IP printer on the application
server that you want to print from. To do this:
- Log in to the application server as a Windows administrator or a member of the
Administration group.
- In Windows Control Panel, double-click Network.
- In the Services tab, click Add to install the Microsoft TCP/IP service.
- Run the Add Printer Wizard on the application server to configure the new printer.
- When prompted, click Local Printer. Clear the Automatically Detect My Printer box.
- Click Create A New Port and then click LPR Port.
- In Name Or Address Of Server Providing lpd, type the full DNS name of the primary Tarantella server in the array.
- In Name Of Printer Or Print Queue On That Server, type
tta_printer
.
- When prompted, choose 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.
- When prompted as to whether the printer will be shared with other
network users, click Do Not Share This Printer.
Note The version of Windows Terminal Services supported by NT 4 is not the same
as the version supported by Windows 2000/2003 and so it requires the above configuration.
Printing using the WinFrame/MetaFrame Windows protocol
To print from an Windows NT 4 application server using the WinFrame/MetaFrame Windows protocol,
you have to configure a Tarantella printer on the UNIX server
running the ICA client and on the Windows application server you
want to print from. To do this:
- Configure a Tarantella printer on the UNIX application server
that runs the ICA client.
- Use Tarantella to log in to Windows application server.
Use the WinFrame/MetaFrame Windows protocol.
- Start the Add Printer Wizard.
- When prompted how the printer should be managed, click Network
Printer Server.
- In the Connect to Printer box, double-click the Client icon.
- In the Shared Printer list, double-click the printer you want to configure.
The name of the printer you need to select has the format
ip_address:#printer_name
, where ip_address is the IP address of the primary Tarantella server in the array and
printer_name is the name of the printer you configured on the UNIX application server.
- When prompted, choose 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.
Limitations when printing from a Windows NT 4 application server
You should note the following limitations of printing from a Windows NT 4 application server:
- 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 Tarantella,
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 Tarantella
server, the user's Tarantella name is needed to identify which
client device to sent the print job to. With Windows NT 4 there is no direct way
to associate print jobs with Tarantella users. If Tarantella
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 Tarantella array.
Next steps in configuring Tarantella printing