                      NetWare/IP Release Document
                              README.TXT



Copyright (c) 1993 Novell, Inc.   All Rights Reserved.



THIS WORK IS SUBJECT TO U.S. AND INTERNATIONAL COPYRIGHT LAWS AND
TREATIES. NO PART OF THIS WORK MAY BE USED, PRACTICED, PERFORMED,
COPIED, DISTRIBUTED, REVISED, MODIFIED, TRANSLATED, ABRIDGED,
CONDENSED, EXPANDED, COLLECTED, COMPILED, LINKED, RECAST,
TRANSFORMED, OR ADAPTED WITHOUT THE PRIOR WRITTEN CONSENT OF
NOVELL, INC. ANY USE OR EXPLOITATION OF THIS WORK WITHOUT
AUTHORIZATION COULD SUBJECT THE PERPETRATOR TO CRIMINAL AND CIVIL
LIABILITY.

                            DISCLAIMER
 
Novell, Inc. makes no representations or warranties with respect to this
software, and specifically disclaims any express or implied warranties
of merchantability, title, or fitness for a particular purpose.

Distribution of this software is forbidden without the express written
consent of Novell, Inc. 

Novell will not be responsible for any data loss that might result from
implementing this software. Novell strongly recommends a backup be made
before installing this software. Technical support for this software is
provided at the discretion of Novell.

***************************************************************************
                                   CAUTION
*************************************************************************** 
ALWAYS backup your system before implementing any program/utility revision
involving the low-level functions of NetWare including re-linking of
operating system .OBJ files, Bindery utilities, and drive and volume 
operation.

This document includes the following sections:

     PURPOSE OF THIS README FILE
     INSTALLING THE NetWare NFS GATEWAY OVER NetWare/IP
     INSTALLING THE NFS GATEWAY OVER NetWare/IP
     INSTALLING NetWare/IP OVER	THE NFS GATEWAY
     RUNNING RFCNBIOS ON THE CLIENT WORKSTATION
     DOS REQUESTOR (VLM) UPGRADE INSTRUCTION
     INSTALLING LAN WORKPLACE OVER NetWare/IP
     INSTALLING NetWare/IP OVER	LAN WORKPLACE
     DELETING IP ADDRESSES FROM THE REPLICA DATABASE INFORMATION SCREEN
     CORRECTIONS TO NetWare/IP ADMINISTRATION GUIDE
     LIMITATIONS

===========================
PURPOSE OF THIS README FILE
===========================
This README file provides information about NetWare/IP that is not included
in the NetWare/IP Administrator's Guide.

==================================================
INSTALLING THE NetWare NFS GATEWAY OVER NetWare/IP
==================================================

Preparing for Installation
===========================
Before you install the NFS Gateway over NetWare/IP, you need to stop
the services that are running by typing the following command at
the console prompt:

     UNISTOP <ENTER>

Installing the Software
========================
The NFS Gateway software requires both NIS and DNS to function

The NFS Gateway software requires that the NIS and DNS servers
both be local (running on the NetWare server), or remote (running
on some other host).

If you plan to install the NFS Gateway after you install NetWare/IP
and you are using a remote DNS server for NetWare/IP, you have the
following choices:

>>Use a remote NIS server

  If you already using a remote DNS server and you have access to a
  remote NIS server, enter the remote NIS server's domain name and
  IP address when the NFS Gateway installation program asks you to
  select nameservers.

>>If you do not have access to a remote NIS server

  When the NFS Gateway installation program asks you to select
  nameservers, it will display the domain name and IP address
  of the remote DNS server that you entered when you installed
  the NetWare/IP, and it will display the domain name and
  IP address of the local NIS server that it proposes to set
  up for the NFS Gateway.

  Because the NFS Gateway requires that both the DNS and NIS servers
  be either local or remote, you must set the information in the DNS
  fields to use the local server.  (By default, the local domain is
  "servername.com" and the IP address is the IP address of the
  local server.  For example, if your NetWare server's name is
  acme, the default domain name is acme.com.)
  
  Use the following procedure to use remote DNS for NetWare/IP and local
  NIS for the Gateway:
  
  1. Enter the local DNS domain (localservername.com) and IP address when
     prompted to "select nameservers" during the NFS Gateway installation.

  2. After installation, run the UNICON utility.

  3. Select "Configure Server Profile" from the Main Menu.

  4. Go to the "Primary Server" (DNS) field.

  5. Enter the IP address of the remote DNS server used by NetWare/IP.
     Enter the IP address of the local DNS Server in the "Secondary
     Server" (DNS) field.

  6. Press the <Esc> key to exit the screen.

  You can now run NetWare/IP and the NFS Gateway simultaneously, with
  DNS service from the remote server and NIS service from the local
  server.

===========================================
INSTALLING NetWare/IP OVER THE NFS GATEWAY
===========================================

Before you install the NetWare/IP over NFS Gateway, you need to stop
all services that are running by typing the following command at
the console prompt:

     NFSSTOP <Enter>

===========================================
RUNNING RFCNBIOS ON THE CLIENT WORKSTATION
============================================

If you need NetBIOS capabilities over TCP/IP, you can substitute the
RFCNBIOS program for the IPX-based NetBIOS program.  The RFCNBIOS
program is provided with the NetWare/IP software. The RFCNBIOS
software implements the NetBIOS B-node protocols as defined in
RFCs 1001 and 1002.

Before you run RFCNBIOS on your client workstation, you must add an
RFCNBIOS protocol section to the NET.CFG file.

WARNING: The RFCNBIOS entry must be the last section in the NET.CFG file
         for RFCNBIOS to function properly.

