Konica Minolta kn303ev2 User Manual

Konica Network Interface Card INSTRUCTION MANUAL  6-9

■

Novell NetWare 4.x can operate in two modes, NetWare Directory Service (NDS) and Bindery Emulation

Service (Bindery Emulation).  Bindery Emulation and NDS will be executed simultaneously.  It is also

possible to set up the print server so that it operates only in Bindery Emulation mode or in NDS mode.

The print server set up for NDS mode will also service the file server of an old version operating in Bindery

mode.

If NDS is not set up properly for the print server and Bindery Service mode is not operating,

the print server cannot find the file server and Novell NetWare protocol will be indicated as

inactive in the Status Page.

●

NDS

Novell Directory Service (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 printing systems,

print server 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 net-

work server.

NDS provides true enterprise networking based on a shared network database rather than individu-

ally defined physical sites.  The result is a greatly improved print server setup and management.

Bindery emulation

NetWare 4.x also provides backward compatibility for 3.x and 4.x print service through Bindery emu-

lation.

The Directory Information Base (DIB) is used to store information about servers and services, users,

printing systems, 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.

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 oper-

ating from a Bindery, the applications making Bindery requests will not know the difference.