NW51SP8 English-Italiano Overlay CD (128bit)

Restriction Status:  Open

Name Size
license_agreement.txt2.1 KB (2252)
nw51sp8ei.iso661.1 MB (693268480)
readme_2970950.html117.8 KB (120688)
Related Product(s) Patch Status for Product Superseded By
NetWare 5.1 Active

platforms

NetWare 5.1

localizations

English

This document (2970950) is provided subject to the disclaimer at the end of this document.

Associated File

Click the filename to download: nw51sp8ei.iso 693268480 bytes 28Feb2005 11:14AM

Abstract

NetWare 5.1 Support Pack 8 English-Italiano Overlay CD with 128-bit encryption.

MD5 Checksum: b33a669f29a917e27511c2ad986256b5

Installation Instructions

NetWare 5.1 Support Pack 8 Overlay CD Image
January 2004

Overview

This file contains the NetWare 5 Support Pack 8 Overlay CD
images, which lets you create a bootable CD that will
install NetWare 5.1 and NetWare 5.1 Support Pack 8
simultaneously on a server. This image is in ISO format.

For more information on Support Pack issues, see
nw5_iss.txt at the root of the created CD.

For information on the latest Support Pack issues, see TID
10085454 at http://support.novell.com/search/kb_index.htm.

To order the Support Pack CD, go to
http://support.novell.com/tools/csp/orderinfo.html

Table of Contents

1.0 Support Pack Installation
     1.1 Requirements
     1.2 Suggested Software
     1.3 NDS7 Install Not Supported
     1.4 Creating a NetWare Overlay CD
     1.5 Prior to Installation
     1.6 Installing NetWare Using the Overlay CD
     1.7 Install Pauses after Choosing to Restart Server
     1.8 Product Versions Not Updated in Installed
          Products List
     1.9 Update Product Versions after Accelerated Upgrade

2.0 Issues
     2.1 Upgrading the Support Pack
     2.2 LSI IDE Driver
     2.3 LDAP Authentication
     2.4 Security Domain Error
     2.5 NetWare 5.1 Install Hangs
     2.6 NWDEPLOY and Certificate Server
     2.7 Tools Directory Not Included
     2.8 Using a Response Files
     2.9 -625 error during NW51 Deployment Manager
          Post-install of Certificate Server
     2.10 Abend in TCPIP during the Install

3.0 Documentation Conventions

4.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 NDS7 Install Not Supported

          This overlay no longer includes an option to
          install NDS 7. This overlay will install NDS8
          only. If you need to install NDS7, you must
          install the server from an original NetWare 5.1
          CD and then install the NetWare Support Pack.

     1.4 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 CD-burning software, use 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.5 Prior to Installation

          Make sure the directory c:\nwupdate has no old
          files in it left from a previous install before
          you begin to copy files into this directory. When
          the installation is complete, delete the
          c:\nwupdate directory.

     1.6 Installing NetWare Using the Overlay CD

          After you have created an overlay CD, you can
          install NetWare following the installation or
          upgrade documentation.

           1. Insert your overlay CD into the server's CD
              drive and power on the server.
           2. Follow the on-screen prompts.

          The NetWare 6 documentation is available at
          http://www.novell.com/documentation/lg/nw6p/index
          .html.

     1.7 Install Pauses after Choosing to Restart Server

          After the GUI install prompts to restart the
          server, an install script runs to install
          additional components. This script takes about
          several minutes to complete.

           The version numbers are updated in the Installed
          Products list (products.dat), then the server is
          restarted.

     1.8 Product Versions Not Updated in Installed
          Products List

          If your Installed Products list is not displaying
          the correct product versions, complete the
          following:

           1. Make sure the pupdate.ips file is found in
              your sys:\system directory.
           2. In NWCONFIG, select Product Options > Install
              a Product Not Listed.
           3. Press F3, then enter the path
              sys:\system\pupdate.ips.

     1.9 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 ProductNot
              Listed.
           3. Press F3 and then specify the path, including
              the volume name to pupdate.ips. For example,
              sys:\system.

          The product versions will then be updated.

2.0 Issues

     2.1 Upgrading the Support Pack

          If you have a NetWare 5.1 server and want to
          update it to include the current Support Pack,
          you should install just the NetWare 5.1 Support
          Pack. Running the overlay as an upgrade is
          supported only when upgrading from NetWare 5.0 or
          earlier.

     2.2 LSI IDE Driver

          To use LSI's IDE driver instead of Novell's
          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. Highlight the IDEATA driver and 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 enter the driver name.
           4. Arrow down and select Return to driver menu.
           5. Arrow down and select Continue, and continue
              with the installation.

          If you are using a Default installation, you will
          need to use Novell's IDEATA driver.

     2.3 LDAP Authentication

          If you cannot log in at the LDAP authentication
          screen during a NetWare 5.1 overlay install,
          update your sys:etc\hosts file with your IP
          address and server name.

     2.4 Security Domain Error

          If you install a NetWare 5.1 server (without any
          Support Packs) into the same replica ring as a
          NetWare 6 server or a NetWare 5.1 server with
          Support Pack 5 or later, the security
          certificates will not be created successfully and
          the following error will be displayed:

          Error while contacting security domain
          infrastructure key server. Error #125

          This is because the default NetWare 5.1 version
          of NICI (1.5.x) is incompatible with NICI version
          2.02 in NetWare 6 and NICI version 2.01 in
          NetWare 5.1 Server with Support Pack 5 or later.
          To resolve this, use the overlay NetWare 5.1
          Support Pack 7 to install the server.

     2.5 NetWare 5.1 Install Hangs

          If you install a NetWare 5.1 server into a tree
          with a NetWare 5.1 Support Pack 4 or earlier and
          a NetWare 5.1 Support Pack 5 or later server, the
          install will hang. This is because the default
          NICI version 1.5.x in NetWare is incompatible
          with NICI version 2.01 in NetWare 5.1 Server with
          Support Pack 5 or later.

          To resolve this, upgrade the NICI on all the
          servers by installing the latest Support Pack.
          Install new servers into the tree only using a
          NetWare overlay install CD.

     2.6 NWDEPLOY and Certificate Server

          If you are running NWDEPLOY from a workstation to
          install Certificate Server on a server, you might
          receive an error. The error occurs when the
          installation reaches 100% and it attempts to
          extend the schema. To resolve this, use the
          Install option on the Server GUI.

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

     2.8 Using a 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 product documentation at
          http://www.novell.com/documentation/lg/nw51.

     2.9 -625 error during NW51 Deployment Manager
          Post-install of Certificate Server

          If you receive a -625 error during the
          post-install of the Certificate Server remotely
          with NetWare 5.1, try copying the
          ni\bin\pkiwrap.dll from overlay to c:\program
          files\common files\novell\ni\bin\ and then retry
          the post-install.

     2.10 Abend in TCPIP during the Install

          If there are more than three servers in the
          eDirectory tree, and if the servers in the
          replica ring have the NCP Packet Signature set to
          2 or 3, a new server being installed into the
          tree might abend in tcpip.nlm.

          To resolve this, change this setting on the
          servers that hold a replica. To set this, load
          Monitor and select Server Parameters > NCP > NCP
          Packet Signature Option > 0 or 1. See also TID
          10057304.

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

