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.
You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside.
Copyright © 2001-2003 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.
Patents pending.
eDirectory is a trademark of Novell, Inc.
GroupWise is a registered trademark of Novell, Inc. in the United States and other countries.
NetWare is registered trademark of Novell, Inc. in the United States and other countries.
Novell is a registered trademark of Novell, Inc. in the United States and other countries.
Novell iFolder is a registered trademark of Novell, Inc. in the United States and other countries.
All third-party trademarks are the property of their respective owners.
This guide provides information on known issues for Novell® iFolder® 2.1 and is divided into the following sections:
For information on installing, configuring, and managing iFolder, see the following:
For the most recent version of the Novell iFolder Readme, see the Novell iFolder Documentation Web site.
For emerging issues, see the Novell iFolder 2.1 Readme Addendum (Technical Information Document 10079972) .
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items within a cross-reference path.
A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark.
When a single pathname can be written with a backslash for some platforms, or a forward slash for other platforms, the pathname is presented with a backslash. Users of platforms that require a forward slash, such as UNIX* should use forward slashes as required by the software.
This section describes known issues for Novell® iFolder® 2.1 server software that have not been resolved for this release. These issues apply to all versions of iFolder 2.1, except where noted.
The issues are categorized as follows:
For information on installing and managing the iFolder server, see the Novell iFolder 2.1 Installation and Administration Guide
The following installation and administration issues for Novell iFolder 2.1 server software apply to all server operating systems:
If an administrator's User object resides on multiple LDAP servers, do not enable the object as an iFolder server Admin user. If you have only one LDAP server and one corresponding Admin user, you can enable the object; however, enabling an administrator User object as an iFolder server Admin user is not recommended.
In the iFolder Management Console, when you attempt to update a User Disk Quota, the User Admin page reports the new User Disk Quota as if the update succeeded, but the Update command is not actually executed by the server. The user's client continues to report the old User Disk Quota. You must repeat the task to force the User Disk Quota to update.
To avoid this problem, modify the User's Disk Quota, then click Update two times, allowing time for the Web page to refresh between clicks.
The Username field is limited for iFolder user IDs.
eDirectory: An iFolder user ID cannot exceed 64 characters in length if you use Novell eDirectoryTM. If the user ID has more than 64 characters, neither the administrator nor the user will be able to access the user's iFolder account.
Active Directory: An iFolder user ID cannot exceed 20 characters in length if you use Microsoft* Active Directory*. If the user ID has more than 20 characters, the operation will fail with an error.
The reason for this is that the sAMAccountName attribute, which acts as the user's logon name, is limited to only 20 characters. The iFolderServer administrator applications sets both the user's CN attribute and the sAMAccountName attribute to the same value.
You can manage user accounts from the User Management page in the iFolder Management Console.
The Apache 2 Server registry and the iFolder server software do not support extended ASCII characters (characters above code point 127) in the following fields during the installation:
Additionally, use English when entering the SSL certificate location.
You can access the iFolder Management Console using Microsoft Internet Explorer (IE) 5.0 or later. Netscape* 7 or later is the recommended Netscape browser version.
For iFolder servers running on a NetWare® or Windows* 2000 server operating system, you must use IE to access your files via a Web browser.
For iFolder servers running on an IIS Web server, you must use an IE browser to access the iFolder Management Console or the default iFolder Web site from that server. You cannot access the iFolder Management Console and default iFolder Web site using a Netscape browser on an IIS server. If the iFolder server uses IIS and you want to use a Netscape browser, access the server remotely from a workstation.
The Java* applet can be accessed using Microsoft Internet Explorer 5.0 or later. Netscape 7 or later is the recommended Netscape browser version.
We require Sun* Microsystems JVM* 1.3 to 1.4.1_02 for the iFolder Java applet to function properly. If you upgrade your browser (such as to IE 6 Service Pack 1), the upgrade will change the default JVM to Microsoft's version. Make sure to manually reset Sun's JVM as the default JVM after you upgrade.
Logging in to the Java applet fails with Sun Java 1.4.2_01. When you attempt to log in, the applet sometimes fails to initialize and returns an error message "Applet NIDapplet not inited." If it does initialize, the applet login fails and returns an error message "Authentication failed."
To avoid this problem, use Sun Java 1.3 to 1.4.1_02.
For the iFolder management and help tools to work properly, you must enable pop-up windows in your Web browser while configuring and administering iFolder. If you use an application that blocks pop-up windows, disable the blocking feature temporarily.
The login to Global Settings from the iFolder Management Console might fail intermittently, displaying a message "Previous Login Failed." To resolve this, repeat the login process until you are successful.
If your browser caches its pages, the next time you return to the iFolder Management console, after having logged out of the console and closed your browser, you might not need to log in again.
The numbers displayed in the Totals field in the Reporting section of the iFolder Management Console reflect only the totals of the iFolder server that the iFolder administrator is logged in to, not the totals of all iFolder servers.
Rapidly toggling back and forth between the Reporting and System Monitoring screens in a Web browser might cause the iFolder server to hang. If iFolder hangs, stop and restart the iFolder server software.
If two administrators are simultaneously making system monitoring requests from two different browsers to two different iFolder servers, either of the iFolder servers in the iFolder system might hang. If iFolder hangs, stop and restart the iFolder software.
The following issues apply to the NetWare server operating systems:
After upgrading from iFolder 1.0x on NetWare 6 to iFolder 2.1x on NetWare 6.5, changes you make to the Client Policies in the iFolder Management Console do not take effect. The interface indicates the changes were successful, but they actually fail. This problem occurs because the upgrade process does not delete the ifolder.xml file for iFolder 1.0x from the iFolder data directory. iFolder 2.1x attempts to use this file instead of the client policies contained in the iFolderSettings object in eDirectoryTM.
To avoid this problem after the upgrade process completes, remove the ifolder.xml file from the iFolder data directory. By default, this location is sys:\ifolder\ifolder.xml. Replace sys:\ifolder with the actual path to your iFolder data directory. After you remove the ifolder.xml file, policies are correctly applied using the the iFolderSettings object in eDirectory.
After upgrading from iFolder 1.0x on NetWare 6 to iFolder 2.1x on NetWare 6.5, the LDAP server has the wrong iFolder port number. This results in iFolder bypassing the Set Passphrase option on an upgraded Novell NetStorage server, even if the existing iFolder account uses encryption.
When upgrading the NetWare 6 server, the NetStorage upgrade sequence provides an option to specify the correct iFolder DNS server name and port number. If you accept the default iFolder server name and port number (80), the wrong address gets stored in the LDAP server. The default port number used in iFolder 1.0x was 52080, but you should enter your actual port number.
To avoid this problem, when upgrading NetStorage, make sure to specify the correct DNS server name and port number for the iFolder server.
To correct this problem if you have already upgraded NetStorage, use iManager to modify the iFolder DNS name and port number for NetStorage.
In iManager, click File Access (NetStorage).
Click iFolder Storage Provider.
Type the correct iFolder server DNS name and port number. For example,
nif1.your-domain-name.com:52080
Replace nif1.your-domain-name.com with the actual DNS name of your iFolder server. Replace 52080 with the actual port number of your iFolder server.
To effect the change, click Submit.
After the server updates, restart your server before you use it again.
With iFolder 2.1 for NetWare 5.1 Support Pack 5 and NetWare 6.0 Support Pack 2 servers, you must use Apache 1.3.26, 1.3.27, or 1.3.28. If you use another version of Apache, iFolder will not work as designed. You can download Apache software from the Apache Web site.
A binary distribution of Apache 1.3.26 was made available with Support Pack 2 for NetWare 6.0 and might already be installed on your network. Reinstall the original Apache 1.3.26 binary distribution; do not install iFolder on an upgraded version of Apache other than Apache 1.3.27 or 1.3.28.
Customers running Apache on NetWare 5.1 Support Pack 5 will most likely use the default Apache configuration file (httpd.conf) under the sys:\apache\conf directory. The iFolder 2.1 server software tries to modify the sys:\apache\conf\adminserv.conf file during the installation. On a NetWare 5.1 server, this file will not exist and the install will generate an error:
Error updating file.
To avoid this problem, manually add the following Include statement at the end of the httpd.conf file:
include sys:\Apache\iFolder\Server\httpd_ifolder_nw.conf
On a NetWare server, you can run iFolder 2.1 in protected memory space or in operating system space. If you get public symbol errors while attempting to load iFolder in protected memory space, iFolder is not loading. This occurs because iFolder cannot find the root certificate file rootcert.der.
To solve this problem, copy the rootcert.der file (usually found in the sys:\public directory) to the following file:
nif1.your_domain_name.com\ldap\_master.der
Replace nif1.your_domain_name.com with the DNS name or the IP address (such as 192.168.1.1) of your iFolder server.
Novell iFolder 1.0x did not allow iFolder to share a server address and port number. In the Netware 6 install, the user is given an option to use either alternate port numbers for iFolder (such as 51080, 52080, 51443, or 52443) or a secondary IP address. If you specified port numbers, the URLs for accessing the iFolder Web pages required that the port numbers be included in the address, such as in the following examples:
iFolder Management Console: The general URL is
https://nif1.your-domain-name.com:portNumber/iFolderServer/Admin
Replace nif1.your-domain-name.com with the actual DNS name or IP address of your iFolder Server. Replace portNumber with the your actual secure port number, such as 51443 or 52443.
iFolder Web Page: The general URL is
http://nif1.your-domain-name.com:portNumber/iFolder
Replace nif1.your-domain-name.com with the actual DNS name or IP address of your iFolder Server. Replace portNumber with the actual clear text port number, such as 51080 or 52080.
After upgrading iFolder 1.0x on NetWare 6 to iFolder 2.1x on NetWare 6.5, the iFolder Management Console for administrators and the iFolder Web page for users return a "Page Not Found" error when accessing the pages without specifying a port number and when using the links on the iFolder Welcome page. The link on the Welcome page directs the HTTPS request to Port 443 instead of to the original port number. Unless the port you used for iFolder 1.0x was actually Port 443, the error results.
To avoid this problem, the iFolder administrator and users must continue to access the iFolder Management Console and the iFolder Web page by specifying the port number you originally configured for iFolder 1.0x in the URL. For example:
https://nif1.your-domain-name.com:52443/iFolderServer/Admin
http://nif1.your-domain-name.com:52080/iFolder
The iFolder 2.1 release of Novell iFolder requires Windows 2000 Server Service Pack 3 and later.
The following issues apply:
During the installation of iFolder 2.1 on an IIS server, the iFolder install program extends the Active Directory schema. You can extend the schema independently using the installation interface, but both the software install and the schema extension must be accomplished in order for iFolder to work.
Make sure that Active Directory is set up properly to enable extension and that the administrator has schema-extension rights to the root of the tree where the iFolder server resides.
In Microsoft Active Directory, shared schema root domain controllers might not extend the schema if all of the member domain controllers are not active and synchronized during the iFolder 2.1 server installation. Make sure all shared root domain controllers are active and synchronized before you install iFolder.
The iFolder 2.1 release of Novell iFolder supports only the Red Hat* Linux* 8 version of Linux.
The following issues apply to Red Hat Linux 8 server operating systems for the initial release of iFolder 2.1:
These issues do not apply to Novell iFolder 2.1.2, which was released with Novell NterpriseTM Linux Services. iFolder 2.1.2 supports only the Enterprise Linux server operating systems specified in the Novell Nterprise Linux Services Installation Guide.
Because Apache 2.0.x is relatively new, other Novell products that use Apache might not work if you upgrade. We recommend that you use have only iFolder and Apache running on the server.
Polling iFolder 2.1 clients for updated files to synchronize produces a large number of entries in the access_log file. You can disable the access_log output by commenting out the following line in the /usr/local/apache2/conf/httpd.conf file:
CustomLog logs/access_log common
HINT: To comment out a parameter, place the pound sign (#) in front of it. For example:
#CustomLog logs/access_log common
To install iFolder 2.1 successfully on Red Hat Linux 8, you must have installed the compat-libstdc++-7.3-2.96.110.i386.rpm file. If this RPM is missing, you will see this error message:
/tmp/install.dir.XXXX/Linux/resource/jre/bin/i386/native_threads/java: error while loading shared libraries: libstdc++-libc6.1-1.so.2: cannot open shared object file: No such file or directory
To install this RPM file:
Log in to the iFolder server as the root user.
Insert CD2 from Red Hat Linux 8.0 software.
To mount the CD, enter
mount /mnt/cdrom
To install the missing RPM, enter
rpm -Uvh /mnt/cdrom/RedHat/RPMS/compat-libstdc++-7.3-2.96.110.i386.rpm
To eject the CD, enter
eject
Novell iFolder 2.1 does not support the Solaris* Server operating system. There is no upgrade path from iFolder 1.0x to iFolder 2.1 and later.
This section describes known issues for Novell® iFolder® 2.1 client software and other user interfaces.
The issues are categorized as follows:
The following issues apply to all workstation operating systems:
The iFolder 2.x client cannot access an iFolder Standard Edition (1.0x) server; similarly, an iFolder 1.0x client cannot access an iFolder 2.1 server. If you have multiple iFolder accounts located on different servers, make sure that you are accessing the iFolder server with the correct version of the iFolder client. For example, use an iFolder 2.1 client to access your files on an iFolder 2.1 server.
If your workstation has Norton Internet Security (NIS) installed, you might see the following error message when attempting to log in to an iFolder server from an iFolder client:
Protocol version error - need newer version of client software.
To correct this problem:
Open the Norton Internet Security application.
Click Options > Internet Security.
Click General > Advanced Options.
Click Web > Add Site.
In the left pane, type the DNS name or IP address of the iFolder site.
In the right pane, click the Privacy tab.
Under Cookies, select Permit from the drop-down list.
Under Browsing Privacy, select Permit from the Referer and Browser drop-down lists.
Click the Active Content tab.
Under Script, select Allow All Scripts to Execute from the drop-down list.
Click Apply.
Close Norton Internet Security.
Restart the iFolder client, then log in again.
The following issues apply to all workstation operating systems:
If you plan to use the encryption option for your iFolder user account, you must create the account by logging in for the first time while using the iFolder client or the Java applet. After the account is set up, you can log in using the iFolder client, the Java applet, Novell NetStorage, or NetDrive.
If you attempt to create the account by logging in for the first time with Novell NetStorage, the account is set up as a clear text account with no encryption option. This occurs even if the administrator sets up encryption as a mandatory policy for all users. Unless your account is already set up for encryption, NetStorage does not offer you a passphrase entry option.
When you use NetStorage for the first time for an iFolder account with encryption, you must enter the passphrase. NetStorage might request the information two times. NetStorage stores the passphrase as an attribute of the User object in eDirectory. After that, NetStorage requests only a password during login.
The Username field is limited for iFolder user IDs.
eDirectory: An iFolder user ID cannot exceed 64 characters in length if you use Novell eDirectoryTM. If the user ID has more than 64 characters, neither the administrator nor the user will be able to access the user's iFolder account.
Active Directory: An iFolder user ID cannot exceed 20 characters in length if you use Microsoft Active Directory. If the user ID has more than 20 characters, the operation will fail with an error.
The iFolder client typically uses your network user ID and password as your login identity for iFolder. If your network user ID exceeds the iFolder limit, contact your system administrator to set your user ID to a value that meets the character limit for user IDs in iFolder.
In iFolder 2.1, if you enable both the Remember Password option and the Place a Shortcut on My Desktop check box, the shortcut persists across system restarts. Even if you delete the icon from your desktop, the icon is re-created every time you reboot your computer.
However, if you log out of the iFolder client and then log in again and uncheck the iFolder shortcut check box, the next time you reboot your computer, the iFolder shortcut will not be created.
If you get an error message indicating that you are not connected to the Internet and you know that you are, open the Internet Connection Wizard to troubleshoot your connection. Right-click the Internet icon on your desktop, then click Properties > Connections > Setup. When the Internet Connection Wizard launches, follow the on-screen instructions.
You must be working online in order for the iFolder client to synchronize files. If you are logged in to the iFolder server and set your Web browser to work offline, the iFolder icon in your system tray dims because working offline breaks the connection to the server. When you set your Web browser to work online, the iFolder client re-connects and logs in to the iFolder server, and the iFolder icon in your system try is once again active (colored).
Logging in to the Java applet fails with Sun Java 1.4.2_01. When you attempt to log in, the applet sometimes fails to initialize and returns an error message "Applet NIDapplet not inited." If it does initialize, the applet login fails and returns an error message "Authentication failed."
To avoid this problem, use Sun Java 1.3 to 1.4.1_02.
You can modify your iFolder preferences while logged in to your iFolder account but working offline. However, the changes will not take effect until you activate your Internet or network connection and log in again.
The following issues apply to all workstation operating systems:
If problems occur when communicating with the iFolder server while either uploading or downloading files, iFolder will return an error and will not try again to upload or download until the next set synchronization interval.
Do not try to synchronize your GroupWise® archive by setting a GroupWise archive path to the location of your iFolder directory. If you do this, the iFolder client will corrupt the GroupWise archive. This happens because iFolder does not synchronize files as a set and GroupWise needs the files in the archive to be maintained as a set of files.
This problem has been identified for GroupWise; however, similar problems might arise with any database that is implemented as a collection of linked files.
The following issue applies to Windows 98SE operating system:
The iFolder client software requires that the client for Microsoft networks is already installed on your Windows 98SE workstation. Otherwise, your workstation might crash.
To avoid this problem, make sure to run the Internet Connection Wizard on the workstation before installing the iFolder client software. Right-click the Internet icon on your desktop, then click Properties > Connections > Setup. When the Internet Connection Wizard launches, follow the on-screen instructions.
The following issue applies to the Windows 2000 Server operating systems:
When Remote Installation Service is installed on your Windows 2000 server, SIS (Single Instance Store) is also installed. The driver for SIS (sis.sys) conflicts with the iFolder client filter driver (niffltr.sys). You must uninstall one of these two programs; otherwise, your users' workstations will not reboot during the iFolder client installation process and you will get an error message indicating that the two drivers conflict with one another.