NetWare/IP 2.2 Release Document README.TXT Copyright (c) 1996 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. *************************************************************************** CAUTION *************************************************************************** Always back up 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. *************************************************************************** CONTENTS *************************************************************************** Welcome to the NetWare/IP 2.2 software! This document contains last-minute information that is not included in the documentation. It includes the following sections: Client Support NetWare Client 32 for Windows 95 NetWare Client 32 for DOS and Windows NetWare DOS Requester (16-bit, VLM-based) Client Installing the Product Editing the Local SYS:ETC\HOSTS File Before Installing the Software Installing with the UnixWare NUC Package Installing the UNICON Management Groups Manually NetWare Language Support Running the Product with Other Software Compatibility with NLSP Compatibility with Broadcast Applications NetWare/IP 2.2 Support on SFT 3 Updates Required for Using NetWare/IP on NetWare 4.1 SFT3 Procedure to Configure NetWare/IP 2.2 on NetWare 4.1 SFT3 NetWare/IP Client for SFT3 Troubleshooting What to do if TCP/IP is Not Available What to do if there is a DSS Database Error Additional Issues Using a NetWare/IP Server as a Forwarding Gateway Pserver.nlm and lpr_gwy.nlm interoperability Using Different DSS-based SAP Filtering Criteria for the Same IPX Network Through Multiple Gateways Mixing NetWare/IP v2.2 and NetWare/IP v2.1 DSS Servers Using a Preferred DSS Server Statement with SFT3 Using NetWare/IP as the Transport for a NetWare Server Installation ============== Client Support ============== The following NetWare clients support the NetWare/IP software: NetWare Client 32 for Windows 95 NetWare Client 32 for DOS and Windows NetWare DOS Requester (16-bit, VLM-based) Client that ships with the NetWare/IP software ====================== Installing the Product ====================== Editing the Local SYS:ETC\HOSTS File Before Installing the Software =================================================================== The SYS:ETC\HOSTS file that installs with NetWare 4.10 contains several sample host entries that do not belong in the file. Before you install the product software, you should edit the SYS:ETC\HOSTS file to ensure that these entries do not exist. If the following entries exist in your HOSTS file, delete them: 127.0.0.1 loopback lb localhost # normal loopback address 130.57.4.2 ta tahiti ta.novell.com loghost 130.57.6.40 osd-frog frog 130.57.6.144 sj-in5 in5 192.67.172.71 sj-in1 in1 192.67.67.20 sri-nic.arpa nic.ddn.mil nic 26.2.0.74 wsmr-simtel20.army.mil simtel20 If you install the product without deleting these entries and you use local DNS, you can use UNICON to delete the entries. Installing with the UnixWare NUC Package ======================================== If your server runs the NUC.NLM package delivered with UnixWare, you must unload NETDB.NLM before installing this product. To unload this module, type the following at the server console prompt: UNISTOP Installing the UNICON Management Groups Manually ================================================ If you are able to log in as ADMIN when you install the NetWare/IP software, the installation program creates the UNICON management groups described in Chapter 5 of the NetWare/IP Administrator's Guide. These management groups are created in the server's default context. Once the groups are created, you can delegate UNICON management tasks by adding users to the appropriate groups. Because the groups are created in the default context, group members who log in using the group user object can be authenticated at the local partition rather than at the root partition. If you change the server's default context or if NDS is not installed on the server when NetWare/IP is installed, you must create the groups manually by typing the following command at the server console prompt: LOAD UNICON /L INITNWIP NetWare Language Support ======================== NetWare/IP 2.2 only supports the English language. When you install NetWare/IP 2.2 on a NetWare server with the LANGUAGE parameter set to French, Italian, German, or Spanish, the NetWare/IP installation program will automatically load using English. There is no need for you to change the LANGUAGE parameter value. ======================================= Running the Product with Other Software ======================================= Compatibility with NLSP ======================= NetWare/IP is fully compatible with the NLSP in its RIP/SAP Only mode. However, NetWare/IP is compatible with NLSP in its NLSP SAP/RIP Compatibility mode only as long as there are at least two NetWare/IP servers in the NetWare/IP network. Compatibility with Broadcast Applications ========================================= You can run non-SAP/RIP broadcast applications in multiple NetWare/IP domains on the same subnet. However, to prevent routing loops, you must make sure the NetWare/IP domains are using different UDP port numbers for NetWare/IP communications. NetWare/IP 2.2 Support on SFT3 =============================== Use the following procedures to set up the NetWare/IP 2.2 software on NetWare SFT3 servers: From a CD: 1. Install native NetWare. 2. Upgrade to SFT3. 3. Install NetWare/IP on NetWare SFT3 as described below. Over an IPX/IP network: 1. Load the NetWare IPX client software. 2. Install the NetWare server software from a remote installation path. 3. Reload the NetWare IPX client software. 4. Install NetWare updates to SFT3 from a remote installation path. 5. Install NetWare/IP on NetWare SFT3 as described below. Over an IP-only network: 1. Load the NetWare/IP client software. 2. Install the NetWare server software from a remote installation path with NetWare/IP. 3. Reload the NetWare/IP client software. 4. Install NetWare updates to SFT3 from a remote installation path. 5. Install NetWare/IP on NetWare SFT3. (This uninstalls the previous installation of NetWare/IP.) Updates Required for Using NetWare/IP on NetWare 4.1 SFT3 ========================================================= To fully support NetWare/IP on NetWare 4.1 SFT3, you need to update a few files. Use the following procedure to update your SFT3 system to enable support for NetWare/IP. 1. Copy the files in the \NWIP\EXTRA\SFTIII\IO directory on the NetWare/IP Installation CD-ROM to the boot directory from which the NetWare server is started. For example, you might copy the files to the following directory: C:\NWSERVER\PATCHES\SFTIII\IO\START 2. Modify the IOSTART.NCF file to include the following commands: LOAD C:\NWSERVER\PATCHES\SFTIII\IO\START\PM410.NLM LOAD C:\NWSERVER\PATCHES\SFTIII\IO\START\MAXPCKFX.NLM LOAD C:\NWSERVER\PATCHES\SFTIII\IO\START\PROTIDFX.NLM LOAD C:\NWSERVER\PATCHES\SFTIII\IO\START\RIPFIX.NLM LOAD C:\NWSERVER\PATCHES\SFTIII\IO\START\SHRRESFX.NLM 3. Copy the files in the \NWIP\EXTRA\SFTIII\MS directory on the NetWare/IP Installation CD-ROM to another directory under the server boot directory. For example, you might copy the files to the following directory: C:\NWSERVER\PATCHES\SFTIII\MS\START 4. Modify the MSSTART.NCF file to include the following commands: LOAD C:\NWSERVER\PATCHES\SFTIII\MS\START\PM410.NLM LOAD C:\NWSERVER\PATCHES\SFTIII\MS\START\RIPFIX.NLM Procedure to Configure NetWare/IP 2.2 on NetWare 4.1 SFT3 ========================================================= For more information on how to set up TCP/IP for SFT3, please refer to Technical Information Document under Netwire (TID021974), Supplement 1 - TCP/IP for SFT III. The following procedure requires that you load and configure TCP/IP from the .NCF files in the IO engines. For this procedure, we'll use the following TCP/IP configuration as an example: Internal Virtual LAN MSEngine: 130.57.4.165 (Network: 130.57.4.164, Node: 1) IOEngine: 130.57.4.166 (Network: 130.57.4.164, Node: 2) Netmask: 255.255.255.252 Actual LAN IO Engine 1: 130.57.6.116 IO Engine 2: 130.57.6.134 Netmask: 255.255.252.0 1. Determine the IP subnet used for the internal virtual LAN. 2. Manually edit the .NCF files for the IO engines to include the following lines. These files exist in the server boot directory of the IO engines respectively. IO Engine 1: IOSTART.NCF ioengine name SJF-NWIP-SFT3-IO1 ioengine ipx internal net 3003EE96 # # Load Hard Disk Driver # LOAD CPQS94.DSK LOAD CPQSDISK.DSK # # NOTE: We have observed that some MSL link driver # requires LAN Driver load here before # loading the MSL link driver or the LAN Driver # might hang during load. # If that is the case, load the LAN driver # before MSL but don't bind any # protocol to the LAN driver. # LOAD PCNTNW INT=5 PORT=7000 BOARD=1 # FRAME=Ethernet_II # NAME=PCNTNW_EII # # Load the MSL link here # LOAD DECMSL4X Slot=1 IO Engine 1: IOAUTO.NCF LOAD SNMP LOAD TCPIP RIP=YES Forware=YES # # Load LAN Driver here # LOAD PCNTNW INT=5 PORT=7000 BOARD=1 FRAME=Ethernet_II NAME=PCNTNW_EII # # Bind Protocol here # BIND IP MSENGINE Address=130.57.4.166 MASK=255.255.255.252 BIND IP PCNTNW_EII ARP=YES MASK=255.255.252.0 Address=130.57.6.116 # # Load NWIPIO (for IO engine communication) here # LOAD NWIPIO IOPARTNER=130.57.6.134 # # Now Bind a virtual IPX network between the IO # engines using NWIPIO # BIND IPX to NWIPIO NET=FEDC7846 IO Engine 2: IOSTART.NCF ioengine name SJF-NWIP-SFT3-IO2 ioengine ipx internal net 3003B463 # # Load Hard Disk Driver # LOAD CPQS94.DSK LOAD CPQSDISK.DSK # # NOTE: We have observed that some MSL link driver # requires LAN Driver load here before # loading the MSL link driver or the LAN Driver # might hang during load. # If that is the case, load the LAN driver # before MSL but don't bind any # protocol to the LAN driver. # LOAD PCNTNW INT=5 PORT=7000 BOARD=1 # FRAME=Ethernet_II # NAME=PCNTNW_EII # # Load the MSL link here # LOAD DECMSL4X Slot=1 IO Engine 2: IOAUTO.NCF LOAD SNMP LOAD TCPIP RIP=YES Forware=YES # # Load LAN Driver here # LOAD PCNTNW INT=5 PORT=7000 BOARD=1 FRAME=Ethernet_II NAME=PCNTNW_EII # # Bind Protocol here # BIND IP MSENGINE Address=130.57.4.166 MASK=255.255.255.252 BIND IP PCNTNW_EII ARP=YES MASK=255.255.252.0 Address=130.57.6.134 # # Load NWIPIO (for IO engine communication) here # LOAD NWIPIO IOPARTNER=130.57.6.116 # # Now Bind a virtual IPX network between the IO # engines using NWIPIO # BIND IPX to NWIPIO NET=FEDC7846 3. Run INETCFG.NLM in the MS engine to configure TCP/IP or modify the MS engine's MSAUTO.NCF file to add the following configuration: LOAD SNMP config=SYS:ETC LOAD TCPIP RIP=YES FORWARD=NO BIND IP MSENGINE Address=130.57.4.165 MASK=255.255.255.252 4. NetWare/IP can be installed and run in MS Engine using the IP address of 130.57.4.165. The two IO Engines are running as IP routers as far as NetWare/IP is concerned. NetWare/IP client for SFT3 ========================== You must upgrade your client software to the NetWare/IP 2.2 client for SFT3 to work. =============== Troubleshooting =============== What to Do if TCP/IP is Unavailable =================================== When using UNICON to log in to a remote server, you may get an error message indicating that TCP/IP is unavailable. This condition is temporary. If you receive this message, retry logging in to the server later. What to Do if there is a DSS Database Error =========================================== If you receive an error message indicating that there is a Btrieve error in the DSS database, you must reset the DSS database on the affected server. To reset the DSS database, type the following command at the server console prompt: load dss /resetdb ================= Additional Issues ================= Using a NetWare/IP Server as a Forwarding Gateway ================================================= By default, the NetWare/IP installation program adds the following line to the server's AUTOEXEC.NCF file to disable internal IPX routing: load ipxrtr routing=none If the server is later configured as a NetWare/IP forwarding gateway, this line needs to be commented out in the AUTOEXEC.NCF file. The server needs to rebooted for the NetWare/IP forwarding gateway to begin functioning. PSERVER.NLM and LPR_GWY.NLM Interoperability ============================================ If your server experiences an abend when unloading PSERVER.NLM, try the PSERVER.NLM file in the /NWIP/EXTRA/PSERVER directory on the NetWare/IP CD. This version fixed all known interoperability problems between PSERVER.NLM and LPR_GWY.NLM. Using Different DSS-based SAP Filtering Criteria for the Same IPX Network Through Multiple Gateways ========================================================================= If all 4 of the following conditions are true, the involved secondary DSS servers might have excessive checksum errors: 1. Multiple IP network segments corresponding to a single IPX network segment 2. An IP/IPX gateway connecting each IP network segment and the single IPX network segment---meaning that you have multiple gateways between a single IPX network and any number of IP network segments 3. Each IP/IPX gateway uses a different secondary DSS server 4. You are using DSS-based SAP filtering and have different criteria defined for each IP network segment For example, suppose a secondary DSS server and the IP/IPX gateway that uses that DSS server are in the 140.1.1.0 subnetwork and a different secondary DSS server and IP/IPX gateway are in the 140.1.2.0 subnetwork. If the SAP filtering criteria are defined such that the two DSS servers allow different sets of SAPs to go through, you will get excessive checksum errors on the secondary DSS servers. Mixing NetWare/IP v2.2 and NetWare/IP v2.1 DSS Servers ====================================================== If a NetWare/IP v2.1 secondary DSS server is used as the DSS server for a NetWare v2.2 IP/IPX gateway, there might be an excessive number of checksum errors, especially if the IPX network contains a lot of SAPs. This situation can be resolved by setting the NetWare/IP v2.1 secondary DSS server to function as a non-dedicated DSS server. To do this, modify the SYS:\ETC\NWPARAMS file by adding a "DEDICATED_DSS 0" line under the [DSS] section; then, unload and reload the DSS service. Using a Preferred DSS Server Statement with SFT3 ================================================ You must use an IP address or host name for the Preferred DSS Server statement for a NetWare/IP server running in a SFT3 MS Engine. Using NetWare/IP as the Transport for a NetWare Server Installation =================================================================== When NetWare/IP is used as transport for an across the wire NetWare server installation, communication between servers is dependent on the database zone transfer setup of NetWare/IP. This dependency might cause the login process (server to server login) to take more time than normal.