Digital Equipment RapidPrint 500, Reference Manual

Page: 79 / 192

NetWare Host Setup Access Lists
9 - 1
9 - NetWare Host Setup
This chapter covers NetWare host setup for printing.
NetWare print queues may be configured using EZCon (the recommended method), PCONSOLE,
or QINST. The method that you use to set up NetWare print queues will be determined by the ver-
sion of NetWare that you are using and whether you use Bindery Emulation or NetWare Directory
Service (NDS). If you are running NetWare version 4.0 or greater, refer to the
Creating NDS Print
Queues section. If you are running versions 2.x, 3.x, or version 4.0 with Bindery Emulation, refer to
the Creating Bindery Print Queues section.
EZCon and QINST are all provided on the distribution CD-ROM. See the CD-ROM booklet and
README files for more information on installation and use.
NOTE: To use EZCon, NetWare users must be running Windows version 3.1 or later with
the NetWare VLM or a Winsock-compliant IP stack.
9.1 Access Lists
By default, the RapidPrint 500 will only scan local file servers (file servers one hop away) for print
queues to service. File servers on non-local Ethernets, such as those with an IPX router between
them and the RapidPrint 500, can be scanned for print queues using the following command:
Figure 9-1: Enabling Non-local File Servers
To enable scanning for jobs on all file servers in the extended network, replace the file server name
with the keyword All.
NOTE: On an extended wide or local-area network with many file servers, specifying All
can severely impact the time between jobs and the overall printing performance.
9.2 Printing
The RapidPrint 500 can process NetWare print jobs either as a printserver (pserver) or via rprinter.
When using the pserver method, the RapidPrint 500 logs into a file server and then queries the
server for pending print jobs that it can service. When using the rprinter method, the RapidPrint
500 dedicates the printer to a particular file server; the printer is not usable by other file servers or
protocols. The significant benefit of the rprinter method is that rprinter does not use a login slot on
the file server (pserver does).
The pserver login uses the RapidPrint 500’s name and the login password to log into the file
server. If the default login password is changed, NetWare print queue setups must also be
changed to reflect the new password.
Local>> DEFINE PROTOCOL NETWARE ACCESS fileserver
Local>> INITIALIZE DELAY 0