Filter
Top Products
Chapter 6 Novell Host Configuration (10/100Base-T)
108
“auto” so that both NDS and Bindery logins are possible. See “Setting the
PrintNet NDS Context (NDS setups)” on page 102.
RPRINTER/NPRINTER Setup
(Netware 3.x and Netware 4.x)
This procedure associates an existing PSERVER with a remote PrintNet
acting as a RPRINTER/NPRINTER in a NetWare 3.x or Netware 4.x
environment. It is the PSERVER’s responsibility to get jobs from the
queue and to pass them off to the PrintNet acting as the remote printer.
Unlike a PSERVER setup, the PrintNet does not deal directly with the
queues.
NOTE: As a RPRINTER/NPRINTER, the print server does not use a
login ID. A non-PrintNet print server such as PSERVER.NLM or
PSERVER.EXE must be running for RPRINTER to operate. Also,
if the PrintNet loses a connection to a PSERVER, it will
automatically reconnect when that server becomes available
again.
The following steps assume that you have created a PSERVER object in
either Netware 3.x or Netware 4.x and have assigned printers and queues
to it. If you have not already done this, do it now. The setup is similar to
creating a PSERVER setup for the PrintNet, except that there are no
restrictions about which names may be used for the print server and
printer objects.
NOTE: Write down the printer number(s) assigned to the printer(s) you
are going to be using for this setup. You will need them in a later
step.
HTML Method
1. Load a PSERVER on your Netware 3.x or Netware 4.x file server
(i.e., issue a
load pserver
pservername
command on the file
server).
NOTE: If it is an NDS PSERVER on a Netware 4.x file server, you must
specify the PSERVER name and context for
pservername
. For
example:
load pserver .sales_ps.sales.microplex