Novell Client 2.0 SP1 for Linux Readme

August 2008

1.0 Installation Issues

NOTE:If you are installing on a workstation that is already running Novell Client 2.0 for Linux, be sure to read the information in Section 2.0, Upgrade Issues.

1.1 System Requirements

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

  • SUSE® Linux Enterprise Desktop 10 SP1 (32-bit or 64-bit)

  • openSUSE 10.2 (32-bit or 64-bit)

IMPORTANT:For this release, you should not install the 32-bit version of the Novell Client 2.0 for Linux onto a 64-bit operating system. If you do so, you will lose the ability to log into the GUI credential provider. You will see the error message, “Authentication Failed,” and will be unable to log in.

If you want to use the precompiled Novell Client for Linux Virtual File System provided with the distribution, make sure one of the following packages is installed on your workstation before you install the Novell Client for Linux. Which package is installed depends on your kernel type.

  • novfs-kmp-default

  • novfs-kmp-smp

  • novfs-kmp-bigsmp

If you want to compile the Novell Client for Linux Virtual File System from sources provided with the Novell Client for Linux, make sure the following packages are installed on your workstation before you install the Novell Client for Linux:

  • gcc

  • kernel-source

  • make

1.2 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.3 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.4 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.0 Upgrade Issues

2.1 Be Sure to Apply the Latest SLED 10 SP2 Patches

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

3.0 Login Issues

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

3.4 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

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

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

/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.8 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.9 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.10 Logging in with a Password Policy

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

4.0 File and Folder Issues

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

4.3 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.4 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.5 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.6 Accessing The Same File from Multiple Workstations

If you log in to the same NetWare server from two different workstations (such as SLED and openSUSE) 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.7 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.8 Using gedit on SLED 10

If you save a file using gedit on SLED 10 when write file access is not given, you will receive a message saying that you can’t save the file. If you try to save the file again, gedit will die.

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

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

5.0 General Issues

5.1 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.2 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.3 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.4 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.5 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.6 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.

6.0 Fixes Since the Last Release