Under the RFCNBIOS section of the NET.CFG file, you need to add a line 
for each host that the client will access using RFCNBIOS. The line contains
the hostname and IP address as shown in the following example:

     Protocol RFCNBIOS
            nbiosserver_name1  123.45.6.78
            nbiosserver_name2  123.45.6.79

Note: You can list a maximum of 16 RFCNBIOS hosts.
         
The NetBIOS software is customized in the Protocol TCP/IP section of the
NET.CFG file. The following paragraphs describe the five NetBIOS settings
and provide the valid and default values of these settings.

     nb_adapter     This setting specifies the NetBIOS adapter number.
                    This value must be either 0 or 1 (the first is 0, the
                    second is 1). The default is 0.

     nb_brdcast     The setting specifies the format of IP broadcasts used
                    when RFCNBIOS.EXE sends broadcast messages.

     nb_commands    This setting specifies the maximum number of asynchronous
                    NetBIOS commands. Each pending NetBIOS command requires
                    32 bytes of memory. The default value is 8 in a range of
                    0 to 80.

     nb_domain      This setting specifies the name of the logical domain
                    for this NetBIOS station. All stations in the same
                    logical domain must use the same value for the nb_domain
                    setting. The value is a string up to 80 characters. The
                    default value is the null string (no value).

     nb_sessions    This setting specifies the maximum number of concurrent
                    NetBIOS sessions. Each session requires 114 bytes of
                    memory. The tcp_sockets parameter must be at least
                    nb_sessions + 1. The default is 4 in a range of 0 to 64.

========================================
DOS REQUESTOR (VLM) UPGRADE INSTRUCTION
========================================

When installing a newer version of VLM over NetWare/IP client, please make sure
you back up copies of your startnet.bat and net.cfg files.  By default, 
these files are placed in the C:\NWCLIENT directory.  After installing the
new VLMs, you can restore the startnet.bat and net.cfg files by using
the backed up copies you made.  In the event that you did not make back
up copies of these two files, you can restore them by using 
startnet.bnw and net.bnw which are saved by the new VLM installation.

===================================================================
INSTALLING LAN WORKPLACE OVER NetWare/IP
===================================================================

If you install the LAN WorkPlace software after you have installed the
NetWare/IP client software, be sure to complete the following tasks:

1.  Check the AUTOEXEC.BAT file to ensure that the line which reads:

	STARTNET.BAT

    is not commented out.

2.  Find the line which reads:

	CALL LANWP.BAT

    and comment it out by placing "REM " in front of it.

3.  Merge the contents of the LANWP.BAT file with the STARTNET.BAT file.

Note:  When you install the LAN WorkPlace software, the installation
program will update your TCP/IP software if the version of the software
that is contained on the LAN WorkPlace disks is newer.

=========================================
INSTALLING NetWare/IP OVER LAN WORKPLACE
=========================================

If you install the NetWare/IP client software on a workstation that
already contains the LAN WorkPlace product, be sure to merge the
contents of your existing LANWP.BAT file with the STARTNET.BAT file
that the NetWare/IP installation creates.

Note:  If your existing LAN WorkPlace contains newer TCP/IP software
than the NetWare/IP client software, the NetWare/IP installation
program will ask you whether it should overwrite the existing software.
You should select "NO" so that the newer TCP/IP software is maintained
on your system.

===================================================================
DELETING IP ADDRESSES FROM THE REPLICA DATABASE INFORMATION SCREEN
===================================================================

If you need to delete an IP address from the Replica Database Information
screen, use the <Backspace> key. The <Del> key does not work.

===============================================
CORRECTIONS TO NetWare/IP ADMINISTRATION GUIDE
===============================================

Page 3-3: The formulas for determining the memory requirements for the
DSS Server and NetWare/IP server should be changed to:

DSS Server:
        NetWare v3.11 or later:
          (a x 0.4) + 450 = memory in KB needed on the server.

        NetWare v4.01 or later:
          (a x 0.4) + 710 = memory in KB needed on the server.

NetWare/IP Server:
          (a x 0.35) + 75 = memory in KB needed on the server.

where "a" equals the number of the NetWare/IP servers in the network.




============
LIMITATIONS
============


The following lists the limitations of the NetWare/IP software.

1. Sometimes NWIP.EXE terminates by displaying the error message
   ".... cannot resolve NWIP domain name ....". If you get this error 
   message, try to re-execute NWIP.EXE to avoid the time delays
   associated with resolving the domain name. If, after you re-execute
   NWIP.EXE, the NetWare/IP domain still cannot be resolved, you need to
   check the DNS and DSS configuration and try again.

   Note: This error may also occur when you use the NWIPMAP command.
         
2. You can use NWIPMAP to connect to more than one remote NetWare/IP
   domain.  However, you should complete your drive mappings in one 
   remote domain before moving on to the next.  The most recent domain 
   to which you established an NWIPMAP connection is the one that 
   you can list and access resources.  If you need to revisit a domain
   in which you have some existing drive mappings, you may encounter 
   the error "Cannot find a server to attach in domain <domain name>".
   In this case, you may need to re-map some drives to the appropriate 
   servers.  Consider the following scenario:  

   	- Login to "local-server" in default NetWare/IP domain "netip.acme.com" 

	- Use "NWIPMAP G:=remote-server10\vol:@netip1.acme.com" to map
	  drive G: to "remote-server10" in remote domain "netip1.acme.com"

	- Use "NWIPMAP H:=remote-server20\vol:@netip2.acme.com" to map
	  drive H: to "remote-server20" in remote domain "netip2.acme.com"

	- Use "NWIPMAP I:=remote-server11\vol:@netip1.acme.com" to map
	  drive I: to "remote_server11" in remote domain "netip1.acme.com". 
	  At this point, you may need to re-map drive G: if the error
	  mentioned above is reported.

