##
Login Issues

###
Integrated Login Not Provided

This version of Novell Client for Linux does not provide an integrated login experience with the initial workstation login screen. Users who have migrated from Windows* desktops to Linux do not have the same experience and must log in to the workstation and then log in to the network using the Novell Client for Linux.

###
CN User Identifier Variable Displays the Wrong Information

If the CN user identifier variable is used in the login script, it displays the wrong information if the Other Name field is filled in. This results in drive mappings not being made. Depending on how the variable login script is used, errors might occur.

###
Supported MAP Command Login Script Syntax

The following is a sample of valid login script syntax for the MAP command:

`map my_projects:=server/vol:path`

`map f:=server/vol/path`

`map f:=vol:path`

`map f:=vol:\path`

`map display on f:=server\vol:path`

`map display off f:=server\vol:path`

`map "my projects":=server/vol:path`

`map f:=\\server\vol\path`

`map *1:=server\vol:\path`

HINT: Linux does not support backslashes on the command line. UNC names can be written with forward slashes. For example, map f:=//server/vol/path

###
Map Command Differences from Windows Behavior

The MAP command works differently based on whether you run it from a login script or at the command line. The following is a list of differences in how the MAP command behaves at the command line in Linux versus how it works at the command line in Windows.

- UNC names must be designated with forward slashes instead of backslashes
- Separate map requests on a single line with a comma instead of semicolon.

  `map j:=server1/vol:/path;server2/vol:path`

- `map errors on/off` is parsed but does not do anything
- `map ins j:=server/vol:/path` the `ins` is ignored
- `map root j:=server/vol:/path` the `root` is ignored
- `map change` is not implemented
- `map physical` is not implemented

###
Login Script Commands Not Implemented in Novell Client for Linux

The following login script commands currently are not implemented in the Novell Client for Linux.

  DRIVE
  MAP S1:=server/vol:/path (Search drives are not implemented but default to creating symbolic links S1..S16)

###
IF Statement Does Not Work without the THEN Statement

In Linux, the IF statement cannot be used without the THEN statement. This is not true in Windows. Hence, the following statement does not work in Linux:

    IF MONTH="07"

    WRITE "This is July"

To resolve this, include the THEN statement each time.

    IF MONTH="07"

    THEN WRITE "This is July"

###
Cannot Log In

If you are experiencing problems logging in with Novell Client for Linux, a first step is to check that the needed packages are all running. At the Console Terminal, type ps -A | grep nov.

IMPORTANT: You must have root rights in order to run this command.

The following should appear:

novell-xregd
novfs_ST
novfsd

If one of these processes is not listed, restart Novell Client for Linux.

`/opt/novell/ncl/bin/ncl_control restart`

If either of these commands displays any errors, you will need to restart the Linux machine.

In addition, `/opt/novell/ncl/bin/ncl_control status` shows whether the NCL drivers are loaded properly or not.

###
Login Requires a Server Name for Trees Not Registered with DNS

If you are logging in to a tree that does not have a registered DNS name, you must enter the server name in the Server field to log in.

###
PAUSE Command in Login Script

When using login scripts that contain a PAUSE command, the Close button activates when the script is paused. If the user closes the login script window while the login script is running but paused, then processes are left open. To close the processes, restart the workstation.

###
Login Script Does not Run

There are rare occasions when the login script does not run. To solve this, log in again to rerun the login script.