Queue server mode

In this mode, the hardware print server directly accesses the print queue using NetWare Core Protocol calls. In NetWare 3, this mode was faster than remote printer mode, but the improved performance of the NetWare Services PSERVER has minimized this distinction.

Queues created in the bindery context can be seen by both NetWare Directory Services and bindery users, so both types of users can access these hardware print servers.

Network-direct print devices developed before NetWare Services are designed to work well with the NetWare bindery. When used in queue service mode, some of these products present the following set of common issues of concern to the network supervisor within a NetWare Services environment.

• Some network-direct print devices and their installation programs are designed to look in the bindery for network printing information. In order for these devices to see binderies and queues, they must be in the same bindery context as these printers and queues.

• The queue's volume must be located on the same server as the queue.

• Queues serviced by network-direct printers must be created in the bindery context where the queue server is defined. The bindery context tells the NetWare server which Directory Services objects should be visible as bindery information.

• Queue users should be in the same bindery context as the queue.

• In NetWare 3, print server configuration files for bindery printers are located in the SYS:SYSTEM directory. In NetWare Services, these files have been replaced by attributes of the print server. Because most network-direct print devices are designed to access information from the bindery and are not Directory Services aware, you must create print device configurations in the bindery emulation mode of PCONSOLE in order for the configuration files these devices require to be created.

• Some of these direct-connect devices need to be configured within the 16 printer limitation for NetWare 3 print servers.

  When using these devices in remote printer mode, you should reserve printer numbers 0-15 for them.

• NetWare 3 created the group EVERYONE by default. Some of the network-direct print devices assume that this group exists in NetWare Services. For these devices, make sure that group EVERYONE is a user of the affected queue. You may need to create this group in the context where the printer is defined before the device will be able to communicate with the network.

• Some network-direct devices require a running print server before you can configure for remote-printer mode.

  Because the communication protocol between print servers and network-direct devices running in remote printer mode did not change in NetWare Services, the running print server can be a NetWare for UNIX 3 print server.

• Some of the utilities provided with these print devices can only be operated with the SUPERVISOR right and do not recognize Supervisor equivalents. You will need to log in as SUPERVISOR in bindery mode rather than logging in as ADMIN in Directory Services mode.

• Some devices include a remote printer configuration utility that requires you to complete duplicate configuration steps. In such cases, you should first define the remote printer in the NetWare Services PCONSOLE utility, and then define the printer again using the third party utility.

  As a result of these duplicate steps, you may end up with unused NetWare 3 printer configuration files on the NetWare Services server.