****************************************************************************
*                                                                          *
*                    (C) Copyright 1993 Novell, Inc.                       *
*                         All Rights Reserved.                             *
*                                                                          *
*                                                                          *
*               README.TXT for NetWare NFS Gateway 1.1                     *
*                                                                          *
*                         March 12th, 1993                                 *
****************************************************************************

This file provides information that became available after the NetWare NFS
Gateway Supervisor's Guide was printed. This file contains information on the 
following topics:

  >> Installation Prerequisites
  >> Adding an Additional Time Zone
  >> Using Gateway Management Groups
  >> Renaming/Deleting the Local Host Name
  >> Installing NetWare FLeX/IP on Top of the Gateway
  >> Running the Gateway with NetWare Accounting
  >> Dismounting NetWare Volumes
  >> Data Transfer Size
  >> Using the Packet Burst NLM (PBURST.NLM)
  >> Getting Extended File Attribute Information
  >> Running a High Volume of Applications or Clients
  >> Lock Request Timeouts
  >> Stopping the Lock Manager


Installation Prerequisites
==========================

A. The installation process will prompt for the host name if none is already
   defined.  In order to correctly use locking with the NFS Gateway, the
   host name for the NetWare server must correspond to the host name by
   which this machine is known to the NFS servers.  The default host name is
   the name of the NetWare server itself, however be sure to type in the same
   host name that is used in the host database of the NFS servers.

B. The NetWare NFS Gateway can coexist with NetWare NFS V1.2B.  If you 
   are using the Gateway on the same NetWare server that contains an earlier
   version of NetWare NFS, you must upgrade to NetWare NFS V1.2B.

   Please contact the following numbers regarding this upgrade:

   North America:  (800) 926-6075
   International:  (716) 871-6527
   WorldWide FAX:  (716) 873-0906

C. If NetWare FLeX/IP, NetWare NFS V1.2B, or NetWare MultiProtocol Router
   (MPR) is installed on the NetWare server, you need to complete the
   following steps on the NetWare server console before you install the NFS
   Gateway:

   If NetWare FLeX/IP is installed:

   1. Type
 
   	FLXSTOP	<Enter>

      This command stops all NetWare FLeX/IP services.

   2. Type

   	UNLOAD PKERNEL <Enter>

      This command unloads the existing Product Kernel.  The Gateway
      installation process installs a new version of the Product Kernel
      that is shared by NetWare FLeX/IP and the Gateway.

   If NetWare NFS V1.2B is installed:

   1. Type

   	NFSSTOP	<Enter>

      This command stops all NFS services.

   2. Type

   	UNLOAD PKERNEL <Enter>

      This command unloads the existing Product Kernel.  The Gateway
      installation process installs a new version of the Product Kernel
      that is shared by NetWare NFS V1.2B and the Gateway.

   If NetWare MultiProtocol Router (MPR) is installed:

   1. Type

   	UNLOAD XCONSOLE <Enter>
	UNLOAD RTRFTP	<Enter>
	UNLOAD INETD	<Enter>

      These commands unload all NLMs that depend on PKERNEL.NLM.

   2. Type

   	UNLOAD PKERNEL <Enter>

      This command unloads the existing Product Kernel.  The Gateway
      installation process installs a new version of the Product Kernel
      that is shared by the MultiProtocol Router and the Gateway.

ADDING AN ADDITIONAL TIME ZONE
===============================

   If the list of time zones does NOT include your specific time zone,
   you can add your time zone to the database file as described on page 12-5
   of the NetWare NFS Gateway Supervisor's Guide. If the SYS:ETC\TIMEZN file
   is read-only, you must change the permissions to read-write. Also note
   that time zones in the Western Hemisphere have positive (+) offsets, while
   those in the Eastern Hemisphere have negative (-) offsets.

USING GATEWAY MANAGEMENT GROUPS
===============================

   If you want to delegate Gateway management tasks to non-Supervisor
   users as described on page 4-2 in the NetWare NFS Gateway Supervisor's
   Guide, you must make sure that the group EVERYONE has at least read (R)
   and filescan (F) rights to the SYS:ETC directory.  You can use either
   the FILER or GRANT DOS utility to perform this operation.

RENAMING/DELETING THE LOCAL HOST NAME
=====================================

   The local host name is the name assigned to the NFS Gateway server.  This
   name is displayed in the "Host IP Name" field of the Server Profile screen.
   This name is used by the NIS and DNS name services and should not be
   modified.  Therefore, you should not rename or delete the local host entry
   using the Host Management screen in NFSCON.

