Table of Contents
Advertisement
NetWare Configuration
Configure Using NetWare 4.x NetWare Directory Services
Overview
NetWare Directory Services (NDS) offers a different, more advanced
approach to network management than previous NetWare versions. Gener-
ally, 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 on individually defined physical sites. The result is
greatly improved print server setup and management.
NetWare 4.x also provides backward compatibility for 2.x, 3.x and 4.x print
service in Bindery emulation.
The Directory Information Base (DIB) is used to store information about
servers and services, users, printers, gateways, etc., and is a distributed
database, allowing access to data anywhere on the network wherever it is
stored.
NetWare versions prior to 4.x provide the same data found in the DIB but
the data is stored in the NetWare Bindery. 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. 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.
3-36 NetWare Configuration
Advertisement
Table of Contents
Troubleshooting