The following bugs have been fixed with the release of the Novell Client 2.0 for Linux:

  • novfs fails to compile on kernel 2.6.21 and later.

  • Bad error message for restricted time.

  • Login dialog box does not return cause of failure (lockout, time restriction, etc.).

  • The Novell Client for Linux does not work with DFS Junctions.

  • If a symlink gets deleted or moved, subsequent delete mappings should not cause an error.

  • DCOP communication error after defining SLP settings.

  • Can't log in using certain UTF-8 characters.

  • No icon for Novell Services when right-clicking the desktop option.

  • Unable to save with gedit on first attempt.

  • eDirectory login profile is saved when password is not saved in miCASA.

  • Novell Services does not function.

  • Username [Public] saved in miCASA after re-overwriting autologin profile.

  • Send Message to System Console gives an exception.

  • ncl_tray randomly crashes.

  • Font of tray doesn't follow system-wide font selections.

  • Add new functions to Novell Services.

  • In Nautilus, some messages are displayed in English after installing novell-nautilus-plugin.

  • Deleting files from a mapped drive take a very long time.

  • Novell Client 1.2 component not releasing from memory after use.

  • Improved configuration between CASA and persistent drive mappings.

  • Novell Properties appears to only have a 20 trustee limit.

  • Red N needs to read Packages64 entry from ncl_ver.txt.

  • Only right-clicking Red N displays menu.

  • Running single section of DOSbox dir will hard lock the server after a few hours.

  • Error: The system could not log you into the network.

  • Nautilus menu extension does not work with Nautilus 2.16.

  • nwlogin --help does not tell you what variable to use with the --E or --passenv switch.

  • NWCCOpenConnByName error when logging in using invalid IP address for tree.

  • Cannot allocate temp dir handle when browsing volume without rights while mapping drive.

  • GUI text change on startup tab for root user.

  • After rcnovfsd stop, rcnovfsd start fails to start novfsd.

  • Context button crashes on Login dialog box.

  • Cannot scan Connection references every time user clicks Red N.

  • nwlogout throws error when given tree IP address.

  • Need a way to hide the password in command line Novell Client for Linux.

  • Need Typical selection to install Novell Client 2.0 for Linux instead of having to manually select which packages to install.

  • man nwlogin does not show/explain the command -E and --passenv options.

  • MAN page of nwcopy command is not updated with -f option.

  • Requester needs to honor the CString types(Unicode,ASCII) requested by the Client.

  • After logging in/out multiple times, login script is not run and cannot relogin.

  • Server field isn't being filled by default on first login.

  • Mapping a drive successfully returns error value 1.

  • END: and EXIT: commands are ignored.

  • The results screen does not display the Network Address of the workstation.

  • Integrated Login doesn't work directly after a reboot.

  • Getting error Warning, unmatched IF...THEN statement (no END or ENDIF) in login script.

  • When logging into a second tree, the login script from the first tree runs instead.

  • Logging into two trees causes the other tree to get disconnected.

  • nwlogin: Login with option -r (run scripts) fails for non-English locales.

  • Client fails to update correctly using YaST.

  • Password fields are not being emptied when user changes password.

  • Mapping at startup does get honored.

  • User quota used not updating when a Novell Client for Linux mapped volume is updated.

  • causes a -bash: [: missing `] error.

  • Salvaging process hangs if you try to salvage already purged files.

  • Novell Properties option does not work for the servers listed in Novell Networks > Novell Services > All Connections.

  • In login scripts, “MEMBER OF” was failing if organization was specified.

  • Canceling the Novell Login pop-up window displayed from Novell Networks > Novell Services > All Connections throws a KDE Error, and the Konquror file browser terminates.

  • In login scripts, mapping a drive name with spaces in the name does not work.

  • A debug error code is displayed in the login scripts results window when logging in to the Novell Client for Linux, leaving the Tree field blank.

  • Error message NWCCOpenConnByName is generated when a user tries to calculate the size of volume using the Property option of the Server.

  • Having multiple TREE commands in a login script could hang login.

  • Create new copies of the gnome-starter.bsh.desktop file in ~/.config/autostart directory.

  • Multiple launchers are created for the Novell Client for Linux.

  • nwcopy -s command is not forcing existing targets to be overwritten.

  • An exception is thrown when a trustee user clicks the OK button in the Inherited Rights and Filters window of a folder.

  • The Novell Navigation Panel appears in the KDE environment despite disabling it in the settings.

  • NWCScanConnInfo() does not return unlicensed connections (only licensed).

  • Cannot open a Crossover Word document from a mapped drive.

  • Cannot execute binary file while configuring Links on mapped drive.

  • Compiling Links on an OES volume takes an abnormally long time.

  • Saving files on mapped drive makes them blank.

  • Could not save a Windows Word 2003 document under Crossover Office.

  • Salvaging a file when the file already exists with the same name locks up the Novell Client for Linux.

  • Failed to back up the data on VFS.

  • File not found when resaving a file on an NSS volume.

  • With NMAS on, NWCCScanConnRefs thrown after logging in/out of eDirectory several times.

  • Drive maps are not cleaned up if you log out of the desktop and the session is removed.

  • Obtaining results from the Context button take up to 60 seconds.

  • File lock (fcntl) is not honored.

  • All trees connection are closed when using the Novell Connections dialog box to close one tree connection.

  • Garbage in Novell Message Popup.

  • When connection is not licensed; Login does not process user login scripts.

  • NCP Remote file locking is not working correctly.

  • Cannot save files in

  • File lock error 820E when trying to assign an NDS user to a GroupWise Post Office.

  • Unable to save Microsoft Office file in Crossover Office.

  • novfs shuts down when using Crossover Office to edit document.

  • novfs daemon hangs machine on shutdown.

  • Add a File Caching setting to the YaST configuration wizard.

  • Unable to log in with a user that has a . in username.

  • It would be nice to have Deselect all buttons option in the configuration wizard.

  • No option to turn off broadcast messages.

  • Login settings in YaST need to have a setting for default server.

  • Scripts need to change to a new directory path.

  • Remove obsolete User Preference check box from Tray Application Settings dialog box in YaST.

  • Default openSUSE desktop is changed after clicking Novell Services.

  • Konqueror side bar: servers volume duplication.

  • Error Is a directory when copying file several times quickly.

  • Login script results windows is automatically closed when there is an error.

  • Clicking Cancel during shell extension login changes browse window.

  • Browse button does not work in Novell Map Directory dialog box.

  • Misleading color-coding on MAP/DISPLAY commands in login script editor.

  • Cannot browse context using IP address as tree (SLP configured).

  • SLP configuration dialog box is not resizable.

  • nwlogin asks for server instead of context.

  • The Novell Client invokes KDE browser in GNOME desktop.

  • Creating/manipulating files on mapped drives via touch or vi results in input/output errors.

  • Unable to cut and past from the results window when running debug for scripting.

  • nwlogin requests context after context is entered in the username.

  • Novell Network in KDE is not working properly.

  • ESC should not mean “yes” when asking if you want to quit NCL_TRAY.

  • Cannot log in as user with 'dot' in the name.

  • If new passwords don't match (when changing password), the Confirm field disappears.

  • If the admin user is in the same context as the server, the admin should not be required to put in his context.

  • The file size of large files is displayed as a negative number.

  • Invalid login confirmation message when user has a Locality code in their eDirectory name.

  • When using the Change Password option in the Novell Tray to change a password with more than 512 characters, the Novell Client fails to change the password, and the Novell Tray does not work consistently.

  • Cannot browse into Locality containers.

  • Unable to map drives when logged in to SLED as an Active Directory user.

  • Using ~/ to represent a home directory on the map command fails.

  • Login script results windows is automatically closing when there is an error.

  • Login scripts are not processed when they are greater than 40K in size.

  • UTF-8 characters are not handled in the integrated greeter (from eDirectory or in local file).

  • Name resolution is not done during integrated login.

  • Integrated login not parsing ms\.dot correctly.

  • Cannot disable integrated login from YaST.

  • Integrated login does not work when no tree is specified.

  • Mapping with space in a directory name does not work.

  • Password Expired message is displayed twice if using mapped drives.

  • Tree command in login script causes seg fault.

  • Error while running CRON job.

  • Stop installing the unused file from novell-client-script.rpm.

  • Tree command does not prompt for correct username.

  • Tree command should attempt to connect to new tree with current credentials.

  • Alias container scripts are executed instead of real users container scripts.

  • Drive mappings fail when using message_server variable.

  • Cannot query or remove mapped drives.

  • Cannot map drives using $HOME on the command line.

  • Cannot use keywords such as 'root' as a directory name in map command.

  • System occasionally hangs during session startup.

  • Integrated login runs twice simultaneously.

  • Login script error ...unexpected END_OF_LINE. expecting COLON_EQUAL...

  • Logging into multiple servers via login script.

  • Passwords in login script are not always hidden.

  • Cannot map to Volume on (single-server tree) using Volume's name.

  • Error mapping directory object.

  • The Novell Client for Linux does not handle Locality containers properly.

  • Extend INCLUDE statement in login scripts to accept the syntax include x:myscript.txt.

  • Run Scripts box is unchecked after running a persistent mapping.

  • User is unable to log in to SLED 10 SP1 after unselecting the Run Novell Client Login at Session Startup option in the Novell Client for Linux.

  • Cannot detach from one server when connected to multiple servers on the same tree.

  • nwlogin with different users on the same tree fails to log in second user.

  • Cannot detach from only one tree if attached to multiple trees.

  • Map this drive at startup option does not actually do anything.

  • User with UTF-8 characters is unable to modify login scripts.

  • SLP Logon to Cluster Server changes according to what server is master.

  • After logging out of a cluster server, you are not completely logged out.

  • If you have the login options Clear previous user name and Integrate login both activated, you get a User Name is not Defined error upon logging into your session.

  • Error during bootup: Novfs kernel loadable module is not installed correctly.

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

Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at and one or more additional patents or pending patent applications in the U.S. and in other countries.

For Novell trademarks, see the Novell Trademark and Service Mark list.

All third-party trademarks are the property of their respective owners.