4.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 � 2003-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, NetWare Core Protocol and NCP, and Novell
     Directory Services and NDS are trademarks of Novell,
     Inc.

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

Symptom

NetWare 5.1 Support Pack 8 Known Issues
February 2005

This is the last Support Pack for NetWare 5.1. Updates
released after this Support Pack should be installed after
installing this Support Pack.

1.0 Installation Issues
 1.1 Sys: Does Not Mount after Install
 1.2 Reinstalling the Support Pack with IDE Hardware
 1.3 ZENworks for Servers
 1.4 Increase File Handles in Config.sys
 1.5 MailFilter 1.5
 1.6 ManageWise 2.7
 1.7 Error Message with Vtxkill.nlm
 1.8 Install Appears to Stop
 1.9 Installing Updated LAN and Storage Drivers
 1.10 Installing Novell Products after the Support Pack
 1.11 Install Backup Takes Longer
 1.12 Simultaneous NetWare 5.1 and Support Pack Install
 1.13 eDirectory Updates
 1.14 Running Accelerated Upgrade
 1.15 NWDEPLOY and Certificate Server
 1.16 JVM 1.3.1 Option
 1.17 Understanding When ConsoleOne Is Updated

2.0 New Issues for this Support Pack 8
 2.1 Abends After Adding Volume Space Or Expanding
  Pools
 2.2 Deactivating Storage Devices
 2.3 Cannot Set Simple Password Using NetWare Remote
  Manager
 2.4 Using Scopes with SLPDA
 2.5 Problem Loading NSS Volumes Created with NSS
  Administration Menus

3.0 Issues from Support Pack 7
 3.1 Grace Connections Changed
 3.2 Using ACPI Drivers
 3.3 NSS Volume Fails to Mount After Device
  Deactivation and Reactivation
 3.4 Down Command Powers Off Server with ACPI Drivers
 3.5 Macintosh Extended Characters Not Supported
 3.6 Packet Receive Buffers Default Changed
 3.7 SMDR Resolution Support
 3.8 SMDR IP Selection Support
 3.9 Timesync Changes
 3.10 Accepting Multiple Certificates with IE6 browser
 3.11 Resolving Port Conflicts
 3.12 ConsoleOne 1.3.5 and JVM 1.4.x Not Supported
 3.13 Error When Loading Timesync
 3.14 Only First Node Can Join a Cluster

4.0 Issues from Support Pack 6
 4.1 FTP Server Issues
 4.2 Apache Web Server
 4.3 NDPS Error When Attaching to Queues
 4.4 iPrint Map Designer
 4.5 Timesync Issues
 4.6 JVM Issues
 4.7 Timesync with Secondary Server
 4.8 Confirming Security Certificates When Accessing
  the NetWare Management Portal

5.0 Issues from Earlier Support Packs
 5.1 Location of CLIB Changed
 5.2 Remove SET CLIENT FILE CACHING ENABLED=OFF from
  Autoexec.ncf
 5.3 Error When Loading Timesync
 5.4 NetWare Web Manager Reports Incorrect TCP Port
 5.5 Daylight Savings SET Parameters
 5.6 Installing DirXML
 5.7 Novell IPP Server Update
 5.8 Using WebDav and WebPublishing
 5.9 JVM Issues
 5.10 Custom XServer Backgrounds Reset
 5.11 SSL Certificate Error
 5.12 Installing GroupWise 5.5 or the Enhancement Pack
 5.13 File Update for ManageWise 2.7
 5.14 Changing the Server Configuration
 5.15 Firewall Considerations with Timesync.nlm
 5.16 BorderManager Issues
 5.17 NDPS Issues
 5.18 NetWare Storage Management Services (SMS) Issues
 5.19 Creating Files or Directories with Double-byte
  Characters Using FTP Server
 5.20 ADSync with ConsoleOne Issue
 5.21 NetWare Management Portal Issues
 5.22 Remote Console and RCONJ Issues
 5.23 Driver Issues
 5.24 WebSphere Issues
 5.25 WebSearch Changes

6.0 NLM Programs Bound into Server.exe

7.0 Product Testing

8.0 Third-Party Product Issues
 8.1 Dell Server Management Software (AppCD)
 8.2 HP Hot-Plug Stops Working
 8.3 Pervasive Updates
 8.4 NetWare for SAA and Oracle Products Not Tested
 8.5 Symantec Norton AntiVirus Enterprise 7.5
 8.6 Tobit FaxWare Running on Novell for Small
  Business and NetWare for Growing Business

9.0 Removing the Support Pack from the Server
 9.1 Uninstalling the Support Pack
 9.2 Downgrading to a Previous NDS Version
 9.3 Uninstall the Support Pack When Running NDS8

10.0 Updated TCP/IP Documentation

11.0 Upgrading to NetWare 6.x

12.0 Files in the \TOOLS Directory

13.0 Changes Since Last Support Pack

14.0 Additional Documentation

15.0 Documentation Conventions

16.0 Legal Notices

