September 18, 2007
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.
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:
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.
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.
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.
Selectto import the key. The install will complete successfully.
If you have already configured the Integrated Login feature and then enable GDM to automatically log in a user, Integrated Login will not work.
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.
The following is a sample of valid login script syntax for the MAP command:
map display on f:=server\vol:path
map display off f:=server\vol:path
map “my projects”:=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
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 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
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)
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:
WRITE “This is July”
To resolve this, include the THEN statement each time.
THEN WRITE “This is July”
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:
novell-xregd novfs_ST novfsd
If one of these processes is not listed, restart the Novell Client for Linux.
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.
If you are logging in to a tree that does not have a registered DNS name, you must enter the server name in thefield to log in.
There are rare occasions when a login script does not run. To solve this, log in again to rerun the login script.
If you log in with a password policy, grace login attempts do not decrement.
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.
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.
GNOME is leaking file handles, which is causing files to be left open.
A patch for this defect will be posted.
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.
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.
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.
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. This functionality is not working properly in this beta release.
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.
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.
Clickto stop the copy.
If you try to open or save an OpenOffice.org or Microsoft Word file in a directory with 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 file/directory Create, Modify, and Erase rights (in addition to the Read, Write, and File Scan rights) will let you open or save the file.
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.
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.
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®.
When you use the Red N menu to create a map drive, there is no default value for the. This field is left blank because with the Novell Client for Linux, you can use wither 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 , select , then click . Select the driver letter you want from the drop-down list, then click >
After the Novell Client for Linux is installed, abutton 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 icon on the sidebar menu to display Novell connections.
With the Novell Client 2.0 for Linux, you cannot purge or salvage files in a Distributed File Services (DFS) junction.
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 www.novell.com/info/exports/ 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 http://www.novell.com/company/legal/patents/ 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.