Novell Client 2.0 SP2 for Linux Readme

1.1 System Requirements

The Novell® Client™ 2.0 for Linux requires workstations running one of the following:

1.2 Installation using ncl_install

During installation of novell-client using ncl_install, you are prompted to download the appropriate packages before it is actually installed. This is because zypper is used instead of rpm for installation.

1.3 Installing From a Directory With Spaces In the Name

The Novell® Client™ for Linux 2.0 cannot be installed from a directory that has spaces in the name. For example, installing from /home/user/NovellClientForLinux will work, while installing from /home/user/Novell Client For Linux will fail.

1.4 Install Script Contains Error Message But Still Installs Correctly

When running the installation script, you might see the following error message, but the Novell Client for Linux installs correctly anyway.

ERROR: Module novfs is in use.

1.5 Installing from CD

When using the Add-on Product feature in YaST to install the Novell Client for Linux, the install process displays an Import Untrusted GnuPG Key error.

Select Import to import the key. The install will complete successfully.

2.1 Be Sure to Apply the Latest SLE 11 Patches

Before you upgrade a Novell Client 2.0 for Linux installation on a SUSE Linux Enterprise 11 workstation, be sure that the workstation is running SUSE Linux Enterprise 11 with the latest patches applied.

3.1 Integrated Login Does Not Work if Auto Login is Enabled

If you have already configured the Integrated Login feature and then enable GDM to automatically log in a user, Integrated Login will not work.

3.2 Integrated Login Does Not Work as CASA service does not start

On SLED 11, after installing and enabling CASA, the CASA service does not start automatically. To verify if the CASA service is running, issue the following command:

/etc/init.d/micasad status

If the status returned is unused, you can manually start the service using the following steps by logging in as root:

After a system reboot, the above mentioned steps must be followed to restart CASA service. Integrated login works as expected after the CASA service is up and running.

3.3 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.

3.4 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

3.5 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^*.

3.6 Some Login Script Commands Not Implemented in Novell Client for Linux

The following login script commands are not currently 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)

3.7 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”

3.8 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.

The following should appear:

novell-xregd
novfs_ST
novfsd

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

/opt/novell/ncl/bin/ncl_control restart

If either of these commands displays any errors, restart the Linux machine.

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

3.9 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.

3.10 Login Script Does not Run

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

3.11 Logging in with a Password Policy

If you log in with a password policy, grace login attempts do not decrement.

4.1 On clicking Novell Services, multiple nautilus windows open

When the novell-nautilus-plugin services is exercised by clicking the Novell Services button on the nautilus toolbar, two windows are opened. One is for browsing eDirectory objects and the other is for browsing the file system objects on the connected servers.

4.2 Launching nautilus file manager for mounted servers

You can launch nautilus file manager window for mounted servers on the available connections directly by using the following command:

nautilus nvvfs://

Similarly, you can launch the eDirectory browser directly by using the following command:

nautilus nds://

4.3 Unable to Delete Folders After They Are Copied to Another Server

In SLED when running the GNOME* desktop, you can’t delete a folder if it has been copied from one server to another and then copied back to the original server if you use the GUI. For example, if you copy and paste a folder from Server A to Server B, delete the original folder from Server A, copy the folder from Server B back to Server A, and then attempt to delete the folder from Server B, an error occurs and the folder cannot be removed. To solve this problem, delete the folder using a terminal.

4.4 Unable to Delete Files on GNOME

Users are unable to delete files on GNOME if the trash folder is set up at the root of an OES or NetWare® server volume where the users don't have rights. Users are then unable to delete files in subdirectories on the OES or NetWare servers where they do have the proper rights to create/modify/delete files. The following is also true:

A patch for this defect will be posted.

4.5 Files Are Left Open on GNOME

GNOME is leaking file handles, which is causing files to be left open.

A patch for this defect will be posted.

4.6 Nautilus and FAM Generate High Amounts of Traffic

Nautilus and FAM generate high amounts of traffic during file operations and severely impact the performance of the Novell Client for Linux.

