NOVELL TECHNICAL INFORMATION DOCUMENT TITLE: NIP199.TXT README FOR: NIP199.EXE NOVELL PRODUCTS and VERSIONS: NetWare/IP 2.2 ABSTRACT: NetWare IP patch, to be applied to NWIP 2.2x only. Various fixes to DNS, LPR, and NWIP functions. ----------------------------------------------------------------- DISCLAIMER THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS 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. ----------------------------------------------------------------- ISSUE: NetWare/IP NIP199 Patch Release Document *************************************************************************** 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: Problems fixed in this release Running the Product with Other Software Compatibility with NLSP Compatibility with Broadcast Applications NetWare/IP 2.2 Support on SFT 3 Procedure to Configure NetWare/IP 2.2 on NetWare 4.1x 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 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 Using Filtcfg.NLM with NetWare/IP ============================== Problems fixed in this release ============================== - NWIP.NLM and NWIPIO.LAN are not returning correct configuration information - client with invalid IP (local subnet broadcast) address produces excessive traffic - NWIP NT client advertised SAP has hop value of 255 in DSS data base - NWIP client advertised SAP did not show up in display servers - NetWare/IP server did not return NWIP parameters when DSS is down - The NetWare DNS server did not properly handle a primary domain name suffixed with anything other than .COM. - UNICON failed to save the DNS database to text files. The following error message was displayed: "NIS and DNS services not configured to run on this machine." - The NetWare DNS server did not properly resolve the MX (mail exchange) query. - The NetWare DNS Server abended while doing a zone dump from a secondary server when the size of the reply was larger than the buffer allocated by the DNS server. - LPR clients were unable to submit print jobs to NetWare queues when the queue names were longer than eight characters. - LPR gateway jobs were printed twice if the printer ran out of paper. When more paper was added, the printer finished the interrupted print job and then printed the job again. - When using the LPR gateway, PSERVER showed "PRINTER MAY NEED ATTENTION" status and had to be restarted. - When using the LPR Gateway, PSERVER showed the XRP printer state changing between "Ready for New Job" and "Error at remote Unix host." The PKERNEL module displayed the following error message: "No sequence numbers available for the remote host." - When the LPR Gateway was unloaded and then loaded again, the LPR Gateway displayed the error message: "No configured UNIX printers." - NWIP client will crash workstation on modem re-dial - NWIP MIB did not have correct trap definition - SFT3 and NWIP 2.2 performance problem with packet burst on Token-Ring - Filtering on behave on pre-2.2 S-DSS, the P-DSS was sending the local route to the 2.2 S-DSS - There is a delay in the Netware/IP Gateway to the Primary DSS forced synchronization - Improved zone transfer checksum handling in all NWIP components - The NetWare DNS server did not properly handle a primary domain name suffixed with anything other than .COM. - UNICON failed to save DNS database to text files. Error message "NIS and DNS services not configured to run on this machine" was displayed. - NetWare DNS server did not properly resolve the MX (mail exchange) query. - NetWare DNS Server abended while doing a zone dump from a secondary server when the size of the reply was larger than the buffer allocated by the DNS server. - When NetWare print services loaded while NDS is unloaded, server abended with the message: "NLM unloaded without deleting all its semaphore". - LPR clients were unable to submit print jobs to NetWare queues with long names. - LPR Gateway jobs were printed twice if the printer runs out of paper and more paper was added during the job. - LPR Gateway displayed the error message "No configured UNIX printers" after the LPR GWY has been previous unloaded. ========================================= 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/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/IP on NetWare SFT3. (This uninstalls the previous installation of NetWare/IP.) Procedure to Configure NetWare/IP 2.2 on NetWare 4.1x 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. Make sure IPXRTR.NLM is not loaded in the MSEngine. NetWare/IP client for SFT3 ========================== You must upgrade your client software to the NetWare/IP 2.2 client for SFT3 to work. If token ring network is used, set the link support line in net.cfg to be 4170. For example, Link Support Buffers8 4170 MemPool4096 =============== 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 be rebooted for the NetWare/IP forwarding gateway to begin functioning. 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. Using Filtcfg.NLM with NetWare/IP ================================= In order for filtcfg.nlm to work with NetWare/IP, NWIP.NLM must be loaded with a board name. You can do this via inetcfg.nlm. From inetcfg boards option, select NWIP and define a board name for it. ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. ----------------------------------------------------------------- Self-Extracting File Name: NIP199.EXE Files Included Size Date Time ..\ NIP199.TXT (This file) ..\NWIP1\ NIP199.IPS 1061 10-17-96 11:26:10 pm ..\NWIP1\ETC\ DSSMIB.MIB 7025 6-7-96 6:03:00 pm ..\NWIP1\SYSTEM\ CONFADDR.NLM 27576 9-19-96 11:00:06 pm DISPATCH.NLM 18236 9-27-96 11:38:34 pm DLLINFO.NLM 3200 9-27-96 11:49:46 pm DNSADMIN.NLM 43827 9-19-96 11:18:12 pm DNSAGENT.NLM 32828 9-19-96 11:13:54 pm DNSCONV.NLM 3674 9-19-96 11:11:08 pm DNSDBGEN.NLM 12992 9-19-96 11:18:42 pm DNSUTIL.NLM 2459 9-19-96 11:18:56 pm DSS.NLM 128566 7-2-96 3:40:46 am DSSAGT.NLM 18735 5-15-96 2:44:30 am IOTADJST.NLM 4294 9-27-96 11:50:04 pm IOXCSTUB.NLM 4771 9-19-96 11:10:54 pm LPRLOAD.NLM 2277 9-27-96 11:48:52 pm LPR_GWY.NLM 19373 9-27-96 11:48:44 pm MSTADJST.NLM 3507 9-27-96 11:50:12 pm MSXCSTUB.NLM 3558 9-19-96 11:10:28 pm NAMED.NLM 34693 9-19-96 10:54:22 pm NETDB.NLM 48596 9-19-96 10:49:52 pm NISBIND.NLM 21609 9-27-96 11:40:28 pm NISDMAG.NLM 32994 9-27-96 11:40:12 pm NISGO.NLM 16435 9-27-96 11:40:46 pm NISSERV.NLM 23947 9-27-96 11:41:02 pm NWCCSS.NLM 3676 6-18-96 3:26:32 am NWIP.NLM 150334 7-15-96 8:56:30 pm NWIPAGT.NLM 16939 5-15-96 2:46:08 am NWIPIO.LAN 9858 7-15-96 8:55:00 pm PRLIB.NLM 22034 9-27-96 11:47:56 pm RPCBSTUB.NLM 585 6-29-96 2:10:18 pm SRVAGT.NLM 22596 9-27-96 11:39:36 pm TADJST.NLM 2299 9-27-96 11:49:54 pm TELNETD.NLM 10937 9-19-96 11:19:48 pm TIMCHK.NLM 2243 9-27-96 11:49:34 pm UNICON.NLM 92346 9-27-96 11:39:08 pm UNICRYPT.NLM 2484 9-27-96 11:37:56 pm UNIDLL.NLM 4446 9-27-96 11:49:40 pm UNINSTAL.NLM 93614 11-15-95 2:08:56 am UNIXLIB.NLM 32780 9-27-96 11:49:24 pm USRAGT.NLM 15695 9-27-96 11:39:46 pm V_NFS.NLM 4936 9-27-96 11:49:00 pm XCONSOLE.NLM 4078 9-19-96 11:20:20 pm XCONSSRV.NLM 67576 9-19-96 11:10:02 pm YPXFR.NLM 21827 9-27-96 11:41:20 pm ..\NWIP1\SYSTEM\NLS\ ..\NWIP1\SYSTEM\NLS\4\ CONFADDR.MSG 2201 9-19-96 11:00:02 pm DISPATCH.MSG 1882 9-27-96 11:38:32 pm DNSADMIN.HLP 6167 6-1-95 12:25:56 am DNSADMIN.MSG 5213 9-19-96 11:18:08 pm DNSAGENT.MSG 2028 9-19-96 11:13:52 pm DNSCONV.MSG 474 9-19-96 11:11:08 pm DSS.MSG 22731 5-8-96 10:57:42 pm DSSAGT.MSG 1216 12-5-95 8:32:46 pm IOTADJST.MSG 655 9-27-96 11:50:02 pm IOXCSTUB.MSG 747 9-19-96 11:10:54 pm LPRLOAD.MSG 323 9-27-96 11:48:50 pm LPR_GWY.MSG 3831 9-27-96 11:48:40 pm MSTADJST.MSG 533 9-27-96 11:50:10 pm MSXCSTUB.MSG 527 9-19-96 11:10:28 pm NAMED.MSG 4803 9-19-96 10:54:18 pm NETDB.MSG 2013 9-19-96 10:49:48 pm NWIP.MSG 11787 5-8-96 10:44:18 pm NWIPAGT.MSG 320 12-5-95 8:33:08 pm NWIPIO.MSG 1588 12-5-95 8:50:02 pm PRLIB.MSG 1586 9-27-96 11:47:52 pm SRVAGT.MSG 1354 9-27-96 11:39:32 pm TADJST.MSG 197 9-27-96 11:49:52 pm TELNETD.MSG 1822 9-19-96 11:19:46 pm TIMCHK.MSG 318 9-27-96 11:49:32 pm UNICON.HLP 15185 5-31-95 4:12:20 pm UNICON.MSG 10329 9-27-96 11:39:00 pm UNINSTAL.HLP 898 3-3-95 9:01:18 pm UNINSTAL.MSG 11891 11-15-95 2:08:50 am UNIXLIB.MSG 2333 9-27-96 11:49:22 pm USRAGT.MSG 705 9-27-96 11:39:44 pm V_NFS.MSG 986 9-27-96 11:48:58 pm XCONSOLE.MSG 799 9-19-96 11:20:20 pm XCONSSRV.MSG 4454 9-19-96 11:09:58 pm ..\WSDOS\ NWIP.EXE 44452 6-7-96 3:43:56 am NWIPWIN.EXE 52224 6-15-96 4:03:38 am Installation Instructions: ================================================================ INSTALLATION OF THE PATCH NIP199 ================================================================ 1. Backup your current SYS:SYSTEM and SYS:ETC subdirectories as a precaution. 2. At a work station attached to the NetWare 4.1 server, create a new directory on any NetWare volume. The directory can have any name. MD NIP199 3. Copy NIP199.EXE into the new directory. COPY NIP199.EXE NIP199 4. Type NIP199 to extract the files. CD NIP199 NIP199 5. From the server console, run UNISTOP.NCF as a general precaution. UNISTOP 6. From the server console, activate the installation program. LOAD INSTALL 7. Select PRODUCT OPTIONS. The Currently Installed Products Menu appears and lists the following: NWIP 2.2b NetWare/IP 2.2 8. Press to install new product. 9. Press to install the files in NIP199. The "SPECIFY DIRECTORY PATH" dialogue box will appear. 10. Enter the path to the directory where the NIP199 files were extracted, in the NWIP1 subdirectory. SYS:/NIP199/NWIP1 After the installation program installs the files, the "Currently Installed Products" menu will list: NWIP 2.2bNetWare/IP 2.2 NWUPD2.2c ETF-F199 NetWare/IP Patch 11. Exit the Installation program or press + to return to the system console prompt. 12. From the server console, run UNISTART.NCF to restart NetWare/IP (and other products if installed). ----------------------------------------------------------------- Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. -----------------------------------------------------------------