INSTALLING NetWare FLeX/IP ON TOP OF THE GATEWAY
================================================

   The version of PATCHMAN.NLM provided with NetWare FLeX/IP is not compatible
   with the Gateway. If you install the Gateway on top of NetWare FLeX/IP, the
   new version of PATCHMAN.NLM automatically overrides the old version.
   However, if you install NetWare FLeX/IP on top of the Gateway, the old
   version overrides the new version. To solve the problem, you need to copy
   the \SYSTEM\PATCHMAN.NLM file from the NFSGW1 installation diskette and
   then place it on the server in the SYS:SYSTEM directory.  You might need to
   change the rights of the file on the server to read-write before you copy
   it.

RUNNING THE GATEWAY WITH NetWare ACCOUNTING
===========================================

   If your Gateway server has NetWare accounting enabled, the users
   you create using NFSCON will not be able to log into the server until you
   enable accounting for these users.  To enable accounting, complete the
   following steps from a DOS workstation:

   1. Log in to the Gateway server as SUPERVISOR.

   2. Enter SYSCON.

   3. Select "User Information".

   4. Select the user you created using NFSCON.

   5. Select "Account Balance," and then press the <ESC> key to exit the
      screen.

   6. Repeat steps 4 and 5 for each user you created using NFSCON.

   The users can now log into the server.

DISMOUNTING NetWare VOLUMES
===========================

   If you dismount a NetWare volume that is being used for the shadow files
   for one or more currently mounted NFS Gateway volumes, be sure to dismount
   those Gateway volume(s) as well.

DATA TRANSFER SIZE
==================

   The NFS Gateway uses the data transfer size negotiated with the target NFS
   server (through the NFS procedure NFS_STATFS). This procedure is used to
   make data read/write calls to the NFS server. In some conditions you might
   want to specify this value. For example, some LAN cards do not work with
   the suggested transfer size (usually 8K). You can change the transfer size
   by modifying the NFS_XFER_SIZE parameter located in SYS:ETC\NWPARAMS file.

MAPPING USERS WHEN YOU ARE RUNNING NetWare NFS V1.2B
====================================================

   In order for a NetWare user to log in and access a volume mounted by the
   Gateway, the user must not only have a NetWare account, but must also have
   a UNIX user account mapped to the NetWare user account.  Therefore, a user
   account must have names on both the left side (NetWare user) and the right
   side (UNIX user) of the User list.

   If you install the Gateway on top of NetWare NFS V1.2B, user accounts
   will exist only as NetWare users even if they have a NetWare-to-UNIX
   mapping in the SYS:ETC\NFSUSERS file.  These users will not be able to
   gain	access to files on a Gateway volume until they are mapped to a UNIX
   account using the NFSCON utility. These user accounts are mapped
   automatically if you follow the first time configuration procedures in
   Chapter 6 of the NetWare NFS Gateway Supervisor's Guide. If you want to
   create the UNIX user accounts and then map them manually, see Chapter 8.

USING THE PACKET BURST NLM (PBURST.NLM)
=======================================

   If you want to use the Packet Burst NLM (PBURST.NLM), you should load it
   before you start the NFS Gateway.  The PBURST.NLM, which is available
   through NetWire in DOSUP6.ZIP, provides the packet burst feature and
   security patch.  The security feature provided in the PBURST.NLM is
   supported by the Gateway, but the packet burst feature is not.

GETTING EXTENDED FILE ATTRIBUTE INFORMATION
===========================================

   This release of the NFS Gateway does not support extended file attributes.
   For example, if you try to use FILER to get file information about files
   that are accessed through the Gateway, you will receive the following
   warning message:
   
   "System was unable to get the extended attributes"

RUNNING A HIGH VOLUME OF APPLICATIONS OR CLIENTS
================================================

   If you are running a high volume of applications and/or clients, you might
   experience locking errors. To solve this problem, you can increase the
   "LOCK DELAY" parameter value in the NET.CFG file as the volume increases.
   We recommend that you start by setting LOCK DELAY=20.  If the problem
   persists, you can increase this value up to LOCK DELAY=60.  You must
   reboot your client after changing the value.

LOCK REQUEST TIMEOUTS
=====================

   In order to correctly use locking with the NFS Gateway, the host name for
   the NetWare server must correspond to the host name by which this machine
   is known to the NFS servers.

   If you receive the following error message:

   LOCKD-Warning: Lock Timeout
  
   then you might need to change the Gateway server's name in the NFS
   server's /etc/hosts file to match the name specified on the Gateway server
   (which is displayed in the Server Profile screen in NFSCON).

STOPPING THE LOCK MANAGER
=========================
   
   To ensure that the NetWare locks are consistent with the remote NFS
   locks, stop the lock manager, and also stop the NFS Gateway.
