Notes on NDS names/logins when using EMSRV for NetWare (NDS)
-----------------------------------------------------------

RJS 20/5/98

EMSRV for NetWare (NDS) has extra functionality to use a
NDS login when authenticating to a NetWare 4.x server and
when using native password checking for client verification,
thus allowing it to run on a NetWare 4.x server when bindery
emulation mode is disabled. 

On NetWare 4.x we recommend that customers use EMSRV for
NetWare (NDS) rather than EMSRV for NetWare (Bindery), even
though the latter may be used when bindery emulation is
enabled.

When setting up EMSRV for NetWare NDS, the network administrator
should be familiar with NDS and in particular NDS names that can
be found in the NetWare 4.x documentaion which can be found
online at:

http://doc1.provo.novell.com/

There is also an excellent NDS Technical Overview at:

http://developer.novell.com/research/devnotes/1998/april/a3frame.htm


Network user object names may either be distinguished (they give the
path from the leaf object to the root object) or relative
distinguished to some point in the NDS tree (usually referred to as
a context). User object names that are used by EMSRV for NetWare
(NDS) for verification should be typeless names either relative to
the [root] context (the default) or some other NDS context
specified by option -SC (set context).

If the EMSRV for NetWare users are found in a container other than
[root], we advise the NetWork administrator to use the -SC option
to set the context to the container object containing the users.