1.0 Installation Issues

 Installation instructions are in nw51sp8.txt located
 at the root of the Support Pack.

 1.1 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\backsp8\storage\<driver_name>.* to
  c:\nwserver. Be sure to copy without using a file
  extension (file.*) so you get the driver's
  associated configuration file.

 1.2 Reinstalling the Support Pack with IDE Hardware

  If you install this support pack again after
  having already installed it, you might be
  prompted to enter a new slot choice for
  ideata.ham after you restart the server. When the
  ideata.ham first loads to press Enter with a new
  slot choice and write down the slot number. After
  the server starts, edit c:\nwserver\startup.ncf
  and enter the slot number your wrote down
  earlier. This eliminates the slot prompt on
  startup. This change is necessary to support
  changes in new hardware.

 1.3 ZENworks for Servers

  If you are installing this Support Pack on a
  server with ZENworks for Servers installed, the
  TED component of ZENworks for Servers 3 might not
  start after installing this Support Pack. If TED
  exits with a -105 error "Cannot resolve DNS
  name", modify the sys:\etc\hosts file to include
  the fully qualified domain name and then restart
  TED.

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

 1.5 MailFilter 1.5

  Before installing the Support Pack on a server
  with MailFilter 1.5 installed, unload mfnrm.nlm,
  the MailFilter/Fax Remote Management snap-in for
  NetWare Management Portal. This snap-in to
  portal.nlm and httstk.nlm will prevent these
  modules from unloading properly during the
  Support Pack install.

 1.6 ManageWise 2.7

  If ManageWise is running on your server during
  the Support Pack install, the install script will
  stop because Java cannot unload with ManageWise
  2.7 running.

  To work around this problem, complete the
  following steps:

   1. In the autoexec.ncf file, comment out the
      following ManageWise lines:
      netxplor.ncf
      nma5.ncf
      mw_auto.ncf
      lanz.ncf (if loaded)
   2. Restart the server.
   3. Install the NetWare 5.1 Support Pack.
   4. In the autoexec.ncf file, remove the comment
      from the ManageWise lines listed in Step 2.
   5. Restart the server by entering RESET SERVER.

 1.7 Error Message with Vtxkill.nlm

  If there are problems unloading Java, follow the
  instructions in the error message which is
  displayed:

  The Support Pack is attempting to Unload
  vtxkill.nlm. You might need to toggle screens and
  press a key.

 1.8 Install Appears to Stop

  If the install program for the Support Pack
  appears to have stopped, toggle through the
  console screens to ensure all programs have
  terminated. Occasionally, a program (like
  VTXKILL) will require user intervention to quit.
  The install will then continue.

 1.9 Installing Updated LAN and Storage Drivers

  Due to the wide variety of hardware
  configurations, the updated LAN and storage
  drivers might not work in your specific
  environment.

  If you chose to install the updated LAN and
  storage drivers during the Support Pack install
  and encountered a problem, you should use the
  drivers you were using prior to installing the
  Support Pack.

  The old drivers were backed up to
  c:\nwserver\backsp8 (whether or not you chose to
  install the updated LAN and storage drivers).

 1.10 Installing Novell Products after the Support Pack

  The Support Pack detects which products are
  installed and automatically updates the files
  needed for those products. Products installed
  after the Support Pack might overwrite newer
  files installed by the Support Pack.

  For example, if you install a Novell product like
  BorderManager after installing the Support Pack,
  you need to reinstall the Support Pack;
  otherwise, some features (like VPN) might not
  function and some files might be overwritten by
  an older version.

 1.11 Install Backup Takes Longer

  The Backup option might take longer than previous
  Support Packs because it also backs up files of
  additional products that will be updated.

 1.12 Simultaneous NetWare 5.1 and Support Pack Install

  You can download a CD image that installs NetWare
  5.1 and the NetWare 5.1 Support Pack
  simultaneously. See the Consolidated Support Pack
  Web site (http://support.novell.com/tools/csp)
  for information on downloading the image or the
  Consolidated Support Pack DVDs.

 1.13 eDirectory Updates

  The Support Pack does not include updates for
  versions of eDirectory that shipped after NetWare
  5.1 shipped. If you have upgraded eDirectory to a
  newer version, such as eDirectory 8.6.2 or 87,
  you will need to get the updates for these
  products from the Novell Downloads Web site
  (http://download.novell.com).

  Some products might be affected if you do not
  install the eDirectory updates after installing
  the Support Pack.

 1.14 Running Accelerated Upgrade

  Beginning with Support Pack 8, accelerated
  upgrades are no longer suppported. Select a
  different method of installation.

 1.15 NWDEPLOY and Certificate Server

  If you are running NWDEPLOY from a workstation to
  install Certificate Server on a server, you might
  receive an error. The error occurs when the
  installation reaches 100% and it attempts to
  extend the schema. To resolve this, use the
  Install option on the Server GUI.

 1.16 JVM 1.3.1 Option

  If you choose to install the JVM 1.3.1 during the
  Support Pack installation, you are prompted with
  Have you reviewed the file nw51_iss.txt for
  product dependencies? You must read this file,
  then select Yes. If you select No, ConsoleOne
  1.3.5 is installed but JVM 1.3.1 is not
  installed. ConsoleOne 1.3.5 requires JVM 1.3.1 in
  order to run. To resolve this, reinstall the
  Support Pack and read the file nw51_iss.txt.

 1.17 Understanding When ConsoleOne Is Updated

  ConsoleOne is updated if any of the following
  conditions is met:

  - You choose to have the Support Pack install
     JVM 1.3 or you already have JVM 1.3 installed
  - ConsoleOne 1.3x or later is installed
  - You have a version of eDirectory earlier than
     8.7

2.0 New Issues for this Support Pack 8

 2.1 Abends After Adding Volume Space Or Expanding
  Pools

  If the server abends after adding volume space or
  expanding pools, there may be an issue with the
  disk drivers. To resolve this, use the older
  SCSIHD.* files found in
  c:\nwserver\backsp3\drivers, and copy these files
  to c:\nwserver. You should contact the storage
  vendor for updated drivers that resolve this
  problem. This issue has been reported with
  Adaptec and other storage drivers. The files
  aarichd.ham and aarichi.ham do not have this
  issue and have replaced aarich.ham. This issue
  has not been reported with the RAID or PERC
  drivers contained in this support pack.

 2.2 Deactivating Storage Devices

  If you deactivate a device using Monitor (from
  the Storage Devices menu), the selected storage
  device is deactivated; however, Monitor never
  returns, and it hangs on the Deactivate Drive
  prompt. Although the server continues to function
  properly, all storage management processes also
  appear to hang from that point on. To resolve
  this, reboot the server.

 2.3 Cannot Set Simple Password Using NetWare Remote
  Manager

  When running NetWare 5.1 Suppo4 Pack 8 in a mixed
  tree with NetWare 6 and NetWare 6.5 servers, you
  might receive the following error when setting
  simple passwords with NetWare Remote Manager
  running from a NetWare 5.1 server:

  Http Error Code 412
  Unable to set password for
  .user100.Novell.ST-INCREDIBLES.
  NMAS error = -1659 which is
  NMAS_E_ACCESS_NOT_ALLOWED

  To resolve this, use Novell iManager from a
  server running NetWare 6.5 to set simple and
  universal passwords.

  This issue is resolved using an updated NMAS
  client.

 2.4 Using Scopes with SLPDA

  In this Support Pack, SLP does not support the
  use of an Unscoped Scope, but in some previous
  NetWare 5.1 Support Packs it did not prevent the
  naming of a scope as UNSCOPED. Slpda.nlm now
  enforces this prohibition, and it will not load
  with an scope named UNSCOPED.

  To resolve this, rename the scope from UNSCOPED
  to something else. For more information, refer to
  TID 10059981
  (http://support.novell.com/cgi-bin/search/searcht
  id.cgi?/10059981.htm).

 2.5 Problem Loading NSS Volumes Created with NSS
  Administration Menus

  If you use the NSS Administration menus option to
  create and manage NSS volumes, make sure to add
  the load NSS command in your autoexec.ncf file.
  Place the load NSS command before the mount all
  command in the file.

3.0 Issues from Support Pack 7

 3.1 Grace Connections Changed

  The number of grace connections was changed from
  two to three.

 3.2 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.3 NSS Volume Fails to Mount After Device
  Deactivation and Reactivation

  On NetWare 5.1 Support Pack 7, the server fails
  to mount an NSS volume after the device with the
  NSS volume is deactivated and then reactivated.

  To resolve this problem, update the NSS Media
  Manager Provider:

   1. Load NWCONFIG.
   2. Select NSS Disk Options.
   3. Select Storage (Configure NSS Storage).
   4. Select Update Provider Information.
   5. Select MMPRV NSS Media Manager Provider.
      On successful update, the NWCONFIG console
      returns the following message:
   6. Scan of selected Provider was successful.
   7. Mount the NSS volume.

 3.4 Down Command Powers Off Server with ACPI Drivers

  If you are using the latest Novell-supplied PSM
  drivers 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 Macintosh Extended Characters Not Supported

  Macintosh Extended Characters are not supported
  with AFP. Using extended characters can cause
  corruption if the file is written to an NSS
  volume.

 3.6 Packet Receive Buffers Default Changed

  Beginning with Support Pack 6, the Minimum Packet
  Receive Buffers and the Maximum Packet Receive
  Buffers defaults were changed to 500 and 5,000,
  respectively.

 3.7 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.8 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 Management Portal under IP
  address Management.

 3.9 Timesync Changes

  Beginning with Support Pack 7, you can administer
  Timesync and view the Timesync health parameters
  from NetWare Management Portal. For more
  information, see TID 10080009
  (http://support.novell.com/cgi-bin/search/searcht
  id.cgi?/10080009.htm).

 3.10 Accepting Multiple Certificates with IE6 browser

  When accessing the NetWare Management Portal from
  a client running Internet Explorer version 6, you
  might have to accept multiple browser
  certificates. To resolve this, edit the server's
  autoexec.ncf after installing the Support Pack
  and change the line that loads portal.nlm to read
  as follows:

  load portal.nlm /NFP

  Either unload and then reload the Management
  Portal using the Unload button on the
  Configuration Page or reboot the server for the
  change to take effect. You will be prompted to
  log in to the NetWare 5.1 Management Portal
  before any Front Page information is displayed,
  including the items that were requiring a
  certificate to be accepted multiple times.

  /NFP stand for "No Front Page" and makes the
  NetWare 5.1 Management Portal login behave
  similarly to the NetWare 6 and NetWare 6.5
  versions of NetWare Management Portal.

 3.11 Resolving Port Conflicts

  NetWare Management Portal and Enterprise Web
  Server use the same default port number, 80, so
  there might be a port conflict when doing a
  NetWare 5.1 Support Pack upgrade. There is no
  port conflict when all components are installed
  on the NetWare 5.1 server, including NetWare
  Management Portal and Enterprise Web Server.
  However, if a server is upgraded and then
  Enterprise Web Server is installed, you might run
  into a conflict. To resolve this, use Remote
  Manager to change the default port number from 80
  to 81 and then restart the server.

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

 3.13 Error When Loading Timesync

  When loading Timesync on a server, you might
  receive the following error on the server
  console:

  TIMESYNC: Unrecognized parameter in configuration
  file.

  Ignore these errors; they do not affect Timesync
  functionality in any way.

 3.14 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, complete the following to resolve this.

  Turn 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

4.0 Issues from Support Pack 6

 4.1 FTP Server Issues

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

  4.1.2 Configuration File Update

     The SECURE_CONNECTIONS_ONLY parameter has
     been added to the configuration file
     etc\ftpserv.cfg. This parameter lets you
     specify only secure FTP connections.

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

  4.1.4 Unloading a Single Instance

     Unloading a single instance of FTP Server
     is now supported. To unload a single
     instance use the following command syntax:

     nwftpd -u
     [volname:[/dirname/...]]myconfig.cfg

  4.1.5 Modifying Parameters for FTP Server

     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.1.6 Data Transfer Issues for FTP Server

     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.2 Apache Web Server

  If your server has the Apache Web server
  installed, which is not included with NetWare 5.1
  or in this Support Pack, you might receive the
  following error after installing the Support
  Pack:

  [crit](10022)Unknown error: make_secure_socket:
  for port 443, WSAIoctl: (SO_SSL_SET_SERVER)
  <press a key to close this screen>

  To finish the Support Pack installation, press a
  key. If you have used ZENworks for Servers to
  install the Support Pack, you need to go to the
  server console or use Rconsole to press a key for
  the install to finish.

 4.3 NDPS Error When Attaching to Queues

  If you are receive an NDPSM-3.1-108 Error (-344)
  while attaching to queues associated with a
  printer, refer to TID 10081038
  (http://support.novell.com/cgi-bin/search/searcht
  id.cgi?/10081038.htm) for more information.

 4.4 iPrint Map Designer

  If the printer agent name contains a space, then
  the driver settings will not be saved. To resolve
  this, complete the following:

   1. Open sys:\login\ippdocs\tool.js in a text
      editor.
      Search for the following line of code:
   2. if(escapedURL != oldURL)
      and replace it with the following:
      if(escapedURL != EscapeUrl(oldURL))
   3. Save the file.

 4.5 Timesync Issues

  Beginning with NetWare 5.1 Support Pack 6, you
  can administer Timesync from NetWare Management
  Portal. For more information see TID 10080009
  (http://support.novell.com/cgi-bin/search/searcht
  id.cgi?/10080009.htm).

 4.6 JVM Issues

  4.6.1 ZENworks for Desktops

     ZENworks for Desktops version 3.0 requires
     the installation of Support Pack 1 or
     later for ZENworks 3, when using JVM
     1.3.1. The Support Pack is available from
     Novell Downloads Web site
     (http://download.novell.com).

  4.6.2 ZENworks for Servers

     Tiered Electronic Distribution (TED) uses
     security certificates to allow subscribers
     to verify that the distribution they are
     receiving is from a trusted source. This
     feature will not work in a mixed JVM
     1.1.7b and JVM 1.3.1 environment (where
     you have some TED components running on
     servers with JVM 1.1.7b and other TED
     components running on servers with JVM
     1.3.1) using ZENworks for Servers version
     2 and 3.0.2.

     If you choose to run TED in this
     environment, it will be necessary to turn
     off the use of the Security Certificate.
     See TID 10062395
     (http://support.novell.com/cgi-bin/search/
     searchtid.cgi?/10062395.htm) for more
     information.

  4.6.3 TED Unable to Generate Keys with ZENworks
     for Servers 3.0.2

     TED is unable to generate its ephemeral
     keys on a NetWare 5.1 and NetWare 6 server
     Support Pack 3 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?/2965417.htm).

  4.6.4 OnDemand

     If using OnDemand v1.5 with JVM 1.3.1,
     edit the file sys:\system\usageserver.ncf
     and change the following line

     java -ns -classpath $USAGECLASSPATH
     UsageServer

     to read

      java -ns -Xbootclasspath $USAGECLASSPATH
     UsageServer

  4.6.5 Novell Servlet Gateway and Web Search
     Server Administration

     The Novell Servlet Gateway and Web Search
     Server Administration are incompatible
     with JVM 1.22 or later.

 4.7 Timesync with Secondary 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 = <File Server Name
      of your time source>.
   3. Set Timesync Restart Flag = ON.

 4.8 Confirming Security Certificates When Accessing
  the NetWare Management Portal

  If you are using Internet Explorer 6 as the
  browser for the NetWare Management Portal, you
  might notice that you are asked to confirm
  several security certificates when you first log
  in to the Management Portal.

  To resolve this, point the browser directly to
  the secure port for Portal
  (https://<IP_address>:8009) instead of the
  unsecure port (http://<IP_address>:8008) or by
  using Netscape as the browser.

5.0 Issues from Earlier Support Packs

 5.1 Location of CLIB Changed

  The following server library files were moved
  from sys:\system to c:\nwserver:

  clib.nlm
  clibaux.nlm
  clibctx.nlm
  fpsm.nlm
  lib0.nlm
  libc.nlm
  nit.nlm
  nlmlib.nlm
  requestr.nlm
  threads.nlm

  Because the c:\nwserver directory is in the
  search path for loading server modules, this
  change should be transparent to all applications
  using the library modules. This is a permanent
  change of location starting with NetWare 5.1
  Support Pack 3.

  The advantages of having these files in the
  server's startup directory are that other modules
  that load before the sys: volume can use them and
  they can be easily replaced as needed, even if
  the sys: volume will not mount.

 5.2 Remove SET CLIENT FILE CACHING ENABLED=OFF from
  Autoexec.ncf

  If you have a SET CLIENT FILE CACHING ENABLED=OFF
  statement in your autoexec.ncf, you should remove
  it.

  This was originally needed to address a
  connection problem with the server and NT client
  where an NT connection could not be cleared. This
  issue has been resolved.

 5.3 Error When Loading Timesync

  When loading Timesync on a server, you might
  receive an error on the server console: TIMESYNC:
  Unrecognized parameter in configuration file.
  Ignore these errors; they do not affect Timesync
  functionality in any way.

 5.4 NetWare Web Manager Reports Incorrect TCP Port

  If the administration server is listening for
  inbound connections on a port higher than 33000,
  the NetWare Web Manager screen reports that the
  port is 4294937760. Any port higher than 33000
  will cause this to happen. Functionality is not
  affected.

 5.5 Daylight Savings SET Parameters

  The following SET parameters have been removed
  starting with NetWare 5.1 Support Pack 4 because
  they are obsolete and should not be used:

  SET Daylight Savings Time Status

  SET New Time With Daylight Savings Time Status
  ongoing

 5.6 Installing DirXML

  After installing DirXML on a server, reboot the
  server to complete the installation; otherwise,
  you might experience an abend.

 5.7 Novell IPP Server Update

  Novell IPP Server has been optimized to work with
  the HTTP Interface (httpstk.nlm). A Novonyx
  configuration is not supported.

 5.8 Using WebDav and WebPublishing

  WebDav and WebPublishing cannot be run
  simultaneously on a server.

 5.9 JVM Issues

  5.9.1 Sixteen-Color Video Not Supported

     JVM 1.1.7b supported video with 16 colors.
     JVM versions 1.2.2 and later do not
     support 16 colors and require support for
     at least 256 colors.

     Before installing a newer JVM, you should
     verify that you can set the video driver
     to Super VGA (256 colors). If you cannot,
     you need to install a new video board that
     supports at least 256 colors.

  5.9.2 New Accelerated Display Drivers

     JVM 1.3.1 has upgraded the GUI to use
     Accelerated-X Display server 6.0. This
     version does not support some older video
     cards.

     If you are using the accelerated drivers,
     you should set the video driver back to
     Super VGA either by using the GUI
     Environment tool or by running VESA_RSP at
     the server console. After installing JVM
     1.3.1, you can then go back and reset your
     video driver to an accelerated driver.

  5.9.3 Oracle and JVM

     Oracle version 8.1.5 will not install on a
     server that has JVM 1.2.2 or later
     installed. To work around this, install
     JVM 1.1.7b and then install Oracle. If you
     need JVM 1.2.2 or later, install it after
     installing Oracle.

     Oracle version 8.1.6 will install on a
     server that has JVM 1.2.2 installed;
     however, Oracle will not uninstall.

  5.9.4 Using OnDemand with JVM

     OnDemand 1.5 is supported using JVM 1.2.2.
     OnDemand 1.0 is not supported with JVM
     1.2.2 or later.

  5.9.5 Using GroupWise Monitor with JVM

     GroupWise Monitor requires JVM 1.1.7b or
     earlier and will not work with later
     versions of JVM.

  5.9.6 WebSphere 3.0.x and JVM

     WebSphere 3.0.x does not run with JVM
     1.2.2 or later. If WebSphere is installed
     on the server, installing the Support Pack
     will not upgrade the Java version, even if
     the upgrade is selected during the Support
     Pack install.

  5.9.7 WebSphere Update

     The Consolidated Support Pack no longer
     includes WebSphere. To download the latest
     version of WebSphere, go to Novell
     Download Web site
     (http://download.novell.com).

  5.9.8 WebSphere 3.5.x Does Not Run on JVM 1.3.1

     If you install JVM 1.3.x, you need to
     completely uninstall WebSphere. Failure to
     do so could result in an unstable system.
     For more information on removing
     WebSphere, see TID 10065899
     (http://support.novell.com/cgi-bin/search/
     searchtid.cgi?/10065899.htm).

 5.10 Custom XServer Backgrounds Reset

  After installing the Support Pack, the NetWare
  XServer image might be reset to the NetWare 5.1
  default graphic. To use your XServer image,
  complete the following steps:

   1. From the graphical user interface at the
      server console, click Novell > Settings >
      Backgrounds.
   2. Select the image you want to use.
   3. Click OK.

 5.11 SSL Certificate Error

  After installing the Support Pack, you might
  receive the following error: "SAS failed to
  initialize with KMO/key=SSL Certificate DNS!
  (-11)".

  To correct this error, enter the following
  commands at the server console in the order
  listed:

  nswebdn
  unload sas.nlm
  load sas.nlm
  nsweb

 5.12 Installing GroupWise 5.5 or the Enhancement Pack

  After installing the NetWare Support Pack and
  then installing GroupWise 5.5 or the GroupWise
  5.5 Enhancement Pack, the following error might
  appear:

  Install detected that you are installing the
  GroupWise agents to a NetWare 4 server. Before
  running the agents, you must update the server's
  CLIB files. For more information, see the readme
  file located on the root of the GroupWise CD. Do
  you want to continue Installation? Yes/No

  Select Yes and the install will proceed normally.

Solutions

 5.13 File Update for ManageWise 2.7

  If you are running ManageWise 2.7 and install the
  Support Pack, nxipx.nlm might break into the
  debugger. This is not an abend. To correct this
  issue, download mwnxpfix.exe from the Novell
  Support Connection
  (http://support.novell.com/cgi-bin/search/searcht
  id.cgi?/2958823.htm).

 5.14 Changing the Server Configuration

  In order to install quickly, the Support Pack
  installation detects the current server
  configuration and installs the appropriate files.
  If you change the server configuration, you need
  to reinstall the Support Pack for the new
  configuration.

  For example, if LDAP Services for NDS is
  installed on a NetWare 5.1 server before the
  Support Pack is installed, then the Support Pack
  installation automatically upgrades LDAP Services
  for NDS. If LDAP Services for NDS is installed
  after the Support Pack installation, you need to
  reinstall the Support Pack to bring LDAP Services
  for NDS up to the Support Pack level.

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

 5.16 BorderManager Issues

  5.16.1 Border Manager 3.6 Abend

     After installing the Support Pack, your
     server might abend in tcp.nlm any time a
     client to site VPN connection is
     initiated. To resolve this, install the
     BorderManager 3.6 Support Pack available
     from the Support Web site
     (http://support.novell.com).

  5.16.2 Border Manager Installation

     When installing BorderManager, the
     server's tcpip.nlm is replaced with a
     secure version of the file. This version
     of tcpip.nlm is not compatible with some
     of the files in this Support Pack. You
     must reinstall this Support Pack after
     installing BorderManager to get the
     correct version of the secure tcpip.nlm
     installed and to get the compatible files
     installed. Failure to do so will result in
     an error, such as: "File
     sys:\system\bsdsock.nlm cannot be opened."

  5.16.3 Installing BorderManager 3.6 after
     Installing the Support Pack

     Before installing BorderManager 3.6, you
     need to download additional files from the
     Novell Support Connection. For more
     information, see TID 2960217
     (http://support.novell.com/cgi-bin/search/
     searchtid.cgi?/2960217.htm).

 5.17 NDPS Issues

  5.17.1 NDPS Printer Drivers

     The NDPS workstation printer drivers are
     no longer included with the Support Pack.
     Updated drivers are available from the
     printer vendor's Web site.

  5.17.2 NDPS Printer Drivers Compressed

     The following applies if NetWare 5.1
     Support Pack 3 was not installed prior to
     this Support Pack.

     After installing this Support Pack and
     rebooting the server, the NDPS printer
     drivers are compressed on the server the
     first time the Resource Management Service
     (RMS) is loaded. If RMS is enabled by
     default, the compression begins when
     broker.nlm is loaded for the first time.
     This process can take over 20 minutes.
     During this process, neither broker.nlm
     nor zlib.nlm can be unloaded. The server
     cannot be restarted until this process is
     complete. This process happens only once
     on servers that are running the NDPS
     broker.

     The benefits of this are that work is
     transitioned from the server and
     distributed to the clients, traffic is
     greatly reduced, and printer driver
     distribution is more reliable.

 5.18 NetWare Storage Management Services (SMS) Issues

  5.18.1 Windows TSA and NWBACK32 Support

     Novell has discontinued support for
     NWBACK32 and the Target Service Agent
     (TSA) components for Windows.

     In case the of a Novell Client for Windows
     upgrade, NetWare SMS components existing
     on the system from a previous installation
     will not be deleted and the Target Service
     will be 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.18.2 Supervisor Right for Open Files Backup

     The Supervisor right is required to back
     up open files.

  5.18.3 Migrated Files Backup

     Backup of migrated files is not supported
     on Novell Storage Services (NSS) file
     system.

  5.18.4 Canwpa.cdm for ARCserveIT 6.6

     When using ARCserveIT 6.6 with this
     Support Pack, we strongly recommend that
     you use canwpa.cdm instead of nwaspi.cdm.
     See the ARCserve Service Pack Readme for
     details on how to use canwpa.cdm.

  5.18.5 Storage Management Services Path Length
     Support

     Backup and restore of directories and
     files with path lengths greater than 300
     characters are not supported on
     traditional file system.

  5.18.6 ArcServe Patches

     Computer Associates provides the fixes for
     ARCserve. You should apply the appropriate
     patches to avoid abending the server. To
     download patches, go to Computer
     Associates Support Web site
     (http://www3.ca.com/support).

  5.18.7 Extended Attribute Backups

     Backup of files with Extended Attributes
     fails on NSS 2.x volumes.

  5.18.8 Trustee Backups

     Backup of files with more than 10,000
     trustees fails on NSS 2.x volumes.

  5.18.9 SMDR Discovery using eDirectory

     SMDR no longer supports eDirectory as a
     mechanism for discovery. SMDR uses SLP or
     SAP for discovery and in addition can use
     hosts/DNS for name resolution. SMDR can be
     configured to use these services through a
     policy ladder mechanism that can be
     defined using the load time parameter SMDR
     NEW.

 5.19 Creating Files or Directories with Double-byte
  Characters Using 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.

 5.20 ADSync with ConsoleOne Issue

  After installing ADSync while using ConsoleOne,
  you might not be able to browse NDS using the
  tree. To resolve this, ensure that the
  workstation running ConsoleOne has a primary
  Novell Client connection to a server running NDS
  8.5.

 5.21 NetWare Management Portal Issues

  5.21.1 Unloading and Reloading Portal.nlm and
     Httpstk.nlm

     To unload and reload the portal.nlm and
     httpstk.nlm modules used for NetWare
     Management Portal, use the Restart button
     on the NetWare Management Portal
     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 run into issues with module
     dependencies (like Timesync, LibC,
     Tcpstats, Nwusage, 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.21.2 New NetWare Management Portal Screen

     Beginning with Support Pack 4, a dynamic
     console screen applet to NetWare
     Management Portal was included under the
     Screens link. The new screen, called
     Screens, launches a window that is
     equivalent to a remote console screen.
     Screens lets you load NLM programs and use
     Monitor and other programs just as you
     would at the physical server console.
     Screens is available only to the Admin or
     Admin-equivalent users logged in to the
     NetWare Management Portal.

     The buttons along the top of the screen
     applet window allow you to do the
     following:

     - Switch between screens on the console
     - Display a list of screens (like
    Ctrl+Esc)
     - Use the Emergency Console to cancel a
    volume mount
     - Unload a module when the main console
    screen is hung
     - Run a new command line process (like
    Ctrl+Alt+Esc)

     Entering BYE at the console prompt can
     dismiss any auxiliary command consoles.

     There are some known limitations in the
     handling of special characters (extended
     ASCII and double-byte characters) in the
     console screen applet, and the response
     time might vary with the Web browser you
     are using. Remote access to the server
     console does not include the GUI screens
     on the server.

  5.21.3 Connectivity to NetWare Management Portal
     at Multiple IP Addresses

     By default, connectivity to the NetWare
     Management Portal is available only at the
     first IP address bound to the server's LAN
     card as viewed in autoexec.ncf or INETCFG
     > View Configuration > Protocol Bind
     Commands. For each additional IP address
     for which Portal access is desired, the
     following server command must be issued.
     We recommend adding this command to the
     autoexec.ncf file for each IP address:

     HTTPBIND XXX.XXX.XXX.XXX /keyfile:"<SSL
     Certificate Name>"

     Replace XXX.XXX.XXX.XXX with the IP
     address and replace <SSL Server
     Certificate Name> with the name of a
     certificate created for the given IP
     address.

  5.21.4 NetWare Management Portal Settings

     After applying the Support Pack, the
     NetWare Management Portal's main page
     might appear without hyperlinks in the
     left frame and the main portion of the
     page might appear empty for users not
     logged in to the Management Portal. This
     is a configurable setting from within the
     Management Portal.

     To have data displayed for users not
     logged in to the Management Portal,
     complete the following steps:

      1. Log in to the NetWare Management
     Portal from the main page.
      2. Click the NetWare Management Portal
     link in the upper-right corner of the
     page.
      3. Change the setting Display Only Header
     on Front Page If Not Logged In to
     "Yes."

  5.21.5 Browser Access to NetWare Management
     Portal

     If you are using Netscape 6 from a Windows
     client, or Internet Explorer or Netscape
     from a Macintosh client, you will not be
     able to log in to the NetWare Management
     Portal using the Login button at the top
     of the left-hand column on the front page.

     To log in to NetWare Management Portal,
     click the server name next to the traffic
     light to display the Login dialog box.

     For more information, see TID 10061585
     (http://support.novell.com/cgi-bin/search/
     searchtid.cgi?/10061585.htm).

 5.22 Remote Console and RCONJ Issues

  5.22.1 Using RCONJ to View Console Monitor Screen

     When using RCONJ to view the NetWare 5
     Console Monitor screen, some screens will
     not refresh unless the screen is the
     current active screen. Other screens that
     have the same type of monitoring (like
     NetWare Web Manager) update the screen in
     RCONJ even if the screen is not the
     current active screen on the system
     console.

     To resolve this, click the Activate
     button, which will activate and update the
     current screen.

  5.22.2 Using RCONJ and Rconsole over IPX

     To use RCONJ or RCONSOLE over IPX after
     installing the Support Pack, you must load
     spxs.nlm before you load rconag6.nlm in
     autoexec.ncf. If spxs.nlm is not loaded,
     rconag6.nlm might fail to load and
     generate the following error: "NSPX did
     not initialize."

  5.22.3 RCONJ Will Not Run

     Rconj.exe will not run unless the Windows
     workstation has a drive mapped to the sys:
     volume.

  5.22.4 Remote Console and NDS Manager

     In this Support Pack, you cannot run
     Remote Console from within NDS Manager.
     Instead, you must run it from a mapped
     drive to sys:\public.

  5.22.5 RCONJ and ConsoleOne

     In this Support Pack, you cannot run RCONJ
     from within ConsoleOne 1.2d when using JVM
     1.2.2. Instead, you must run it from the
     network at
     sys:\public\mgmt\consoleone\1.2\rconj.exe.

     This is an issue only when using JVM
     1.2.2. RCONJ will run on the server when
     JVM 1.1.7b or 1.3.1 is installed.

 5.23 Driver Issues

  The latest certified Storage drivers are
  available at Certified Storage Drivers Web site
  (http://developer.novell.com/devres/storage/drive
  rs/index.html).

  The latest certified LAN drivers are available at
  Certified LAN Drivers Web site
  (http://developer.novell.com/devres/lan/drivers/i
  ndex.html).

  5.23.1 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,
     Novell has found that many new routers and
     clients will 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 will 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 load line
     option.

  5.23.2 Using Cpqscsi.ham

     After updating to Compaq's latest Support
     Software for Novell products (NSSD) using
     cpqscsi.ham, the NDS database might not
     open. To resolve this, you need to
     manually load NDS by adding a LOAD DS
     statement to the server's autoexec.ncf.

  5.23.3 IDE CD Drives

     If your server includes an IDE CD drive
     that is configured as a Master device but
     it does not appear in the list of devices
     in NetWare, reconfigure the device to
     present itself as a Slave device.

  5.23.4 IDE Drives

     Many IDE drives do not adhere to the
     industry standard for IDE. If you
     experience issues with your IDE drive
     after installing the Support Pack, you
     might need to use the IDE driver that you
     were using before installing the Support
     Pack.

     The IDE drivers are automatically backed
     up to c:\nwserver\backsp8\storage. To use
     the earlier driver, copy the file from the
     backup directory to c:\nwserver.

  5.23.5 New Option for Named.nlm

     A new option has been added to named.nlm
     that purges the DNS cache of all records.
     To use this, enter LOAD NAMED.NLM -PA at
     the server console.

  5.23.6 Server Abend in NCMCON

     If the server abends in NCMCON while
     installing NSSD from Compaq in all
     languages except English and Japanese, you
     should copy the English ncmcon.msg from
     sys:\system\nls\4 to the language
     directory. For example, if you are using
     Spanish, copy the file to
     sys:\system\nls\14.

  5.23.7 Change in Adapter Multipath Support

     Beginning with NetWare 5.1 Support Pack 4,
     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?/10070244.htm).

 5.24 WebSphere Issues

  5.24.1 Launching WebSphere

     If you launch WebSphere from the Java GUI
     and WebSphere does not run, you need to
     edit autoexec.ncf and remove the pound
     sign (#) from the beginning of the Start
     WebSphere command. After rebooting the
     server, you will be able to launch
     WebSphere from the GUI.

  5.24.2 BorderManager and WebSphere

     If you use a BorderManager proxy
     accelerator in front of your Web site and
     you have dynamic content (either servlets
     or JSP pages), note that the BorderManager
     accelerator name needs to match with an
     entry in the Configured Hosts for
     WebSphere.

     If the name and entry do not match, you
     might get errors where servlets aren't
     found and JSP pages aren't processed. If
     you get an error, either change the
     accelerator name to match or add a
     matching hostname to WebSphere.

 5.25 WebSearch Changes

  5.25.1 Indexes No Longer Listed on Default Search
     Page

     After upgrading from previous versions of
     Web Search, the list of collections that
     appear on the default search page might
     disappear. This is because newer versions
     of Web Search differentiate between the
     collections specified by a particular
     query versus those actually available at
     the server.

     To make it so that all available indexes
     display on the search page, either use the
     templates that ship with the newer Web
     Search (located in the
     \nsearch\templates\samples directory) or
     make the following changes to the
     searchtemplate.html file that you are
     currently using as your search page:

     - Change $$BeginCollectionsLoop to
    $$BeginServerCollectionsLoop
     - Change $$EndCollectionsLoop to
    $$EndServerCollectionsLoop

  5.25.2 New Sample Web Search Templates

     NetWare Web Search includes new sample
     search results templates. You should
     always use the new templates as a basis
     for your own templates.

     If you install Web Search over a previous
     installation, your existing templates are
     not overwritten. The new templates are
     copied into the
     sys:\nsearch\templates\samples directory.

     To test the sample templates from a Web
     client machine, include the Theme query
     parameter with the value Samples:

     &theme=Samples&other_query_parameters

     You can also temporarily change the
     templates directory to the samples
     directory in the Search Properties form in
     the NetWare Web Search Manager.

     For more information, refer to the Novell
     Cool Solutions article
     (http://www.novell.com/coolsolutions/netwa
     re/features/a_websearch_nw.html).

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

 Server.exe includes the following NLM programs:

 connmgr.nlm
             
 cdbe.nlm
             
 cpucheck.nlm
             
 diag500.nlm
             
 filesys.nlm
             
 hwdetect.nlm
             
 lfs.nlm
             
 lsl.nlm
             
 mm.nlm
             
 nbi.nlm
             
 ncp.nlm
             
 neb.nlm
             
 nwkcfg.nlm
             
 nwpa.nlm
             
 nwpaload.nlm
             
 pmlodr.nlm
             
 pver500.nlm
             
 queue.nlm
             
 server.nlm
             
 sguid.nlm
             
 showlogo.nlm
             
 xldr.nlm
             

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

 - Open Enterprise Server
 - NetWare 6.5 Support Pack 3
 - NetWare 5.1 Support Pack 8
 - NFS 3.0 Support Pack 7
 - NFAP 1.0 Support Pack 5
 - GroupWise 6.5 Support Pack 4
 - GroupWise Messenger 1.0 Support Pack 4
 - BorderManager 3.8 Support Pack 3
 - Novell Client 4.9 for Windows NT/2000/XP

8.0 Third-Party Product 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.

 8.1 Dell Server Management Software (AppCD)

  Prior to installing the Support Pack, temporarily
  disable Dell OpenManage Software by editing the
  autoexec.ncf file and commenting out---with a
  preceding semicolon (;) or pound sign (#)---the
  following lines:

  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.

 8.2 HP Hot-Plug Stops Working

  When performing an upgrade to NetWare 5.1 Support
  Pack 7or 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.

 8.3 Pervasive Updates

  Updates for Pervasive SQL are not included in
  this Support Pack.To obtain updates, go to
  Pervasive's Web site
  (http://www.pervasive.com/support) and look for
  Pervasive SQL 2000i.

 8.4 NetWare for SAA and Oracle Products Not Tested

  This Support Pack has not been tested with
  NetWare for SAA and Oracle database products.

 8.5 Symantec Norton AntiVirus Enterprise 7.5

  After installing the Support Pack, you might see
  the following abend: Page Fault Running Process:
  NAVCode executing in module v536936454.0l at
  offset +CCA806EDh.

  To resolve this, download an update from
  Symantec. This abend is fixed in version 7.6 of
  the Norton Antivirus.

 8.6 Tobit FaxWare Running on Novell for Small
  Business and NetWare for Growing Business

  Tobit FaxWare might not load after the Support
  Pack has been applied to Novell for Small
  Business and NetWare for Growing Business. To
  correct this problem, replace the david.nlm file
  with the one in the \tools\tobit directory.

9.0 Removing the Support Pack from the Server

 9.1 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\backsp8 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 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\backsp8 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.

 9.2 Downgrading to a Previous NDS Version

  After DS.NLM version 7.49 or 8.72 or later is
  loaded on the server, previous versions of NDS
  (7.48 or earlier) will no longer load. This is
  caused by slight changes to the semantics of some
  NDS records. Downgrading from NDS version 7.49 or
  8.72 to a previous version of NDS is not
  recommended; however, it is still possible.

  If you selected the Backup option during the
  Support Pack install, you can uninstall the
  Support Pack to restore the earlier version of
  Directory Services. For more information, see
  section 14.1, "Uninstalling the Support Pack."

  To downgrade NDS manually, complete the
  following:

   1. Copy the previous version of ds.nlm to the
      server's sys:\system directory.
   2. With ds.nlm still loaded, issue the
      appropriate console command.
      For NDS version 7.49:
      SET DSTRACE=DOWNGRADEDIBTOVERSION9
      For NDS version 8.72:
      SET DSTRACE=DOWNGRADEDIBTOFUSION
      The local database closes and downgrades
      itself. It will not reopen.
   3. After the database has closed and the console
      prompt returns, bring down the server.
   4. Replace the dsloader.nlm file in c:\nwserver
      with the previous version.
   5. Restart the server.

  The next time you load a newer NDS version, the
  database automatically reupgrades.

 9.3 Uninstall the Support Pack When Running NDS8

  If you remove the Support Pack from a server that
  is running NDS 8.xx, the server might abend when
  unloading DSRepair. To prevent this, copy
  dsrepair.nlm in this Support Pack from
  \products\nds8\system to the server's sys:\system
  directory after uninstalling the Support Pack.

10.0 Updated TCP/IP Documentation

 For information on the updated TCP/IP included with
 the Support Pack, see the tcpip.txt file at the root
 of the Support Pack.

11.0 Upgrading to NetWare 6.x

 If you are upgrading from NetWare 5.1 server with the
 Support Pack installed to NetWare 6.x, you might be
 prompted to overwrite newer files. You should always
 select the option Always Overwrite Newer Files to
 ensure the correct NetWare 6.x files are installed.

12.0 Files in the \TOOLS Directory

 For a list of files in the \tools directory, see the
 tools.txt file at the root of the Support Pack.

13.0 Changes Since Last Support Pack

 For a list of the changes made since the last Support
 Pack, see TID 10094148
  (http://support.novell.com/cgi-bin/search/searchtid.c
 gi?/10094148.htm).

14.0 Additional Documentation

 In addition to this Readme file, the following sources
 provide additional information about the Support Pack:

 - For installation instructions, see nw51sp8.txt
    located at the root of the Support Pack.
 - For information on using the enhancements to TCP/IP
    included with this Support Pack, see tcpip.txt at
    the root of the Support Pack.
 - For more information on the latest Support Pack
    issues, see TID 10094148
     (http://support.novell.com/cgi-bin/search/searchti
    d.cgi?/10094148.htm).
 - For information about files in \tools, see
    tools.txt located at the root of the Support Pack.
 - For more information about showing printer status
    information in the NDPS Manager Health, see TID
    10061751
    (http://support.novell.com/cgi-bin/search/searchtid
    .cgi?/10061751.htm).
 - TID information is available on the Novell Support
    Web site (http://support.novell.com).
 - For updated documentation, see the NetWare 5.1
    online documentation
    (http://www.novell.com/documentation/lg/nw51/index.
    html).

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

16.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 2005 Novell, Inc. All rights reserved. No
 part of this publication may be reproduced,
 photocopied, stored on a retrieval system, or
 transmitted without the express written consent of the
 publisher.

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

 Novell, NetWare, BorderManager, ConsoleOne, DirXML,
 GroupWise, ManageWise, NDPS, Novell Directory Services
 and NDS, and ZENworks are registered trademarks of
 Novell, Inc. in the United States and other countries.

 eDirectory, Internet Packet Exchange and IPX, NetWare
 Loadable Module and NLM, NetWare Storage Services and
 NetWare SMS, Novell Client, Novell Cluster Services,
 Novell Distributed Print Services, Novell Storage
 Services are trademarks of Novell, Inc.

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

File Contents

Self-Extracting File Name:  nw51sp8ei.iso

Files Included       Size   Date         Time    Version   Checksum

\
 NW51SP8EI.ISO  693268480   28Feb2005    11:14AM

document

Document Title: NW51SP8 English-Italiano Overlay CD (128bit)
Document ID: 2970950
Creation Date: 08Mar2005
Modified Date: 08Mar2005
Revision: 1
Novell Product Class:NetWare

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.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.