Bindery PSERVER Setup (Netware 3.x and Netware 4.x)
21.Click on “Assignments” in the dialogue that pops up, and then on the “Add...” button.
22.Select the printer you created earlier.
23.Click on “OK” to assign this printer to this print server.
24.Click on “OK” to close the printer servers details dialogue and make the changes permanent.
25.Physically
Bindery PSERVER Setup
(Netware 3.x and Netware 4.x)
A Bindery PSERVER setup is possible under both Netware 3.x and Netware 4.x. If you are using Netware 4.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 81. The setup using PCONSOLE in Netware 4.x is described in “NetWare Version 4.x RPRINTER Setup” on page 86.
Referencing a Bindery Queue in NDS (Netware 3.x and Netware 4.x)
If you would like to reference a Bindery queue when you perform your PSERVER setup in NDS, you must create a PSERVER object for the PrintNet on the file server where the Bindery queue resides. This is important because in order to service the queue, the PrintNet must log on to the queue’s file server. Since the queue is not an NDS queue, the PrintNet can’t login under NDS, so it must login under Bindery.
This will only work 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 “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 PrintNet must be set to
107
