Overview Of Ipx Printing To The Fiery X2 - Fiery X2 Administrator's Manual

Table of Contents

Advertisement

4
4-3 Tips for experts—IPX networks
The Fiery X2 looks for print jobs on one NetWare print server per bindery server.
Each print server can store jobs for any queue on the Fiery X2.
Windows 95 workstations (whether a Novell server is present or not) can use IPX/SPX
protocols for communicating with the Fiery X2 directly to run the Fiery utilities.

Overview of IPX printing to the Fiery X2

NetWare file servers support the creation of print queues, which are storage areas for
print jobs. When a client on a remote computer decides to print, the job is directed to
a print queue on the NetWare file server and spooled to the NetWare server disk,
freeing up the client workstation.
The queues on the NetWare server must be named to match the Direct connection,
Hold queue, and Print queue on the Fiery X2. The NetWare queue names should be
given an extension corresponding to the Fiery X2 printing connection, as follows:
_print
_hold
_direct
The extensions must be all lowercase and in English.
N
:
OTE
There is no need to rerun Setup when adding or removing a NetWare queue; however
you should reboot the Fiery X2 after a queue is created or removed.
When the Fiery X2 is configured to connect to a NetWare server, it polls the NetWare
server for jobs in each of its queues. If jobs are found, they are transferred over the
network to the matching connection: Print to Print, Hold to Hold, Direct to Direct.
While a job is processed and printed, a record of the job is being created. You can
access the Job Log containing these records at any time.

Advertisement

Table of Contents
loading

Table of Contents