Printronix P5000LJ User Manual
Bindery PSERVER Setup (Netware 3.x, 4.x, and 5.x)
231
20. Select the “Define additional properties” and click the “Create” button.
21. Click “Assignments” in the dialogue that pops up, and then click the
“Add...” button.
22. Select the printer you created earlier.
23. Click “OK” to assign this printer to this print server.
24. Click “OK” to close the printer servers details dialogue and make the
changes permanent.
25. Physically re-power the printer to make the new settings take effect.
Bindery PSERVER Setup (Netware 3.x, 4.x, and 5.x)
A Bindery PSERVER setup is possible under Netware 3.x, Netware 4.x and
Netware 5.x. If you are using Netware 4.x or 5.x, Bindery emulation is
required. Please consult your Novell manual on how to set up Bindery
emulation. A Bindery setup using PCONSOLE in Netware 3.x is described in
“NetWare Version 3.x RPRINTER Setup” on page 210. The setup using
PCONSOLE in Netware 4.x is described in “NetWare Version 4.x and 5.x
RPRINTER Setup” on page 213.
Netware 5.x. If you are using Netware 4.x or 5.x, Bindery emulation is
required. Please consult your Novell manual on how to set up Bindery
emulation. A Bindery setup using PCONSOLE in Netware 3.x is described in
“NetWare Version 3.x RPRINTER Setup” on page 210. The setup using
PCONSOLE in Netware 4.x is described in “NetWare Version 4.x and 5.x
RPRINTER Setup” on page 213.
Referencing A Bindery Queue In NDS
(Netware 3.x, 4.x, and 5.x)
(Netware 3.x, 4.x, and 5.x)
To reference a Bindery queue when you perform your PSERVER setup in
NDS, you create a PSERVER object for the NIC on the file server where the
Bindery queue resides. This is important because to service the queue, the
NIC must log on to the queue’s file server. Since the queue is not an NDS
queue, the NIC cannot log in under NDS, so it must log in under Bindery.
NDS, you create a PSERVER object for the NIC on the file server where the
Bindery queue resides. This is important because to service the queue, the
NIC must log on to the queue’s file server. Since the queue is not an NDS
queue, the NIC cannot log in under NDS, so it must log in under Bindery.
This only works if there is a valid PSERVER object on the file server. This
PSERVER object must have the same name that was used for the NDS
setup. By default, this will be “
PSERVER object must have the same name that was used for the NDS
setup. By default, this will be “
M_xxxxxx
” where “
xxxxxx
”
equals the last
six digits of the print server’s Ethernet address found on the bottom of the
device (e.g., M_091C1A). This PSERVER object does not need to have any
printers or queues assigned to it. Also, when referencing a Bindery queue in
NDS, the Novell Mode on the NIC must be set to “auto” so that both NDS and
Bindery logins are possible. See “Setting The NIC Context (NDS)” on page
227.
device (e.g., M_091C1A). This PSERVER object does not need to have any
printers or queues assigned to it. Also, when referencing a Bindery queue in
NDS, the Novell Mode on the NIC must be set to “auto” so that both NDS and
Bindery logins are possible. See “Setting The NIC Context (NDS)” on page
227.
Note
The name you use here must match the name stored on the NIC. This
name can be found by using the
name can be found by using the
list pserver
command. See “List
Commands” on page 254 for more information.