Novell NetWare with NDS

LinkLaunch NT accepts several formats for a remote device name under NDS:

  1. Volume object

    BULLET.gif
Typed and typeless names are accepted

BULLET.gif At least one embedded dot (.) is required

BULLET.gif Leading and trailing dots are accepted, see below

Example:

LLNT \\.CN=server1_sys.OU=development.O=bgrove\joblog

  1. Directory Map object

    BULLET.gif
Typed and typeless names are accepted

BULLET.gif At least one embedded dot (.) is required

BULLET.gif Leading and trailing dots are accepted, see below

Example:

LLNT \\cdrommap.accounting.\medical

  1. server\volume

Example:

LLNT \\acctg\sys\data

For Volume objects and Directory Map objects, use a leading dot to indicate an absolute path. Otherwise, the object name is assumed to be relative to the current context. Trailing dots can be used to refer to the parent of the current context. The rules for leading and trailing dots are the same as for the 'CX' command. If LinkLaunch is having trouble finding the object, use typed names.

For all three formats, LinkLaunch NT will attempt a background authentication if the user is logged into the tree and the server is an NDS server. Otherwise, LinkLaunch will attempt a bindery login.

NOTE: Object names that contain spaces must be surrounded by double quotes.

See also:

Automatic Login/Logout for NetWare Servers