A patch for this defect will be posted. With this patch applied, a polling interval can be configured to improve overall performance of file I/O using NCL.

4.7 Cannot See Cluster Virtual Server Objects

Users cannot see cluster virtual server objects through SLP from the Server button. To resolve this, use the IP address instead of the server name.

4.8 Accessing The Same File from Multiple Workstations

If you log in to the same NetWare server from two different workstations (such as SLED) and open the same file on both workstations, you might receive an error when you try to save the file from one of the workstations.

If you save the file again, the file will save properly.

4.9 File Locking Issue

If you open the same document from different workstations, you should be notified that the second file you open is in use, and the document should be opened as read only.

4.10 Canceling a File Copy During a Simultaneous Copy

Cancelling a file copy during another simultaneous copy results in an error message saying that the file cannot be deleted because you do not have permissions to modify the file’s parent folder.

Click Cancel to stop the copy.

4.11 Opening or Saving Files in a Directory With Only Read, Write, and File Scan Rights

If you try to open or save a file in a directory with only Read, Write, and File Scan rights, you might see filter selection or general input/output error messages (which prevent you from opening or saving the file). In most cases, giving the directory Create, Modify, and Erase rights, in addition to the Read, Write, and File Scan rights, will let you open or save the file.

5.1 Closure of connections during desktop logout

If there are existing connections opened by Novell Client after a desktop logout, these connections are not automatically closed.

5.2 All Connections lists only Available Connections

When a user clicks Novell Services icon on nautilus tool bar, the All Connections icon lists only the set of available connections. It does not show the connections listed by SLP.

5.3 FAM/iNotify Causes File Copy to Hang

During a file copy, the workstation hangs because of issues with FAM/iNotify. These issues are not directly related to Novell Client, but happen because of the way FAM validates requests. This means that in order to complete a file copy, you must remove the FAM service.

To remove a service from a runlevel, you must either delete the symbolic links manually from the folder with all the scripts for the desired runlevel, or run the following command:

insserv -r fam

This command removes the service from all runlevels.

5.4 Invalid Connections Displayed

Occasionally, non-authenticated (invalid) connections are erroneously displayed in the /var/opt/novell/nclmnt directory. When the server name is displayed along with the volumes and files, this indicates an authenticated (valid) connection.

5.5 Users Not Prompted to Change an Expired Password if it Has Expired

When a user’s password expires, the user is informed of the amount of grace logins remaining but is not prompted to change the password. When the grace logins have been exhausted, the user cannot login.

An administrator must update the password using Novell iManager or ConsoleOne®.

5.6 Default Values in the Novell Map Directory Dialog Box

When you use the Red N menu to create a map drive, there is no default value for the Enter the name of the link or select a drive letter option. This field is left blank because with the Novell Client for Linux, you can use either a driver letter or a name.You can use the Novell Client for Linux Configuration Wizard to specify the first letter to use when creating symbolic links to network resources. To do this, click the Red N menu, then click System Settings, select Map, then click Start Wizard. Select the driver letter you want from the First Network Drive drop-down list, then click Next > Finish

5.7 Novell Services Button

After the Novell Client for Linux is installed, a Novell Services button appears in the Nautilus file browser. Clicking this button displays a list of all available Novell connections and all current Novell connections. If you are using the Konqueror file browser, click the Novell Network icon on the Navigation Panel to display Novell connections (press F9 to display or hide the Navigation Panel).

5.8 Purging or Salvaging Files in a DFS Junction Target Location

With the Novell Client 2.0 for Linux, you cannot purge or salvage files in a Distributed File Services (DFS) junction target location.

As a workaround, you can use either the Novell Client for Windows 4.91 SP4 or NetStorage to purge or salvage files. You can also use the Files and Folders plug-in to iManager 2.7 to manage deleted files. In iManager, select Files and Folders, then click Deleted Files. Search for the directory where the file existed when it was deleted to get a list of the deleted files. You can see only those files you have permission to access. Select the deleted file, then click Salvage or Purge.