EFI KM-C1530 Configuration Manual page 35

2
2-11 Fiery X3e on a NetWare 4.x or 5.x network
Setting up an NDS connection
In NDS, all NetWare entities (objects) are organized in a hierarchical tree structure.
Objects have a name, properties, and a context that defines the location of the object
in the directory tree. For the Fiery X3e, you are mainly concerned with defining a
printer, a print server object, and one or more print queue objects. Objects are created
in NetWare administrator programs such as PCONSOLE, NETADMIN, or NetWare
Administrator.
The top-level tree object is known as the [Root] object. The name of the [Root] object
is also the name of the tree. Below the [Root] are other objects: either containers
(which consist of other objects) or leaf objects (which do not contain other objects).
Access to objects is controlled by rights that are defined as properties of each object.
Rights are established by network administrators.
Setting the NetWare 4.x bindery context
You can connect only one directory tree to the Fiery X3e. If you need to connect
additional NetWare 4.x servers, you can do so by using bindery emulation. You can
connect up to eight bindery servers to the Fiery X3e.
The file server you select must not be in the same tree as the one you selected in
N :
OTE
NDS Setup.
In order to set up the NetWare 4.x server in bindery emulation mode for printing to
the Fiery X3e, the network administrator must do the following:
• Determine the Directory Services path to the container in which the print server and
the print queue for the Fiery X3e will be created.
The container defines the "bindery context" for your network structure.
• Edit the network startup file to set the bindery context.
• Activate the new bindery context.