Pioneer DRM-6NX manual NetWare NCP, Specific Distinguished Names

NetWare (NCP)

Specific Distinguished Names

Names in the Directory tree have two name types: typeful or typeless. A typeful name includes the name types (OU,O, etc.) when identifying the distinguished name of the object. A typeless name excludes the name types. You can use either syntax when specifying the parameters.

Example 1 (NDSServerContext parameter syntax): Typeful distinguished name: OU=Corp.O=Acme Typeless distinguished name: Corp.Acme

Example 2 (NDSAdminName parameter syntax): Typeful distinguished name: CN=Admin.O=Acme Typeless distinguished name: Admin.Acme

Objects in an NDS Directory Tree

NOTE:

7Display Details in NWAdmin to verify the syntax of the

NDSServerContext and NDSAdminName parameters

Deleting the Server Object

If the NW Admin's partition manager is used to delete the server object from your NDS tree, turn off the unit (DRM-6NX) for a minimum of 5 minutes before deleting the object. If you do not turn off the server before attempting to delete the server object, your client workstation will hang and you will have to reboot the PC. However, when using NDS manager this is not needed.

Installation Errors in NetWare NDS

Any errors which may occur when installing your DRM- 6NX in a NetWare NDS network, are written to a file named logfile.txt located in the System / Server Properties folder. Display the log file through the Event Log page within the DRM-6NX web interface.

The table comprises a summary of error messages:

Error	Description
Installation failed:	The server could not find the NDS tree.
NDS tree not found	Verify the spelling
Installation failed:	The server could not find the user object
Administrator object	specified in the NDSAdminName parame-
missing	ter. Verify that the proper format is used
Installation failed:	e.g. admin.acme. Verify the spelling
	The password supplied in the
Administrator pass-	NDSAdminPassword password could not be
word is incorrect	used to login as the user in the
	NDSAdminName parameter.
Installation failed:	Verify the spelling
	The context specified in the
Server context not	NDSServerContext parameter was not
found	found. Verify the spelling
Installation failed:	The specified user in the
Insufficient rights to	NDSAdminName parameter does not have
create server object	sufficient rights to create the server
Installation failed:	object in the specified context.
	You have tried to install the server on
NDS Server object	top of an existing server object. Set the
already exists	NDSInstall parameter to forced to
Installation warning:	overwrite the existing object.
	The administrator who is trying to install
Could not extend	the server has insufficient rights for
NDS Schema. User	adding the schema extension.

xxxxxdoesn't have Specify a NDSAdminName with

SUPER-VISOR rights Supervisor rights to the [Root] object. to the [Root] object.

Installation warning:

Could not extend

NDS Schema (class 1)

These errors are the result of insufficient Installation warning: rights of the administrator trying to install Could not extend the server.

NDS Schema (class 2) Specify a NDSAdminName with Supervisor rights to the [Root] object.

Installation warning: Couldnot extendNDS Schema (attribute)

NOTE:

7If logged in as Administrator, the NDS error message “Insufficient rights” indicates that NDS has been corrupted. You must repair or rebuild NDS. Repair NDS by entering the LOAD DSREPAIR command at the server console.

22

<DRB1239>