Novell Client for SUSE Linux Enterprise 11 SP1 Readme

June 2010

Readme has the following sections:

1.0 System Requirements

The Novell Client for SUSE Linux Enterprise 11 Service Pack1(SLE 11 SP1) requires workstations / servers running one of the following:

  • SUSE Linux Enterprise Desktop 11 (32-bit or 64-bit) or later

  • SUSE Linux Enterprise Server 11 (32-bit or 64-bit) or later

NOTE:It is recommended that you install all the latest patches on your system.

2.0 Login Issues

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

2.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:

  1. touch /var/run/

  2. /etc/init.d/micasad restart

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.

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

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

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

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

  • 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:/paththe ins is ignored

  • map root j:=server/vol:/paththe root is ignored

  • map change is not implemented

  • map physical is not implemented

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


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

2.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”

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

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

The following should appear:


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

rcnovell-xregd restart

This command stops and reloads XTier registry service that is needed by Novell Client for Linux daemon modules.

rcnovfsd restart

This command stops and reloads Novell file system kernel module and daemon modules of Novell Client for Linux.

Manually launch Novell Client tray application by running the command /opt/novell/ncl/bin/ncl_tray either on the command line of a terminal window or in Run Application utility that can be launched by pressing Alt-F2.

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

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

2.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.0 File and Folder Issues

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

3.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://

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

3.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:

  • There is no indication on the user’s desktop that items are in a Trash folder and can be permanently deleted.

  • As long as these files remain in a Trash-user folder on a remote file system, that system cannot offer any salvage or purge options because the files still remain in an UNDELETED state.

  • If additional files of the same name are subsequently created and then deleted, GNOME complains that the file already exists and asks for a rename or overwrite as it tries to move the files to the .Trash folder.

A patch for this defect will be posted.

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

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

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

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

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

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

4.0 General Issues

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

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

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

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

4.5 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

4.6 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).

4.7 Purging or Salvaging Files in a DFS Junction Target Location

With the Novell Client 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.

5.0 Fixes Since the Last Release

The following bugs have been fixed with the release of the Novell Client for SUSE Linux Enterprise 11 SP1:

  • EA size was getting returned as 1 with flistxattr API, even if there are no EAs. This is corrected now.

  • 64 bit library handling.

  • Login with default context when wrong context is given.

  • Integrated Login failure fix.

  • OU names with dot are not displayed correctly in the novell login and LDAP contextless login window.

  • Ability to browse the eDirectory trees via Novell Client.

  • Single-sign-on for Novell Client on LUM setups.

6.0 Legal Notices

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.

Copyright © 2007 - 2010 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.