Fiery DocuColor 3535, Руководство по настройке

Страница: 33 / 116

2
2-9 Fiery on a NetWare network
You can give the NetWare queue names a specific extension corresponding to the Fiery
print connection, as follows:
_print
_hold
_direct
N
OTE
:
These extension names must be in English and in all lowercase letters.
You do not need to rerun Setup when you add or remove a NetWare queue; however,
you should restart the Fiery after you create or remove a queue.
When the Fiery 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 automatically transferred
over the network to the matching connection on the Fiery. For example, jobs from the
NetWare queue with the
_print extension are sent to the Fiery Print queue. 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.
Configuring a NetWare 4.x server for printing
The following sections explain how to set up a NetWare file server so networked users
can print to the Fiery from their workstations, and the Fiery can obtain print jobs from
the NetWare server.
For each NetWare file server that you configure, follow these general steps. More detail
is provided in subsequent sections and in your NetWare documentation.
• Make sure the server is connected to a functioning IPX network.
• Log in as the Supervisor on a Windows computer connected to the NetWare
file server.
• For NetWare 4.x installations, set up an NDS connection (see page 2-11 ).
• For NetWare 4.x in emulation mode, set the bindery context (see page 2-12 ).
• For NetWare 4.x in bindery emulation, set up a file server, print server, and print
queue for the Fiery (see page 2-12 ).
With bindery services, you can route all Fiery print jobs through the same NetWare file
server, or you can configure more than one file server to handle Fiery jobs.