NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: NW6SP5 English-Espaņol Overlay CD (128bit) TID #: 2969168 README FOR: nw6sp5ee.exe NOVELL PRODUCTS and VERSIONS: NetWare 6 ABSTRACT: NetWare 6 Support Pack 5 English-Espaņol Overlay CD with 128-bit encryption. ----------------------------------------------------------------- DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES ALL REASONABLE EFFORTS TO VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION. ----------------------------------------------------------------- INSTALLATION INSTRUCTIONS: NetWare 6 Support Pack 5 Overlay CD Image June 2004 Overview This DVD contains the NetWare 6 Support Pack 5 Overlay CD images, which lets you create a bootable CD that will install NetWare 6 and NetWare 6 Support Pack 5 simultaneously on a server. This image is in ISO format. This is the last Support Pack for NetWare 6.0. Updates released after this Support Pack should be installed after installing this Support Pack. For more information on Support Pack issues, see nw6_iss.txt at the root of the created CD. For information on the latest Support Pack issues, see TID 10091736 (http://support.novell.com/cgi-bin/search/searchtid.cgi?/ 10091736 .htm). To order the Support Pack CD, go to Consolidated Support Pack Web site (http://support.novell.com/tools/csp/orderinfo.html). 1.0 Support Pack Installation 1.1 Requirements 1.2 Suggested Software 1.3 Creating a NetWare Overlay CD 1.4 Installing NetWare Using the Overlay CD 1.5 DOS Partition Not Created When Manual Execution Option Selected 1.6 Upgrading to NetWare 6 2.0 Installed Products Database Might Not Be Updated 3.0 Update Product Versions after Accelerated Upgrade 4.0 Issues 4.1 JVM 1.3.1 Installed 4.2 LSI IDE Driver 4.3 Upgrading NetWare 5.1 Server Running eDirectory 8.7 4.4 Using Response Files 4.5 In-place Upgrades from NetWare 5.1 Overlays 4.6 Tools Directory Not Included 5.0 Documentation Conventions 6.0 Legal Notices 1.0 Support Pack Installation 1.1 Requirements 700 MB CD-R media with a supported CD-R device. 1.2 Suggested Software Roxio Easy CD Creator, Nero, or any CD-burning software that supports ISO formats. 1.3 Creating a NetWare Overlay CD The following steps are for using Roxio Easy CD Creator 5. If you are using other CD-burning software, consult the software's documentation for specific instructions on how to create a CD from an ISO image. If you are installing from the Consolidated Support Pack Overlay DVD, start with Step 2. 1. Extract the ISO file to a computer that has a writable CD device. 2. In your Roxio EasyCD Creator 5, select the option to Record CD from CD Image. 3. Browse to the location of the image. 4. Select the .iso file. 5. Click Open > Start Recording. When recording is completed, you will have a bootable CD that will install NetWare and the Support Pack simultaneously. The correct CD volume label is created automatically. 1.4 Installing NetWare Using the Overlay CD After you have created an overlay CD, you can install NetWare by following the installation or upgrade documentation on the NetWare 6 (http://www.novell.com/documentation/lg/nw6p/index.html). 1. Insert your Overlay CD into the server's CD drive and power on the server. 2. Follow the on-screen prompts. 3. After the install completes and the server reboots, enter LOAD NWCONFIG at the console prompt. 4. Select Product Options > Install a Product Not Listed. 5. Change the install path to sys:\system, then press Enter. This runs sys:\system\pupdate.ips, a script that updates the product versions and descriptions. 1.5 DOS Partition Not Created When Manual Execution Option Selected During the initial stages of booting the NetWare 6.0 Support Pack 5 overlay CD, you are prompted with the following: A - Auto Execution of Install.bat M - Manual Execution of Install.bat (allows optional parameters to be used). If you do not respond within 30 seconds, the install defaults to option A - Auto Execution, which proceeds with the DOS Partition Creation utility and the install program. If you select option B, the install bypasses the DOS Partition Creation utility and exits to a DOS prompt. If a DOS partition does not exist, you must use the Caldera DOS utilities fdisk.com and format.com, located in the install\drdos directory on the Overlay CD, to create and format a DOS partition. When a DOS partition exists, enter install (along with any optional command line parameters) to start the server installation. If you launch the install with no DOS partition available, it will result in the following message: Error writing response file to disk. If there is no DOS partition on the system, you will need to create one before continuing the install 1.6 Upgrading to NetWare 6 If you are upgrading from a NetWare 5.1 server with the Support Pack installed to NetWare 6, you might be prompted to overwrite newer files. You should always select the option Always Overwrite Newer Files to ensure the correct NetWare 6 files are installed. 2.0 Installed Products Database Might Not Be Updated After installing this overlay, you might notice that the View Installed Products list was not updated. The correct files were installed, but the listing was not updated. To correct this, enter the following at the server console: NWCONFIG B=SYS:\SYSTEM\PUPDATE.IPS The script will update the View Installed Products list (also known as the products.dat database) and the correct list of installed products will display. 3.0 Update Product Versions after Accelerated Upgrade After using the Accelerated Upgrade Method, you must do a post-install of the products you want to run on the server. The post-install does not update the product versions. To update the product versions as displayed in View Installed Products, complete the following: 1. At the server console, load NWCONFIG. 2. Select Product Options > Install a Product Not Listed. 3. Press F3 and then specify the path, including the volume name, to pupdate.ips. For example, sys:\system. 4.0 Issues 4.1 JVM 1.3.1 Installed The overlay install contains JVM 1.3.1 only. If you want JVM 1.4.1 or later installed on the server, you will need to install it separately after completing the server install. JVM is available from Novell Products Downloads (http://download.novell.com) or from the Consolidated Support Pack DVDs. 4.2 LSI IDE Driver To use the LSI IDE driver instead of the Novell IDEATA driver during a custom installation of NetWare, do the following: 1. When prompted to accept the IDEATA storage driver, arrow down and select Modify. 2. Select the IDEATA driver, then press Del to remove the driver from the list of storage drivers to install. 3. Press Ins to add a new driver to install, then specify the driver name. 4. Arrow down and select Return to Driver Menu. 5. Arrow down and select Continue, then continue with the installation. If you are using a Default installation, you will need to use the Novell IDEATA driver. 4.3 Upgrading NetWare 5.1 Server Running eDirectory 8.7 If you are using the NetWare 6 Support Pack 3 overlay or later to upgrade a NetWare 5.1 server running eDirectory 8.7 or later, role-based services might not work correctly. To resolve this, you need to set up role-based services again. Follow the instructions in the "Novell iManager Administration Guide" (http://www.novell.com/documentation/lg/imanage10/index.html? imanage/data/a40igz4.html). 4.4 Using Response Files Due to changes in the syntax of the response.txt file, you must create a new reponse.txt to use with this overlay and subsequent installs. Response.txt files that worked with previous Support Packs will not work with this release. For information on creating a response file, refer to the NetWare 6 online documentation (http://www.novell.com/documentation/lg/nw6p/ othr_enu/data/a30hh07.html). 4.5 In-place Upgrades from NetWare 5.1 Overlays If you are using the overlay to do an Inplace Upgrade of a server created using the NetWare 5.1 Support Pack overlay, you will need to delete pupdate.ips from the server's sys:\system prior to performing the upgrade. 4.6 Tools Directory Not Included The \tools directory is not included in this overlay image. If you need files from \tools, you must go to the Support Pack. 5.0 Documentation Conventions In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. 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. 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 2004 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. U.S. Patent No. 5,157,663; 5,349,642; 5,455,932; 5,553,139; 5,553,143; 5,572,528; 5,594,863; 5,608,903; 5,633,931; 5,652,859; 5,671,414; 5,677,851; 5,692,129; 5,701,459; 5,717,912; 5,758,069; 5,758,344; 5,781,724; 5,781,724; 5,781,733; 5,784,560; 5,787,439; 5,818,936; 5,828,882; 5,832,274; 5,832,275; 5,832,483; 5,832,487; 5,850,565; 5,859,978; 5,870,561; 5,870,739; 5,873,079; 5,878,415; 5,878,434; 5,884,304; 5,893,116; 5,893,118; 5,903,650; 5,903,720; 5,905,860; 5,910,803; 5,913,025; 5,913,209; 5,915,253; 5,925,108; 5,933,503; 5,933,826; 5,946,002; 5,946,467; 5,950,198; 5,956,718; 5,956,745; 5,964,872; 5,974,474; 5,983,223; 5,983,234; 5,987,471; 5,991,771; 5,991,810; 6,002,398; 6,014,667; 6,015,132; 6,016,499; 6,029,247; 6,047,289; 6,052,724; 6,061,743; 6,065,017; 6,094,672; 6,098,090; 6,105,062; 6,105,132; 6,115,039; 6,119,122; 6,144,959; 6,151,688; 6,157,925; 6,167,393; 6,173,289; 6,192,365; 6,216,123; 6,219,652; 6,229,809. Patents Pending. Novell and NetWare are registered trademarks of Novell, Inc. in the United States and other countries. eDirectory is a trademark of Novell, Inc. All third-party products are the property of their respective owners. NetWare 6.0 Support Pack 5 Known Issues June 2004 1.0 Installation Issues 1.1 File Overwrites 1.2 Installing the Support Pack with BorderManager 1.3 Upgrading a NetWare 6.0 Middle Tier Server to Causes Policy Distribution to Fail 1.4 Server Consolidation Utility 1.5 Using ZEN for Desktops with iPrint 1.6 Volumes Larger Than 2 Terabytes 1.7 Avoiding a ConsoleOne 1.3.6 Downgrade 1.8 Sys: Does Not Mount after Install 1.9 ULTRA Driver 1.10 Updating JVM 1.11 ConsoleOne 1.3.5 and JVM 1.4.x Not Supported 1.12 Increase File Handles in Config.sys 1.13 New Server Installation to an Existing NetWare 6 Tree Fails during Authentication 1.14 Ensuring Native File Access for UNIX Functionality 1.15 Simultaneous NetWare 6 and Support Pack Install 1.16 Using ZENworks for Servers to Distribute the Support Pack 1.17 Using Accelerated Upgrade 1.18 Resolving NetMail Port Conflicts after an Upgrade 2.0 New Issues for Support Pack 5 2.1 Security Updates for PKI, NMAS, and NTLS 2.2 GroupWise Does Not Install 2.3 Storage Management Issues 2.4 DEX 4.1 2.5 DNS/DHCP 3.0 Issues for Support Pack 4 3.1 Using ACPI Drivers 3.2 NFS Gateway for NetWare 6 3.3 Macintosh Extended Characters Not Supported 3.4 Down Command Powers Off Server with ACPI Drivers 3.5 Remove SET CLIENT FILE CACHING ENABLED=OFF from Autoexec.ncf 3.6 Grace Connections Changed 3.7 Migration Wizard Not Included 3.8 Radius.nlm update for iChain and NMAS 3.9 Packet Receive Buffers Default Changed 3.10 NetWare FTP Server Changes for Support Pack 4 3.11 SMDR Resolution support 3.12 SMDR IP Selection Support 3.13 iFolder 2.1 3.14 NetStorage 3.15 Starting a Different Web Server 3.16 Supernetting with TCP/IP 3.17 Cluster Trustee Assignments Incorrect after Upgrade 3.18 NCS and NSS Software RAID0 3.19 Only First Node Can Join a Cluster 3.20 Certificate Server Installation Error 3.21 Node Fails to Join Cluster with Different Code Page 4.0 Issues from Support Pack 3 4.1 TCP/IP for BorderManager VPN 4.2 TED Unable to Generate Keys with ZENworks for Servers 3.0.2 4.3 NetStorage and NetWare WebAccess 4.4 NetStorage 409 Error 4.5 NetStorage HTML View Requires Authentication 4.6 Adding NetWare 6 Servers to eDirectory 8.7 4.7 Removing Users/Groups from NetWare NIS Slave Server 4.8 NetWare FTP Server Issues 4.9 PERL Scripting 4.10 NetWare Usage Removed 4.11 Novell iManager Updates 4.12 Pervasive SQL Updates 4.13 "Failed to Associate Initial Roles" Error 4.14 Timesync Issues 4.15 Installing NetWare WebAccess 4.16 56-Bit Version of iFolder 4.17 BorderManager 4.18 Rights and Drive Mappings 4.19 Settings Change 4.20 Dell Server Management Software (AppCD) 4.21 Creating Files or Directories with Double-byte Characters Using NetWare FTP Server 4.22 NAAS Installation 4.23 NetWare Storage Management Services (SMS) 5.0 Issues from Support Pack 1 and 2 5.1 DNS/DHCP Issues 5.2 iPrint/NDPS 5.3 NetWare Enterprise Web Server 5.4 Change in Adapter Multipath Support 5.5 NetWare Remote Manager Issues 5.6 Changing HTTPSTK Values 5.7 Novell Advanced Audit Service 5.8 Novell Cluster Services 5.9 Novell iFolder 5.10 NWDEPLOY Authentication Problems 5.11 Novell iManager 1.2.2 Issues 5.12 Restoring iMonitor 1.5 Custom Settings 5.13 Novell Native File Access for Macintosh (AFP) 5.14 NFS and Native File Access for UNIX Issues 5.15 Novell Native File Access for Windows (CIFS) 5.16 Joining a NetDevice NAS Appliance into a NetWare 6 eDirectory Tree 5.17 Novell Storage Services 5.18 Apache Web Server 5.19 Novell TCP/IP 5.20 Perl for NetWare 5.21 Timesync Issues 5.22 Novell Small Business Suite 5.23 Btrieve Updates 5.24 Server Communication Issue 6.0 NLM Programs Bound into Server.exe 7.0 Driver Issues 7.1 Epson Gateway 7.2 Using Netr4m.ham 7.3 HP Hot-Plug Stops Working 7.4 I2o Drivers Removed 7.5 Updated Dell Drivers 8.0 Uninstalling the Support Pack 8.1 Novell LDAP Server Does Not Support Downgrades from Support Packs 8.2 Native File Access for UNIX Uninstall Issues 9.0 Files in the \Tools Directory 10.0 Changes Since Last Support Pack 11.0 Product Testing 12.0 Additional Documentation 13.0 Legal Notices 1.0 Installation Issues Installation instructions are in nw6sp5.txt, located at the root of the Support Pack. 1.1 File Overwrites Complete the following if you want to turn on error messages for file overwrites during the Support Pack install: 1. Using a text editor, open the response.txt file found in the Support Pack's install directory. 2. Locate the overWriteNewerFilePrompt=false entry and modify it to overWriteNewerFilePrompt=true. We recommend that for an upgrade you choose to always overwrite every file, so you have the same configuration Novell tested with. 1.2 Installing the Support Pack with BorderManager Is you are running BorderManager on the server where you install the Support Pack, you will be forced to reboot the server after the Support Pack installation, even if you chose the option to not reboot during the install. 1.3 Upgrading a NetWare 6.0 Middle Tier Server to Causes Policy Distribution to Fail Upgrading a ZENworks 4.0.1 or 6.5 Middle Tier Server to NetWare 6.0 Support Pack 5 causes distribution failure for User policies with an Add Scheduled Action property. It also causes workstation associated Group policies and Computer Extensible policies to fail on NT/2000/XP workstations. To prevent this condition, you need to download some updated files. - For ZENworks 4.0.1, see TID 10093378 (http://support.novell.com/cgi-bin/search/searchtid.cgi?/100 93378.htm). - For ZENworks 6.5, see TID 10093372 (http://support.novell.com/cgi-bin/search/searchtid.cgi?/100 93372.htm). 1.4 Server Consolidation Utility When using the Server Consolidation Utility and migrating data from or to a cluster volume, an error fffdae might occur if your cluster server nodes are spread throughout different eDirectory contexts. If the server (from the SCU project) that holds the mounted cluster volumes does not have rights to the cluster virtual server object and the cluster-enabled volume object, and does not have a Read\Write replica of the partition these objects reside in, then a failure fffdae is displayed on the Verification screen of the Server Consolidation Utility. To resolve this, add the server as a trustee of the context that contains the Virtual Server and Cluster Volume objects. The default rights assigned when adding the trustee are sufficient. 1.5 Using ZEN for Desktops with iPrint iPrint v3.0.5 that ships with this Support Pack requires an update for ZEN for Desktops 4.0.1 in order to deliver the new iPrint modules in a policy. Download and install the ZEN for Desktops 4.0.1 Interim Release 4a (IR4a) from Novell Product Downloads Web Site (http://download.novell.com). 1.6 Volumes Larger Than 2 Terabytes Before applying this Support Pack on a server with pools larger than 2 TB, consult TID 10081723 (http://support.novell.com/cgi-bin/search/searchtid.cgi?/100817 23.htm) before continuing with the Support Pack install. 1.7 Avoiding a ConsoleOne 1.3.6 Downgrade If you installed ConsoleOne 1.3.6 prior to installing the Support Pack, you must copy \tools\console1\products.ver from the Support Pack to the server's sys:\system before installing the Support Pack. Failure to copy this file results in ConsoleOne 1.3.6 being downgraded to 1.3.5. If ConsoleOne was downgraded, reinstall ConsoleOne 1.3.6. 1.8 Sys: Does Not Mount after Install If volume sys: does not mount after installing this Support Pack and restarting the server, restore your previous storage driver. Storage drivers used prior to installing the Support Pack are backed up (even if you did not choose the Backup option during the install). Look at the server's startup.ncf file to determine the storage driver being used. Then copy the storage driver from c:\nwserver\backsp5\storage\.* to c:\nwserver. Be sure to copy without using a file extension (file.*) so you get the driver's associated configuration file. 1.9 ULTRA Driver If the ULTRA driver has been selected during the NetWare installation, yet refuses to load, you should load the IDEATA driver instead: 1. Return to the installation program's drivers screen 2. Select the ULTRA driver, and delete the driver. 3. Press Insert to select the IDEATA driver to replace it. 1.10 Updating JVM This Support Pack includes updates for both JVM 1.3.1 and JVM 1.4.1. The install detects which version is installed on the server and applies the corresponding updates for JVM. 1.11 ConsoleOne 1.3.5 and JVM 1.4.x Not Supported If you are running ConsoleOne 1.3.5 and install JVM 1.4.x, ConsoleOne will no longer work. ConsoleOne 1.3.6 works with JVM 1.4.x, which is available at the Novell Product Downloads Web site (http://download.novell.com). 1.12 Increase File Handles in Config.sys NetWare might require additional file handles. You should edit c:\config.sys on your NetWare server and increase the Files= parameter to 100. If there are insufficient file handles, an NLM program might not load or the server might hang during the server startup. 1.13 New Server Installation to an Existing NetWare 6 Tree Fails during Authentication If the NCP Packet Signature option is set to 3 on a NetWare 6 Support Pack server and that server holds the Master Root Replica, subsequent server installations into that tree might fail during authentication. To resolve this: 1. On the server that holds the Master Root Replica, change the NCP Packet Signature option on the master server to 0 (zero) and then restart the master server for the change to take effect. 2. On the new server being installed, use the Back button in the installation program to return to the beginning and then go through the installation screens again. This should allow the installation to authenticate and complete successfully. After installation, you can reset the NCP Packet Signature option back to its original setting. 1.14 Ensuring Native File Access for UNIX Functionality For Native File Access for UNIX to function correctly, upgrade all servers in the tree to the latest Support Pack. Upgrade all NetWare 5.1 servers to Support Pack 4 or later and all NetWare 6 servers to Support Pack 1 or later. Native File Access for UNIX services function only after they are upgraded. 1.15 Simultaneous NetWare 6 and Support Pack Install You can download a CD image that installs NetWare 6 and the NetWare 6 Support Pack simultaneously. See the Consolidated Support Pack DVDs or Consolidates Support Pack Web site (http://support.novell.com/tools/csp/csplist.html) to obtain the image. 1.16 Using ZENworks for Servers to Distribute the Support Pack For information on using ZENworks for Servers to distribute the Support Pack, see \tools\zfs\zfssp.pdf. This requires Acrobat Reader, which is available from Adobe's Web site (http://www.adobe.com). 1.17 Using Accelerated Upgrade If you are upgrading a NetWare 5.1 server with NetWare 5.1 Support Pack 6 and eDirectory 8.6, the accelerated upgrade does not work. You should use the In-place upgrade option instead. See the NetWare 6 online documentation (http://www.novell.com/documentation/lg/nw6p/index.html) for more information. 1.18 Resolving NetMail Port Conflicts after an Upgrade If you are upgrading a NetWare 5.1 server running NetMail on port 80 to NetWare 6 Support Pack, you need to complete one of the three following options after the Support Pack is installed to resolve port conflicts, because the Support Pack installs the Apache Web server and Web servers generally respond to requests on port 80. Option 1: If you are using the server as a dedicated NetMail server and do not want it to host a Web server, edit autoexec.ncf and comment out the line that reads NVXADMUP by putting a pound sign (#) at the beginning of the line. Option 2: If you want to continue to run NetMail on port 80, change the port that the Web server listens on by bringing down the Web server (use the nvxadmdn command) and editing sys:\apache\conf\httpd.conf. Change the line that reads Listen 80 to use a different, unused port number. Option 3: If you want the Web server to answer to port 80 but still want NetMail to run, you can change the NetMail port by completing the following steps: 1. Launch the NetMail WebAdmin. 2. Browse to the Messaging Server. 3. Browse to the Modular Web Agent. 4. Change the ports to ones that are not in use on your server. 2.0 New Issues for Support Pack 5 2.1 Security Updates for PKI, NMAS, and NTLS There are several security components issues that are resolved with this support pack, including some security vulnerability fixes. For more details on the security vulnerability fixes, please see TID 10087450 ((http://support.novell.com/cgi-bin/search/searchtid.cgi?/10087 450.htm) titled "NISCC vulnerability advisory on SSL (secure sockets layer) and TLS (transport layer security) protocols." If eDirectory 8.7.1 or greater is installed, the following security components are updated to the versions indicated: PKI 2.7.3, NMAS 2.3.4, NTLS 1.8. If eDirectory 8.7.0 is installed, no security component updates are updated by the Support Pack. If eDirectory 8.6.x (default) is installed, the following security components are updated to the versionsindicated: PKI 2.5.2, NMAS 2.3.0, NTLS 1.6. 2.2 GroupWise Does Not Install If cannot install GroupWise on a NetWare 6.0 server from a workstation running the Novell Client 4.9 Support Pack 2, you need to update to ConsoleOne v1.3.6c. You can download the latest ConsoleOne from the Novell Product Downloads Web Site (http://download.novell.com). 2.3 Storage Management Issues 2.3.1 TSA600 Support TSA600 has been replaced by TSAFS from NetWare 6.0 SP4. TSAFS provides the same functionality and has several performance improvements over TSA600.We recommended that you use TSAFS because TSA600 is no longer supported. 2.3.2 Extended Attributes of Directories TSAFS does not back up extended attributes for directories on traditional file system volumes. The following error is logged to the TSA error log: "The extended attributes cannot be read". However, extended attributes for files are fully supported. 2.3.3 Cache Memory Threshold To reduce the amount of memory used by TSAFS in backup operations, the cache memory threshold value can be set at 10%. It has been found empirically that setting it at 10% on standard configurations does not adversely affect backup performance while reducing memory utilization. New server installations use 10% as the default from NetWare 6.5 SP2, but upgrades do not alter existing values. 2.3.4 Data Backup in Non-English Environments If data backed up from a NSS volume in non-English environments needs to be restored to a traditional volume, a conversion from UTF-8 to MBCS is required. This might result in certain specific characters in pathnames being altered. This restored data needs verification especially, if the target server runs in a different locale. Backup engines use MBCS interfaces and might display data differently from how they are represented on NSS volumes because of a conversion from UTF-8 to MBCS in non-English locales. However, it is expected that dat is backed up and restored correctly because TSAFS stores data natively in UTF-8 streams. In such circumstances, we recommend that the backup and a trial restore be manually verified before the backup is certified to be correct and consistent. In environments with MAC files stored on the NetWare server, files that have the 0xDA character might cause the scan to abort because this character is converted to a "/" during the scan by backup engines. If the backup engine did the scan in all available name spaces, then the files are backed up using their UTF-8 names. 2.4 DEX 4.1 If you are running DEX 4.1 (NPS) on your server you might get a WrappedRuntimeException error, and you cannot launch Dex (NPS) after installing the Support Pack. To resolve this, delete the following libraries from the path where Dex was installed, typically, /webapps/nps/web-inf/lib: xerces.jar xercesImpl.jar xalan.jar Do not delete these files from other directories. 2.5 DNS/DHCP - There is a New command line option for dnipinst. - You cannot use iManager to import/export the DHCP Subnet Pool. Use the DNS/DHCP Java-Based Management Console to perform this operation. - If you use the Reload DNS server feature using iManager, you might encounter an Invalid command line option error on the named screen. This is because the command line options passed for Named in the reload request are being corrupted. However, you can use the Netware Console to reload the DNS server. 3.0 Issues for Support Pack 4 3.1 Using ACPI Drivers If you are doing a new server install using the Overlay CD on a server machine that supports ACPI, the install will auto-detect and load the correct hardware support modules (PSMs), whether it is MPS14 or ACPI. If your server has a P4 processor that supports HyperThreading and this feature is enabled in the machine's BIOS, the ACPI driver will detect the setting and enable the multiple logical processors. The machine's BIOS must be set up correctly before beginning the NetWare install in order for the automatic hardware feature detection to work correctly. There is no benefit in "manually" loading ACPI drivers on a machine that does not support HyperThreading. For example, NetWare does not support ACPI on Pentium III machines with the Novell ACPI drivers. For a list of tested and approved hardware, see the Novell Developer Web site (http://developer.novell.com/yessearch/Search.jsp). 3.2 NFS Gateway for NetWare 6 If you have installed the NFS Gateway for NetWare 6 (also known as NFS Gateway 4.0), you need to obtain an updated nfsgy.nlm. Without the update, nfsgy.nlm will not load due to version-specific dependencies on nss.nlm. The updated nfsgy.nlm can be downloaded from Product Updates Web site (http://support.novell.com/filefinder) by searching on nfsgy4a.exe or nfsgy.nlm. 3.3 Macintosh Extended Characters Not Supported Macintosh Extended Characters are not supported with AFP. 3.4 Down Command Powers Off Server with ACPI Drivers If you are using the latest PSM drivers supplied by Novell on machines with ACPI support (acpidrv.psm), you might notice that the Down command powers off the server as part of the NetWare server software shutting down. This is because most ACPI-compliant hardware requires a power cycle to reinitialize the ACPI tables before the NetWare server can be restarted. Instead of using the Down command, use Reset Server to bring the machine back up automatically. 3.5 Remove SET CLIENT FILE CACHING ENABLED=OFF from Autoexec.ncf This Support Pack adds the is setting SET CLIENT FILE CACHING ENABLED=OFF to your server's autoexec.ncf file. If you want this turned on, remove this statement from your autoexec.ncf. 3.6 Grace Connections Changed The number of grace connections was changed from two to three. 3.7 Migration Wizard Not Included Beginning with Support Pack 4, the Migration Wizard has been removed. You can download the Migration Wizard from the Novell Product Downloads Web Site (http://download.novell.com). 3.8 Radius.nlm update for iChain and NMAS If your server is running radius.nlm and configured to work with NMAS, you need to copy the radius.nlm from the \tools directory to each server. Failure to do this will cause an error -802, where the user seems to authenticate but then fails after that. For more information, see TID 2965335 (http://support.novell.com/cgi-bin/search/searchtid.cgi?/296533 5.htm). 3.9 Packet Receive Buffers Default Changed Beginning with Support Pack 3, the Minimum Packet Receive Buffers and the Maximum Packet Receive Buffers defaults were changed to 2000 and 10,000, respectively. 3.10 NetWare FTP Server Changes for Support Pack 4 3.10.1 Large File Support NetWare FTP Server now supports file transfer for files greater than 4 GB in size. 3.10.2 Security Extensions NetWare FTP server is now capable of establishing secure connections with secure FTP clients. After successful negotiation of the SSL/TLS mechanism, all the commands, replies, and data transferred are encrypted. Making use of this feature requires an FTP client which is compliant with RFC 2228-FTP Security Extensions. For more information, see TID 10085857 (http://support.novell.com/cgi-bin/search/searchtid.cgi? /10085857.htm). 3.10.3 Configuration File Update The SECURE_CONNECTIONS_ONLY parameter has been added to the etc\ftpserv.cfg file. This parameter lets you specify only secure FTP connections. SYMPTOM: 3.10.4 Dynamic Updates to Restrictions File By default, the changes made to the FTP Server configuration and restrictions files now take effect dynamically. If required, you can disable the dynamic configuration. 3.10.5 Unloading a Single Instance Unloading a single instance of FTP Server is now supported. To unload it, use the following command syntax: nwftpd -u [:[//...]].cfg 3.11 SMDR Resolution support SMDR now resolves targets available in the etc\hosts file and the configured DNS server in the machine where SMDR is running. 3.12 SMDR IP Selection Support SMDR can be configured to listen at any bound IP address in the machine using the new SMDR interface or NetWare Remote Manager under IP Address Management. 3.13 iFolder 2.1 Novell iFolder 2.1 fails to install on a server with NetWare 6 Support Pack 4 because the iFolder 2.1 install checks for Apache 1.3.26 or 1.3.27, but NetWare 6 Support Pack 4 includes Apache 1.3.28. For more information, see TID 10087636 (http://support.novell.com/cgi-bin/search/searchtid.cgi?/100876 36.htm). 3.14 NetStorage NetStorage login does not work after the NetStorage post-install. For information on resolving this, see TID 10086436 (http://support.novell.com/cgi-bin/search/searchtid.cgi?/100864 36.htm) and 10079985 (http://support.novell.com/cgi-bin/search/searchtid.cgi?/100799 85.htm). 3.15 Starting a Different Web Server Before starting a new Web server, the following NLM programs should be unloaded: - Mod_icgi.nlm - Modnsn.nlm - Nslcgi.nlm - Nwsec.nlm - Scrcv.nlm 3.16 Supernetting with TCP/IP - Once the server is configured with a supernet mask, it behaves like an end node when IP Forward gets disabled. It continues to behave like an end node, even if the mask is changed to a non-supernet mask and the system is reinitialized. To make it work like a router, change the state of the IP packet forwarding or RIP or LAN Static Routing in INETCFG and reinitialize the system. - With the CIDR mask on, some valid host IDs ending in .255/.0 cannot be bound. 3.17 Cluster Trustee Assignments Incorrect after Upgrade When upgrading from NetWare 5.1 to NetWare 6 Support Pack 4 or later, the trustee assignments might not have completed when the Upgrade Complete message is displayed in ConsoleOne. Depending on the number of trustee assignments, you might have to wait a while for the trustee assignments to be completed after receiving the Upgrade Complete message. 3.18 NCS and NSS Software RAID0 For NetWare 6.0, the implementation of Novell Cluster Services with an NSS software RAID0 (striping) device is not supported. 3.19 Only First Node Can Join a Cluster If you run IPFLT after installing the Support Pack and only the first node can join the cluster, to resolve this by turning off the default filtering of the packets when IPFLT31 is loaded. The following parameter should be turned off at the server console: Set Filter Subnet Broadcast Packets=off 3.20 Certificate Server Installation Error After installing the Support Pack, you might receive the following error when installing Certificate Server from a workstation running NICI 2.6.4 or 2.6.5: A Novell NICI client has not been installed on your computer. In order to install Certificate Server, you must install a NICI client first. The Novell NICI client can be installed from the Novell Client Software CD. To resolve this, install Certificate Server from a workstation running NICI 2.6.1. You can download NICI 2.6.1 from Novell Downloads Web site (http://www.novell.com/downloads). 3.21 Node Fails to Join Cluster with Different Code Page If you are running a cluster containing servers that use different code pages, you will receive the following error after installing the Support Pack: SbdJoin: The code Page (850) on this node doesn't match that (932) of node #1. CLUSTER--<12038>: SBD has reported a fatal error. To resolve this, nodes that are using a different code page must be reinstalled to use the same code page as all other nodes in the cluster. 4.0 Issues from Support Pack 3 4.1 TCP/IP for BorderManager VPN This Support Pack does not include the 56-bit version of TCP/IP. After applying the Support Pack to a server running the 56-bit version of TCP/IP, the VPN stops communicating. To re-establish communication, complete one of the following options: Option 1 - Keep 56-bit Encryption Copy tcpip.nlm, tcp.nlm, and bsdsock.nlm from sys:system\backsp4 to sys:\system. Option 2 - Upgrade to 128-bit Encryption 1. Regenerate the RSA and DH keys at the master VPN server using VPNCFG and the Generate Encryption Information option. 2. Copy the new encryption information on the master VPN server to a diskette. 3. Regenerate the RSA and DH keys at the slave VPN servers using VPNCFG and the diskette from Step 2. 4. Copy the new encryption information on the slave VPN servers to a diskette. 5. From NWADMN32, delete and read the new slave servers using the diskette from the Step 4. 6. Restart the VPN servers. For successful operation on a site-to-site VPN, all sites must be running the 128-bit version for communication to take place. 4.2 TED Unable to Generate Keys with ZENworks for Servers 3.0.2 TED is unable to generate its ephemeral keys on a NetWare 6 Support Pack 3 or later server with JVM 1.3.1_06. This inability to generate ephemeral keys means no encrypted distribution support is possible. To resolve this, download the patch associated with TID 2965417 (http://support.novell.com/cgi-bin/search/searchtid.cgi?/296541 7.htm). 4.3 NetStorage and NetWare WebAccess When accessing NetStorage through the gadget in NetWare WebAccess, the Menu items are displayed midway down the page and the status bar shows that JavaScript and other errors have occurred. None of the menu items is functional. This is found with MS Internet Explorer 6 Service Pack 1, and on Win98, NT, 2000, and XP. Netscape 7.0 works fine. To resolve this, access the NetStorage server directly from a browser. 4.4 NetStorage 409 Error After installing the Support Pack, when you try to overwrite a file with the same name (whether doing a move, copy, or upload) through NetStorage, you might get an HTTP /1.1 409 error. To resolve this, rename the file that you want to overwrite and then proceed to move, copy, or upload the file. 4.5 NetStorage HTML View Requires Authentication If you are using the NetStorage HTML view and are prompted multiple times to authenticate when creating a new folder or renaming or deleting a file, you need to download an update. See TID 10077724 (http://support.novell.com/cgi-bin/search/searchtid.cgi?/100777 24.htm) for more information. 4.6 Adding NetWare 6 Servers to eDirectory 8.7 Before you add the first NetWare 6 server into an existing tree eDirectory 8.7, you need to prepare the tree by running DSRepair and selecting the Post NetWare 5 Schema Update option. This is performed automatically if you install the NetWare 6 server through Deployment Manager. Additionally, if you want to use Domain containment, you need to run the NetWare 6 version of DSRepair on a server holding a read/write replica of root and then select the Optional Schema Enhancements option. You might need to copy the NetWare 6 version of DSRepair from the CD along with the NetWare 6 version of sal.nlm. Sal.nlm should be version 2.0 or later. 4.7 Removing Users/Groups from NetWare NIS Slave Server When the NetWare server is made a slave NIS Server and users/groups are deleted from the master NIS Server, you need to do the following to remove the users/groups from NetWare NIS slave server: 1. From the ConsoleOne main menu, right-click the User or Group object. 2. Click Properties > Other. 3. Under Attributes, select nisUserGroupDomain and then select the specific domain. 4. Click Delete. For a list of ongoing Native File Access for UNIX issues, see 5.14 NFS and Native File Access for UNIX Issues. 4.8 NetWare FTP Server Issues 4.8.1 Administering Using NetWare Web Manager When administering NetWare FTP Server using NetWare Web Manager, when you make any changes and click the Save button, although the changes are saved to the configuration file, the following message displays in the right pane of the page: "The page cannot be displayed" You can ignore this message. To view the changes that you made, visit some other page and then revisit the page where you made the changes. 4.8.2 Modifying Parameters The following parameters can be modified only in the ftpserv.cfg configuration file. - DATA_BUFF_SIZE - KEEPALIVE_TIME - DEFAULT_FTP_CONTEXT - PSEUDO_PERMISSIONS including PSEUDO_FILE_PERMISSIONS and PSEUDO_DIR_PERMISSIONS You cannot modify these parameters using the NetWare Web Manager management utility. 4.8.3 Data Transfer Issues When the DATA_BUFF_SIZE configuration parameter is set to certain values such as 512 KB or 1020 KB, operations such as get, put, ls, and dir for more than 10,000 files in a directory might give errors. To resolve these errors, set the DATA_BUFF_SIZE parameter to a lesser value. 4.9 PERL Scripting PERL scripts that need access to system files must now log in to eDirectory. You can turn off this security feature by editing the sys:\system\nwsec.ini file. The feature is enabled by default. 4.10 NetWare Usage Removed Beginning with this Support Pack, NetWare Usage information was removed from NetWare Remote Manager and is not currently available. 4.11 Novell iManager Updates - You can download Novell iManager 1.5.2 from http://download.novell.com and selecting iManager for the NetWare platform. - Novell iManager 1.5 supports English and French languages. 4.12 Pervasive SQL Updates Updates for Pervasive SQL are not included in this Support Pack.To obtain updates, go to Pervasive's Web site and look for Pervasive SQL 2000i. 4.13 "Failed to Associate Initial Roles" Error If you are installing a new NetWare 6 Support Pack 3 or later on a server into an existing eDirectory tree that has iManager and role-based services already installed, you might receive an error message stating that the installation program "failed to associate initial roles." The new server attempts to associate the role-based services objects with the server's Admin object, but because the association was already performed in the existing eDirectory tree, the error displays. This error does not affect iManager or role-based services, and all iManager components should continue to work as designed. 4.14 Timesync Issues Beginning with NetWare 6 Support Pack 3, you can administer Timesync from NetWare Remote Manager. For more information see TID 10080009 (http://support.novell.com/cgi-bin/search/searchtid.cgi?/100800 09.htm). 4.15 Installing NetWare WebAccess When NetWare WebAccess (Apache Web Server) and the Novoynx Web server are installed on the same NetWare server, a 404 error might occur when you log in to NetWare WebAccess, because webaccess.html and webaccess1.jpg are copied to the documentroot of the Novonyx Web server. To resolve this, configure the WebAccess home page to point to the webaccess.html on the Novonyx Web server by completing the following: 1. Using ConsoleOne, access the properties of the WebAccess_Configuration_All_Users object and then click the Configure button. 2. On the Specify Your Home Page screen, enter the URL to webaccess.html located on the Novonyx Web server. 4.16 56-Bit Version of iFolder Novell will no longer provide support for the 56-bit version of iFolder. There is no upgrade path to the 128-bit version of iFolder from the 56-bit version because of encryption incompatibilities. To move to the 128-bit version, you should back up the iFolder data prior to installing the 128-bit version. After installing the 128-bit version, restore the files. 4.17 BorderManager If BorderManager is installed on the server and you upgrade using the NetWare 6.0 Support Pack 3 or later overlay CD, the LAN board names are changed to default names and the IP filters are disabled. After the installation, you need to reconfigure the filters using the BorderManager utilities. 4.18 Rights and Drive Mappings After installing the Support Pack, some users might not be able to map a drive to sys:\public or sys:\login. To resolve this, create a container or profile login script and then assign rights on the Server object to the sys:\public directory. 4.19 Settings Change Beginning with NetWare 6 Support Pack 2, the Minimum/Maximum Directory Cache Buffers settings were set to a higher default. The new defaults are Minimum Directory Cache Buffers = 500 and Maximum Directory Cache Buffers = 2000. The defaults were changed to accommodate larger default server configurations that have become common, both in terms of server RAM and server storage. Instead of setting a very low minimum of 20 or maximum of 150 and then letting the cache buffer count grow as needed (dynamically), the defaults were increased in the SET parameters of filesys.nlm to increase performance. You can change these default settings and your new settings are maintained. If your server configuration has not changed (for example, no memory or disk space has been added), there is no reason to bump these values up if performance is acceptable. 4.20 Dell Server Management Software (AppCD) Prior to installing the Support Pack, temporarily disable Dell OpenManage Software by editing autoexec.bat and commenting out (with a preceding ";" or "#") the lines that read: dell/omanage/omsa/dcstart""arraymgr.ncf sys:stystem/dell/omanage/iws/bin/netware/omastart If a DRACIIIXT, ERA, or ERA/O card is present, also comment out the following line: sys:system\dell\omanage\rac\d3start Restart the server and install the Support Pack. After the Support Pack is installed, you can uncomment the lines and restart the server to finalize the installation. Failure to follow the above steps might cause the Support Pack install to stop. 4.21 Creating Files or Directories with Double-byte Characters Using NetWare FTP Server If you create a file or directory in a DOS name space on a server with double-byte characters, the file or directory is created; however, the message to the FTP client might contain a different name. This happens especially with the 0x8374 character in Shift_JIS, 30D5 in Unicode that gets converted to the 0x8354 character in Shift_JIS, 30B5. 4.22 NAAS Installation - NAAS install does not extend the eDirectory schema if the container administrator is installing the server and that is the first server in the tree where NAAS is getting installed. - NAAS install does not extend the eDirectory schema in a tree in which eDirectory servers with version 8 or later are not available. 4.23 NetWare Storage Management Services (SMS) 4.23.1 Windows TSA and NWBACK32 Support We have discontinued support for NWBACK32 and the Target Service Agent (TSA) components for Windows. In the case of a Novell Client for Windows upgrade, NetWare SMS components existing on the system from a previous installation are not deleted and the Target Service is activated on start up. In the case of a NetWare upgrade, the modules existing on the server (tsaproxy.nlm and sbsc.nlm) from a previous installation are not deleted. However, they are not autoloaded. 5.0 Issues from Support Pack 1 and 2 5.1 DNS/DHCP Issues - The DNS/DHCP iManager-based management utility does not support the Netscape browser. - When deleting RRSet and IP Address objects through the DNS/DHCP iManager utility, do not select more than 5,000 objects at the same time. - The DNS/DHCP iManager utility does not support typeful names while creating objects. You must specify typeless names, or use the Object Selector. - The minimum screen resolution for running the DNS/DHCP Java-based Management Console is 600 x 800 with a minimum color setting of 256. 5.2 iPrint/NDPS 5.2.1 Lost Trustee Assignment When Using Migration Wizard When migrating to NetWare 6 from an earlier version of NetWare using the Migration Wizard, the trustee assignment to sys:\login is lost for the Public object. Therefore, NetWare 6 users do not have access to the directory. However, iPrint requires users to have access to this directory. To resolve this, assign Read and File Scan rights to sys:\login for the Public object or download the latest Migraction Wizard from the Novell Product Downloads Web Site (http://download.novell.com). 5.2.2 Novell IPP Gateway Removed The ability to create a new printer agent in iManager to use the Novell IPP gateway has been removed. Existing printers continue to function as originally created. The Novell IPP gateway uses IPP between the server and printer, and does not affect iPrint's use of IPP between the client and server. If you need to use the Novell IPP gateway, see TID 10072638 (http://support.novell.com/cgi-bin/search/searchtid.cgi? /10072638.htm) for more information. 5.2.3 Abend When Unloading WebAccess A server running GroupWise WebAccess and NDPS might abend when unloading the WebAccess modules. To avoid this, unload the NDPS NLM programs before unloading the WebAccess modules or move WebAccess or NDPS to a different server. 5.3 NetWare Enterprise Web Server 5.3.1 Setting Up Additional Document Directories on Remote Volume The Help topic for the Additional Document Directories screen shows the incorrect syntax for specifying a path to a remote volume. You must use the following syntax in the Map to Directory field when setting up an additional document directory that is located on a remote volume in your network: \sys:\system You can also use the following syntax: \sys:\ 5.4 Change in Adapter Multipath Support Beginning with NetWare 6 Support Pack 1, the multipath adapter support has been changed. The default setting is Off (disabled). For more information, see TID 10070244 (http://support.novell.com/cgi-bin/search/searchtid.cgi?/100702 44.htm). 5.5 NetWare Remote Manager Issues 5.5.1 Unloading and Reloading portal.nlm and httpstk.nlm To unload and reload the portal.nlm and httpstk.nlm modules used for NetWare Remote Manager, use the Restart button on the NetWare Remote Manager Configuration Options page. This function keeps track of additional plug-in modules and reloads them correctly when portal.nlm and httpstk.nlm are reloaded. If you just unload portal.nlm or httpstk.nlm at the server console, you might experience an issue with module dependencies (Timesync, LibC, Tcpstats, etc.) that have been established, and the NLM might not unload. If you successfully unload the modules, the dependent plug-in modules have to be loaded manually after portal.nlm. 5.6 Changing HTTPSTK Values If you modify configuration values for HTTPSTK while running a cluster, you might make the master cluster node leave and then rejoin the cluster. This forces the Master IP resource load script to do an HTTPBIND on the next master node. 5.7 Novell Advanced Audit Service 5.7.1 Excessive Memory Consumption If you are using NAAS on a server where NetWare 6 with SP1 or later is installed and Pervasive is running, the NetWare server abends due to excessive memory consumption. To avoid this, install Pervasive SQL 2000i Service Pack 4, the latest version of the Pervasive database. For more details, see the Pervasive Web site (http://www.pervasive.com). 5.7.2 Deploying NAAS in a Mixed Environment with NetWare 6 and NetWare 6 Support Pack Servers If you are configuring and using NAAS for the first time after installing NetWare 6 with a Support Pack and do not have NAAS on any other NetWare 6 server, this issue isn't applicable to your setup. Auditing eDirectory on NetWare 6 servers with Support Pack uses - A new eDirectory event template with Service Version 2.0 - Service Identifier NDS - A new eDirectory event policy The new eDirectory event policy template and eDirectory event policy are created as part of the default configuration of NAAS on the NetWare 6 Support Pack. But, auditing eDirectory on NetWare 6 servers without a Support Pack still uses the eDirectory template with Service Version 1.0, Service Identifier NDS, and the eDirectory event policy derived from it. In order for eDirectory auditing to function on NetWare 6 Support Pack servers, you must reconfigure the existing NAAS framework using the NAAS snap-ins that ship with the Support Pack. Only the administrator can reconfigure the existing NAAS configurations, using the NAAS default configuration utility. To successfully audit eDirectory after installing the NetWare 6 Support Pack, complete one of the following procedures. If the Auditor has not manually created a new eDirectory event policy template and an eDirectory event policy in the eDirectory partition (NAAS uses the DS Event policy template and DS Event Policy created by the NAAS default configuration utility on NetWare 6), complete the following steps: 1. Manually replicate the contents of the old eDirectory policy contents to the newly created eDirectory event policy. 2. Restart NetWare servers with the Support Pack after reconfiguring the NAAS framework. 3. To refresh templates and policies, restart ConsoleOne after reconfiguring NAAS. If the Auditor has manually created a new eDirectory event policy template or eDirectory event policy in the eDirectory partition (by creating new ones in addition to the DS event policy template and DS event policy created by the default configuration utility on NetWare 6), complete the following steps: 1. For every eDirectory event policy template and eDirectory event policy in the partition (other than DSEventPolicyV2 and DSEventPolicyTemplateV2, which are created by default), manually create a new eDirectory event template using the events.txt file located in the sys:\audit\naasevents folder on all NetWare 6 Support Pack servers and a new eDirectory event policy. 2. Manually replicate the contents of the old eDirectory policy contents to the newly created directory event policy. 3. Replicate associations to new event policies. For example, associate the new eDirectory event policies to wherever the old ones were associated. 4. After reconfiguring the NAAS framework, restart your NetWare 6 Support Pack servers. 5. To refresh templates and policies, restart ConsoleOne after reconfiguring NAAS. 5.7.3 Real Time Alert Settings The frequently generated events File Open, File Close, DSE Read Attribute, and DSE List Subordinates events should not be set for Real Time alert.This might abend the server. 5.8 Novell Cluster Services 5.8.1 Installation and Upgrade Issues If you had a NetWare 5.1 cluster installed and you performed an in-place upgrade on the servers in that cluster to NetWare 6, you must ensure the product entry for Novell Cluster Services is the proper version before installing the NetWare 6 Support Pack. To check the Novell Cluster Services product entry version number, do the following: 1. At the server console, load nwconfig.nlm. 2. Select Product Options > View/Configure/Remove Installed Products. 3. Find the NWCS product entry and ensure the version number is 1.6.0 or later. 4. Repeat the above steps at every server in the cluster. If the product entry version is earlier than 1.6.0, you must apply a patch to update the Novell Cluster Services product entry. Cluster servers that do not have the proper product entry version abend when you install NetWare 6 Support Pack. To apply the patch, do the following: 1. Go to the Novell Support site (http://support.novell.com/search/ kb_index.jsp) and search for TID number 2960777. 2. Click the filename to download the patch, and then follow the instructions included in the TID to update the Novell Cluster Services product entry. 3. Apply the patch to each cluster server that requires an updated Novell Cluster Services product entry. In all cases except the one described above, we recommend you use the NetWare 6 Overlay CD to create a new CD image that combines Netware 6 and NetWare 6 Support Pack in order to install or upgrade Novell Cluster Services for the NetWare 6 Support Pack. 5.8.2 Deleting a Shared Pool If you use the Delete option on the Media tab in ConsoleOne to delete a cluster-enabled pool that is offline, the virtual server, all volumes, and the cluster volume resource are removed from eDirectory but the pool is not deleted. 5.8.3 Viewing Cluster E-Mail Notification Messages The message portion of Cluster e-mail notification messages might be hidden in an attachment if you have chosen not to receive messages in XML format. This affects only GroupWise e-mail. View the MIME attachment in GroupWise to see the notification message. 5.8.4 Overlay CD Required on Cluster Upgrades When upgrading a NetWare Cluster from NetWare 5.1 to NetWare 6 Support Pack 1 or later, you must use a NetWare 6 overlay CD to run the Deployment Manager. If you use the NetWare 6.0 CD to run the Deployment Manager to pre-upgrade a NetWare 5.1 cluster or upgrade a cluster running on NetWare 6 Support Pack 2 or later servers, the results are unpredictable. The NetWare 6 Support Pack Overlay CD is available on the Consolidated Support Pack DVDs or the Consolidated Support Pack Web site (http://support.novell.com/tools/csp). 5.8.5 Spaces in Cluster Object Names If you have a NetWare 6 Cluster object that contains a space in its eDirectory name and you accepted the default naming convention when cluster enabling volumes, the default virtual server name (derived from the cluster name) that is automatically added to commands in the load and unload scripts will also contain space characters. This results in the CVSBIND and NUDP commands being ignored. If your cluster is already in this state and you then apply NetWare 6 Support Pack, you cannot migrate a resource over to another server without editing the cluster resource load and unload scripts. If you do not edit the resource load and unload scripts and you attempt to migrate a resource, you see an error similar to the following: This Server and the system having the hardware address 00-50-8b-b3-76-f9 have a conflict for IP address 10.251.217.10. You also get a similar message on the server that is attempting to load that migrated resource. Novell Cluster Services has never supported NDS object names containing spaces. Prior to NetWare 6 Support Pack 2 and the changes to ncpip.nlm and the NUDP DEL command, this problem might have gone unnoticed because the changes result in the secondary IP address not being deleted from the unload script if there are space characters in the virtual server name on the NUDP DEL command line. When the resource is migrated from node to node, the IP address is not deleted from the first node and causes an IP address clash when the resource is loaded on the second node. After applying NetWare 6 Support Pack to all the nodes in the cluster, edit the cluster resource load and unload scripts and replace space characters in virtual server names with underscores (_). 5.8.6 Node Will Not Join Cluster If you have problems with nodes joining a cluster, see TID 10072016 (http://support.novell.com/cgi-bin/search/searchtid.cgi? /10072016.htm). 5.9 Novell iFolder 5.9.1 iFolder Enhancement iFolder has enhanced its proxy support for the iFolder client. The iFolder client now includes a Proxy button on the iFolder Client Login dialog box that allows you to set specific proxy settings. For more information, see the "Novell iFolder Quick Start Guide" (http://www.novell.com/documentation/lg/ifolder/index.html). 5.9.2 NetStorage File Upload Performance Tuning If NetStorage file uploads are slow and you want to tune performance, you can use the following SET command: SET TCP Nagle Algorithm = Off The SET command works for NetStorage HTML, not NetStorage Gadget. The default is SET TCP Algorithm = On. 5.9.3 Setting the NetStorage/iFolder Passphrase The NetStorage\iFolder passphrase is stored in the eDirectory User object. A dialog to change the passphrase automatically appears when you select iFolder. Editing the passphrase.htm file that is included in the \iFolder directory can also set the passphrase. 5.9.4 Register All User Contexts for iFolder All user contexts must be registered in the Xtier\Configuration\Xsrv\Authentication Domains registry area and must be set in the iFolder configuration. You can use the NWAdmin utility to change NetStorage-specific registry settings. You can check the iFolder configuration at https:// :/. iFolderServerMultiple trees are not currently supported. That is, users of multiple trees cannot access iFolder from NetStorage; each tree should have its own NetStorage server/admin. 5.9.5 Ensure Admin Proxy User Is Logged In and Has Rights to All Contexts Make sure the admin proxy user is always logged in and has rights to all contexts. You can check this by adding oneNet/SESSIONS to the end of the NetStorage URL. NetStorage uses the proxy user to set the encrypted passphrase in the User object. In ConsoleOne, click the Other tab on the User Properties page to see the xtier-ifolderpassphrase string (encrypted). The admin proxy user is configured during the NetStorage installation and can be changed after the installation by clicking the General link in the NWAdmin utility. 5.9.6 Specifying an Invalid Passphrase If users specify an invalid passphrase that doesn't match the current iFolder passphrase, the passphrase.htm file continues to appear. SOLUTION: 5.9.7 Ensure passphrase.htm Is Posting the Correct URL Make sure the passphrase.htm form is posting to the correct URL. Open the passphrase.htm form and then right-click the document, and then select View Source. Search for the word action and check the URL. The URL is in the form ://:/oneNet/iFolder/pph. Make sure the protocol is HTPS and the port is the correct secure port. Also make sure the host name is correct. You can change the protocol, port, and host name using the NWAdmin utility. 5.9.8 Changing eDirectory Password Invalidates iFolder Passphrase If you change your eDirectory password, your iFolder passphrase becomes invalid. If this happens, reset your passphrase by re-entering the original passphrase that was created when your iFolder account was created. If you are using a browser to access NetStorage, you are automatically prompted to reset your passphrase. If you are using Web Folders to access NetStorage, you must access the passphrase.htm file in the iFolder directory to reset your passphrase. 5.9.9 Resetting the Passphrase The user's passphrase can also be reset at any time at the following URL where NetStorage is running: http:///oneNet/iFolder/pph. 5.9.10 HTTP Errors When Submitting Passphrase Context configuration problems, port/protocol, and invalid DNS addresses usually cause HTTP errors when attempting to submit the passphrase form. 5.9.11 Port Conflicts or Invalid Port Settings During the NetWare 6 Support Pack installation and configuration process, an administrator might inadvertently set the port number used by NetStorage to the same port number used by NetWare Enterprise Server. Manually changing the NetStorage port number after the installation also might cause a port conflict or an invalid port setting. NetStorage requires the Apache Web Server and must use the same port number as the Apache Web Server. The default port number for NetWare Enterprise Server is 80 for HTTP and 443 for HTTPS. If you have NetWare Enterprise Server installed, by default the Apache Web Server will get port 51080 for HTTP and 51443 for HTTPS. If the NetWare Enterprise Server is not installed, the default port number for Apache (and NetStorage) is 80 for HTTP and 443 for HTTPS. Be sure that NetStorage in configured to the same port numbers as Apache. NetStorage port conflicts and invalid port settings cause HTTP Forbidden errors when users attempt to create new folders in home directories and on mapped drives. These errors are characterized by Connection Refused IO errors and new folders not appearing after they are created. Servers configured to use multiple IP addresses are less likely to have port conflict problems because each service can generally use its default port assignment. To correct NetStorage port number conflicts or invalid port settings, edit the settings.properties file in the sys:\webapps\netstorage\web-inf\classes directory. Change the port number to match the one that is listed in the sys:\apache\conf\adminserv.conf file. This port number can be found in the # Start Apache Services Port Configuration section of the file. You can also edit the port number by clicking the WebDav Server link in the NWAdmin utility. 5.9.12 Downloading Folders Using a Browser Is Not Supported The Novell NetStorage documentation indicates that you can download folders using a browser with NetStorage. This is incorrect. You can download individual files using a browser with NetStorage, but downloading folders is not currently supported. You can create new folders or you can copy, delete, rename, or move existing files and folders by right-clicking the file or folder and then selecting the option you want. 5.9.13 Problems with Extended Characters in Text View You might encounter problems viewing extended characters using the NetStorage Text View feature. Also, folders containing extended characters that are created using the Text View feature might not display correctly in either the Text View or the Folder View. This problem can be avoided by creating folders with extended characters or viewing extended characters using the NetStorage Folder View. 5.9.14 LDAP Clear Text Passwords Are Required for Contextless Login If you want to provide contextless login for users through NetStorage, you must enable LDAP Clear Text passwords. Contextless login lets users log in without specifying their entire User object context. You can enable LDAP clear text passwords during the NetWare 6 installation or after the NetWare 6 installation using ConsoleOne. 5.10 NWDEPLOY Authentication Problems NWDEPLOY might be unable to authenticate to a new node when you attempt to add that node to an existing cluster. This problem occurs more frequently when either SLP or DNS isn't configured properly on servers or clients. This problem can be resolved by doing any of the following: - Before running NWDEPLOY, manually map a drive from your client to volume sys: on the new node. - Add the server name and IP address of the new node to DNS. - Add the server name and IP address of the new node to the Windows Hosts file on the client machine where you run NWDEPLOY. - Configure SLPDA to discover the server name of the new node. 5.11 Novell iManager 1.2.2 Issues - Selecting User Objects: If you perform an operation that requires you to select a User object, and the list of User objects that match your search criteria contains more than 15 to 20 objects, you can select objects only from the first objects in the list. If you click to see more User objects, you can no longer select any objects. To resolve this, refine your search to find fewer User objects. - Using the Keyboard to Expand Roles: If you use the Tab key to move to a role in Novell iManager and then press Enter to expand the role and view the tasks assigned to that role, your browser will GPF. To prevent this from happening, use the mouse to expand roles. 5.12 Restoring iMonitor 1.5 Custom Settings Any custom settings you previously specified in the iMonitor configuration file are overwritten during the installation of the NetWare 6 Support Pack. To restore those settings, open ndsimon.ini (located in the same directory as the iMonitor executable) and make the desired changes. To preserve your previous settings, you might want to manually copy them to another file before the installation. 5.13 Novell Native File Access for Macintosh (AFP) 5.13.1 Filename Character Limit Version 2.2 of the Apple Filing Protocol (AFP) limits filenames to a maximum of 31 characters while the Mac OS X implements AFP 3.0, which supports filenames longer than 31 characters. Because the afptcp NLM uses AFP 2.2, you should keep your filenames to no more than 31 characters to successfully copy and move files to an AFP volume. 5.14 NFS and Native File Access for UNIX Issues 5.14.1 Error 9600 When NDSILIB is autoloaded during some operations, it might not load and returns Error 9600. To continue the operation, perform NFSSTOP and then execute the operation again. 5.14.2 NIS Services The bootparam and netgroup maps are not supported in this release. 5.14.3 Makenis Issues - Upon executing makenis in a server with no replica when the Master replica is down, instead of displaying a DS error, a series of messages similar to the following are displayed erroneously: Nullpointer passed to routine Kmutex. - Do not use makenis to delete users and groups. Use ConsoleOne instead. 5.14.4 Pkernel Messages If the pkernel screen displays messages similar to the following after executing yppush, you can ignore them (they do not affect functionality in any way): Out of memory, cannot create UDP Client handle. 5.14.5 ConsoleOne Snap-in Issues - If the connection to the administered server under NFSAdmin Server is lost, log out and log in again to regain functionality for ConsoleOne administration. - While administering multiple servers and switching between them, it is possible that the data you view is for the previous server. Click the corresponding Server object to display its data. 5.15 Novell Native File Access for Windows (CIFS) 5.15.1 Certain Double-Byte Characters Not Supported in File and Directory Names CIFS does not currently support certain double-byte characters used in file and directory names. Specifically, the double-byte backslash (\) and the double-byte dash (-) characters do not work. (The Unicode value for the double-byte backslash is 0xFF3C; the Unicode value for the double-byte dash is 0x817C.) We recommend that you use the single-byte backslash (unicode value) and dash (unicode value) characters in file and directory names. 5.15.2 Double-Byte Characters in Usernames You must use ConsoleOne to manage CIFS passwords for users who have double-byte characters in their usernames. 5.15.3 Use ConsoleOne to Configure Your Windows/CIFS Network Environment After you have installed the NetWare 6 Support Pack, you must configure your Windows/CIFS network environment with ConsoleOne. Previously, CIFS parameters were configured by manually editing sys:\etc\cifs.cfg. That file now contains a note telling you to use ConsoleOne for CIFS configuration. If eDirectory is reinstalled on a server running CIFS with the NetWare 6 Support Pack, ConsoleOne CIFS management does not automatically reimport the cifs.cfg configuration into ConsoleOne. To reimport the configuration, un comment lines starting with ### from sys:etc\cifs.cfg and then run CIFSSTOP and CIFSSTRT. 5.15.4 Enable Unicode on a CIFS Server with DFS Junctions Unicode must be enabled on a CIFS server in order for DFS junctions to work. You can enable Unicode in the following ways: - During the Installation: Make sure the Enable Unicode check box is checked on the first Server Properties screen. - After the Installation Using ConsoleOne: Right-click the Server object in ConsoleOne and then click Properties > CIFS > Config. Make sure the Unicode check box is checked, and then restart CIFS by running CIFSSTOP and CIFSSTRT. 5.15.5 CIFS Server Selected as a Master Browser in Domain Mode In Domain mode, when the CIFS server is selected as a master browser, it maintains a list of servers in the domain only on the local subnet. Subsequently, servers in the domain that are located on other subnets do not appear in Network Neighborhood. 5.16 Joining a NetDevice NAS Appliance into a NetWare 6 eDirectory Tree NetWare 6 Support Pack 1 and later includes fixes to eDirectory for NetWare 6 that allow a Novell NetDevice NAS appliance to join a NetWare 6 eDirectory tree. If you are planning to deploy a NetDevice NAS appliance into a NetWare 6 eDirectory tree, you must make sure that the NetWare 6 server in the replica ring that holds the partition which the NetDevice NAS appliance is targeted to join is running NetWare 6 Support Pack 1 or later. 5.17 Novell Storage Services 5.17.1 NSS Enhancements - Beginning with NetWare 6 Support Pack 2, a new utility has been added. The NSS Management Utility (nssmu.nlm) allows you to administer partitions, volumes, and pools. This utility was designed to help administrators recover from volume sys: failures and similar situations. The NSS Management Utility is not meant to replace ConsoleOne or any other Web-based management utility. This utility will run only on NetWare 6.0 and later. To use the utility, enter LOAD NSSMU.NLM at the server console. - Beginning with NetWare 6 Support Pack 2, new sys: recovery commands have been added. For more information on the commands, see "SYS: Recovery Commands" in the Novell Storage Services online documentation (http://www.novell.com/documentation/lg/nw6p/nss_enu/ data/h98xrv3c.html#h98xrv3c). - Beginning with NetWare 6 Support Pack 3, additional NSS utilities have been included. See TID 10079738 (http://support.novell.com/cgi-bin/search/searchtid.cgi?/10079738.htm) for more information. 5.17.2 Logging In with a Windows Client If you are trying to access a junction and you get an error that says Bad User Name or Password, this means that you used different usernames and passwords to log in to your workstation and the network. DFS requires that you use the same username and password for workstation and network login, otherwise login fails. 5.17.3 Windows Client Limitation with DFS Junction Levels Due to a limitation in Windows 95/98/ME/XP clients, if you create a junction that points to a volume that contains another junction, your second junction might fail because these clients don't support multilevel junctioning (that is, having more than one junction in a path). Multilevel junctions are supported on Windows NT 4 and Windows 2000 clients. 5.17.4 DFS Requires Unicode Support Unicode must be enabled on a CIFS server in order for DFS junctions to work. You can enable Unicode in the following ways: - During the Installation: Make sure the Enable Unicode check box is checked on the first Server Properties screen. - After the Installation Using ConsoleOne: Right-click the Server object in ConsoleOne, then click Properties > CIFS > Config. Make sure the Unicode check box is checked, then restart CIFS by running CIFSSTOP and CIFSSTRT. 5.18 Apache Web Server If you are running the Apache Web Server, you should read the bulletin 20020617 (http://httpd.apache.org/info/security_bulletin_20020617.txt). Apache updates are available at the Apache Web site (http://www.apache.org/dist/httpd/binaries/netware). The Support Pack contains updates to the Apache Web server. 5.19 Novell TCP/IP - Once the server is configured with a supernet mask, it behaves like an end node when IP Forward gets disabled. It continues to behave like an end node, even if the mask is changed to a non-supernet mask and the system is reinitialized. To make it work like a router, change the state of the IP packet forwarding or RIP or LAN Static Routing in INETCFG and reinitialize the system. - With the CIDR mask on, some valid host IDs ending in .255/.0 cannot be bound. - Load balancing might not work when all the clients' IP address are mapped to a single server NIC and all the clients start data transfer simultaneously. - EGP and OSPF are not completely functional in this release. - Ensure that at least 512 MB of RAM is available where the server is to be stressed with heavy network operations. - If the IP address used by an application is changed, it might stop working. For more information, refer to the documentation for the particular application. 5.19.1 Configuration through INETCFG - In machines with multiple NICs, if already-in-use IP addresses are selected for binding, an ARP conflict error message is displayed (in the logger screen) for each binding. The system should automatically trigger unbinding of the IP addresses. If the binding persists, manually delete the bindings and reinitialize the system. 5.19.2 IPTRACE.NLM - A blank space is not permitted between the command arguments and the equal sign (=) following them. - Source option is not supported in this release. - In some destination addresses, the utility stops at the hop before the target. 5.19.3 NIC Teaming Currently, only one user-specified protocol is supported. 5.19.4 Default Behavior Changes Compared to CSP8 Netware 6 Support Pack 2 - IP packet forwarding is disabled. The NetWare server works as an end node. - RIP is disabled. The server is not be able to listen and transmit RIP routes. - LAN Static Routing is enabled. When NetWare is installed with the default gateway and you load INETCFG for the first time, the gateway information is transferred to \etc\gateways. Therefore, when the LAN Static Routing is enabled by default, the default gateway from \etc\gateways is activated as the default route. 5.20 Perl for NetWare - Crypt() and Flock() functions are not supported on NetWare. - Unicode character encoding schemes, except utf-8 are also not supported. - Encode::Guess is not supported. - Accessing MySQL4.1.1-alpha from Perl is currently nonfunctional. - Rename function is not implemented. - Failure of UCX methods will be indicated by an unknown error. The error description given by the UCX call is currently not available for the Perl script. - Scripts that use the 'Thread' and 'threads' modules may not work as desired. - When multiple CGI scripts (more than about 40), each doing complex operations, are run simultaneously then the Apache 1.3.x, the Web server either hangs or abends. The fix for this will be available in the future builds. - The readlink built-in procedure always returns an undefined value. According to Perl's definition of the function, this is the correct behavior on a system such as NetWare that does not support symbolic links. - To execute system() command from the Perl Web interface you need to authenticate with administrator rights. This feature is provided for enhanced security. In case you do not authenticate, no error is returned. We recommend to use the perl system () without the load prefix to load an NLM. However this method of executing the NLMs does not update the $? variable. - Complex scripts running from the console might give the following message: Process did not relinquish control frequently. 5.21 Timesync Issues 5.21.1 Auto-Discovery of IPX Single Server If there is a pure IPX single server in a tree, then the IP/IPX secondary server does not auto-discover the single server. This can be resolved by the completing the following: 1. Set Timesync Configured Sources = ON. 2. Set Timesync Time Source = . 3. Set Timesync Restart Flag = ON. 5.21.2 Firewall Considerations with Timesync.nlm Timesync.nlm includes a modified method for exchanging time over NTP over the firewall. A new SET parameter (NTP Client Port) has been added to configure the source port of an NTP Request sent from within a firewall. Ideally, you should configure one server to get time from the Internet. The firewall should be configured to allow packets to and from this one server, on the specified NTP Client Port. All other servers within the firewall should get their time from this configured server. For more information, see Troubleshooting NTP Time Synchronization (http://www.novell.com/coolsolutions/nds/features/trench es/tr_troubleshooting_ntp.html) on the Cool Solutions Web site. 5.22 Novell Small Business Suite Beginning with NetWare 6 Support Pack 2, a POP Forwarding Agent is included. For more information on setting up this agent, see pfa_read.pdf located in \products\nsbs of the Support Pack or in sys:\system after the Support Pack has been installed. 5.23 Btrieve Updates For the latest Btrieve updates, install Pervasive SQL 2000i Service Pack 4, the latest version of the Pervasive database. For more details, see the Pervasive Web site (http://www.pervasive.com.). 5.24 Server Communication Issue Previously, Novell Ethernet network drivers have always evenized Ethernet II frames. Beginning with NetWare 6 Support Pack 2, Ethernet II frames are no longer evenized by default. A new LAN driver load line option called EVENIZE_ON has been created to allow you to re-enable frame evenization, as might be needed by older NetWare installations. In the past, routers have been known to reject nonevenized packets. Currently, we have found that many new routers and clients reject evenized packets. Many network operating systems and clients (SunOS, Windows NT/2000/XP, Linux, etc.) do not evenize Ethernet II frames, and most routers accept both evenized and nonevenized frames. Modules affected by the change are msm.nlm and ethertsm.nlm. If network communication problems appear due to dropped packets, you should first turn Ethernet II frame evenization on using the EVENIZE_ON driver loadline option. 6.0 NLM Programs Bound into Server.exe This Support Pack contains a server.exe file which has bound into it a number of important NLM programs. If any of these NLM programs is already in your startup directory (that is, you received one of these NLM programs outside of this Support Pack), these NLM programs are automatically deleted during Support Pack installation. server.exe includes the following NLM programs: Pmlodr.nlm January 23, 2003 Pver500.nlm February 27, 2003 Server.nlm December 12, 2003 Xldr.nlm February 11, 1999 7.0 Driver Issues This support pack contains some third party drivers for LAN,WAN, Storage, and Printers. The latest updates on these are available from the third party vendor web site. The latest certified Storage drivers are available at http://developer.novell.com/devres/storage/drivers/index.html. The latest certified LAN drivers are available at http://developer.novell.com/devres/lan/drivers/index.html. 7.1 Epson Gateway For information on the EpsonNet NDPS Gateway 2.3, see \tools\espongw23_1.txt. 7.2 Using Netr4m.ham If you are using the netr4m.ham driver, you will need to manually copy the updated driver from the Support Pack to c:\nwserver\drivers. 7.3 HP Hot-Plug Stops Working When performing an upgrade to NetWare 6 Support Pack 3 or later the HP Hot-Plug driver (cpqsbd.nlm) is moved from the DOS partition to the sys:, hence hot-plug functionality may be affected. If previously functional Hot-Plug slots are not visible through NCMCON after the upgrade, then most likely cpqsbd.nlm was not loaded. To resolve this, copy the cpqsbd.nlm from sys:system\drivers.new directory to sys:system, then load it to resume Hot-Plug functionality. 7.4 I2o Drivers Removed Beginning with Support Pack 4, the i20pci.ddi and i2opci.nlm have been removed and are no longer supported. 7.5 Updated Dell Drivers Updates for the following Dell drivers are available on Dell's Web site (http://www.dell.com): pedge3.ham, perc2.ham, dellsbd.nlm and associated .xdi files. The latest certified Storage drivers are available at http://developer.novell.com/devres/storage/drivers/index.html. 8.0 Uninstalling the Support Pack If you selected the Backup option during the Support Pack installation, files that are overwritten by the Support Pack files are backed up to sys:system\backsp5 (or to the location you specified) so that you can restore the server to its original state if necessary. If you didn't select the Backup option, you can't uninstall the Support Pack. Do not uninstall the Support Pack if you installed any products or patches after the installation of the Support Pack. To uninstall the Support Pack, complete either one of the following procedures: 1. At the server console prompt, enter NWCONFIG. 2. Select Product Options > Install a Product Not Listed. 3. Press F3, then specify the path to the backup files (sys:system\backsp5 or the location you specified). OR 1. At the server console prompt, enter NWCONFIG. 2. Select Product Options > View/Configure/Remove Installed Products > SPACK. 3. Press Delete, then select Yes. 8.1 Novell LDAP Server Does Not Support Downgrades from Support Packs If you install a Support Pack and then later remove it, you might find that the LDAP server no longer responds to client requests. To resolve this, use ConsoleOne or iManager to manually create new LDAP Server and Group objects, reassociate the LDAP Server object with the NCP Server object, and remove the obsolete Server and Group objects. After completing either procedure, be sure to review the contexts of the LDAP Group and Server objects to ensure they refer to each other properly. Also make sure that security measures such as X.509 certificates are created and associated correctly and that SSL is configured accordingly. Using ConsoleOne 1. Open a pre-Support Pack version of ConsoleOne (from the NetWare 6 CD) that exactly matches the version of the LDAP server you want to run, then log in with administrator privileges. 2. At the same tree location where the upgraded LDAP objects exist, create a new LDAP Server object and a new LDAP Group object. These new objects contain the original defaults for the specific version of the LDAP server and group. Be aware that shared Group objects are generally not compatible across multiple LDAP server versions. You need to restore any changes and associations that had been made to these objects prior to the installation of the Support Pack. 3. Review the properties of the NCP Server object associated with this Support Pack change. 4. Right-click the NCP Server object, then click Properties. 5. On the Other tab, replace the LDAP server name listed in the Attributes list with the new LDAP Server object name. 6. Delete the obsolete LDAP Server object. 7. Delete the obsolete LDAP Group object after it is not being shared among other LDAP Server objects. Using Novell iManager 1. Log in to iManager as a user that has rights to modify LDAP. 2. Click LDAP Management > Delete LDAP Object. 3. Delete the Server and Group objects that will be replaced. 4. Click Create LDAP Object. The object class box will display LDAP Server. The LDAP Server object must be created first. 5. Type the name of the object, usually LDAP Server - . 6. Browse for the context to create the object. This should be the same context where the server object resides. Click Next. 7. Browse for and select the host Server object, then click Start. 8. Click Create LDAP Object > LDAP Group in the Object Class field. 9. Type the name in the Object Name field. LDAP Group - . 10. Browse for the context where the newly create LDAP server object resides, then click Next. 11. Browse for and select the newly create LDAP Server Object, then click OK >Next. 12. Follow the prompts, then click Start. 8.2 Native File Access for UNIX Uninstall Issues When uninstalling Native File Access for UNIX, delete the NFAUUser object. Downgrading Native File Access for UNIX to an earlier version is not supported. 9.0 Files in the \Tools Directory For a list of files in the \tools directory, see tools.txt at the root of the Support Pack. 10.0 Changes Since Last Support Pack For a list of the changes made since the last Support Pack, see TID For information on the latest Support Pack issues, see TID 10091736 (http://support.novell.com/cgi-bin/search/searchtid.cgi?/10091736.htm) at http://support.novell.com. 11.0 Product Testing The Support Pack has undergone component testing, core OS, system, and integration testing with other Novell products. The Support Pack was also tested with the following: - NetWare 6.0 Support Pack 5 - NetWare 6.5 Support Pack 2 - NFS Gateway Support Pack 2 - GroupWise Messenger 1.0 Support Pack 2 - GroupWise 6.5 Support Pack 2 - BorderManager 3.8 Support Pack 2 - Novell Client 4.90 Support Pack 2 for Windows NT/2000/XP 12.0 Additional Documentation In addition to this Readme file, the following sources provide additional information about the Support Pack: - For installation instructions, see nw6sp5.txt located at the root of the Support Pack. - For more information on the latest Support Pack issues since the Support Pack was released, see TID 10091736 (http://support.novell.com/cgi-bin/search/searchtid.cgi?/10085454.htm). - Updated documentation for NetWare 6 is at the Novell Documentation Web site (http://www.novell.com/documentation/lg/nw6p). - EpsonNet NDPS Gateway 2.3, readme located in \tools\espongw23_1.tx of the Support Pack. - For information about files in \tools, see tools.txt located at the root of the Support Pack. 13.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. You may not use, 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 2004 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, NetWare, BorderManager, ConsoleOne, GroupWise, NDPS, Novell Directory Services and NDS, and Novell iFolder are registered trademarks of Novell, Inc. in the United States and other countries. eDirectory, Internetwork Protocol Exchange and IPX, NetWare Core Protocol and NCP, NetWare Loadable Module and NLM, NetWare Storage Management Services and NetWare SMS, Novell Cluster Services, Novell Distributed Print Services, Novell eGuide, and Novell Storage Services are trademarks of Novell, Inc. All third-party products are the property of their respective owners. Self-Extracting File Name: nw6sp5ee.exe Files Included Size Date Time ..\ NW6SP5EE.TXT (This file) ..\NW6SP5EE\ NW6SP5EE.ISO 730726400 6-30-2004 12:41:06 pm ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. -----------------------------------------------------------------