Ricoh AP1400/AP2000 manual

7.Enter the name of the print server in the Print server field and press the ENTER key.

Note: The print server name is printed under the Novell Network Information on the Status and Configuration report. The factory default name is RDP_XXXXXX (XXXXXX is the serial number of the unit).

8.Press the ESC key to move to the New printer field. Enter a name and press the ENTER key.

9.Press the ESC key to move to the New printer queue field. Enter a name and press the ENTER key.

10.Press the ESC key to move to the Printer type field and press the ENTER key. From the list of printer types, select Other/Unknown and press the ENTER key.

11.When you are finished, press the F10 key to save the configuration.

12.Repeat steps 5 through 10 for each file server that the printer server services.

13.To view, add, delete, or modify print servers or queues after the initial setup, select either the Print Queues or Print Servers option on the Available Options screen.

4.3Configuring the Network Interface Board in NetWare Directory Services

NetWare Directory Services (NDS) offers a different, more advanced approach to network management than previous NetWare versions. Generally, it stores and tracks all network objects. As a rule, all 4.x servers must have NDS loaded in order to function. In this way, every NetWare 4.x server is a Directory server, because it services named Directory objects such as printers, print servers and print queues. With the appropriate privileges, you can create a print server object, which, once configured in its context (or location) on the network, eliminates the cumbersome setup of print servers on every network server. NDS provides true enterprise networking based on a shared network database rather than a individually defined physical sites. The result is greatly improved print server setup and management.

The Directory Information Base (DIB) is used to store information about servers and services, users, printers, gateways, etc. It is a distributed database, allowing access to data anywhere on the network wherever it is stored. Pre-4.x NetWare versions provide the same data found in the DIB but the data is stored in the NetWare Bindery. The DIB was designed with more flexible access, more specific security, and, since it is distributed, it was designed to be partitioned. The Directory uses an object-oriented structure rather than the flat-file structure of the Bindery, and offers network-oriented access, rather than server-oriented access found in the Bindery.

The Directory is backward-compatible with the NetWare Bindery through Bindery emulation mode. Section 4.2 describes Print Server Operation with a 4.x NetWare system in bindery emulation mode. When Bindery emulation is enabled, Directory Services will accept Bindery requests and respond just as if a Bindery existed on the NetWare server being accessed. Be aware that information obtained from the Bindery query may not be stored in the server since the Directory is a partitioned and distributed database. Even though the NetWare 4.x server is not operating from a Bindery, the applications making Bindery requests will not know the difference.

Chapter 4 - 7