NetWare/IP 2.2B Release Document
README.1ST
**************
ABSTRACT
**************
NIP22B.EXE upgrades the server's NetWare/IP to v2.2B. Customers who have
downloaded NIPS22.EXE previously DO NOT need to download this. It is required
for all NetWare 4.10 sites that want to run IP. To use NIP22B, you must also
download and install NIPW22.EXE. NetWare/IP is a set of NetWare Loadable
Modules (NLMs) and client software that enables existing NetWare 3 and 4
servers to use TCP/IP or Novell's IPX (or both) as their transport protocol.
**************
CONTENTS
**************
Welcome to the NetWare/IP 2.2B software! With NetWare/IP, you have the
flexibility of running TCP/IP and/or Novell's IPX, thus allowing you to deploy
a total IP solution or a mixed IPX-IP solution in one NetWare environment.
All existing NetWare services run unmodified with NetWare/IP.
This document contains information about the contents of the NetWare/IP
Installation CD-ROM and installation procedures using the CD-ROM that are not
included in the documentation.
Included in this document is information on features, documentation, and
installation. It organized into the following sections:
New NetWare/IP 2.2B Features
Features and Enhancements
Known Problems
Troubleshooting
Additional Issues
CD-ROM Contents
Installing the Online Documentation to a Network
Viewing the Online Documentation
Viewing the Documentation from the CD-ROM
Viewing the Documentation from a NetWare Server
Viewing the Documentation from a Local Hard Drive
Printing the Hardcopy Documentation
Installing the NetWare/IP Server Software
Installing the NetWare/IP Server Software Remotely
Install from a CD-ROM Mounted as a NetWare Volume
Installation Notes
Note: To install the NetWare/IP 2.2B Server software, also follow the
detailed instructions in Chapters 1 through 5 of the NetWare/IP
Administrator's Guide.
New NetWare/IP 2.2B Features
============================
NetWare/IP Server Features
--------------------------
1. New TCPIP that addresses the problem with TCPIP DOWN and hang on CLIB close
2. Removed a harmless error message on NetWare/IP server initialization. The
message "NWIP parameter file nwipip.dmp can not open for write" applies to
customers who have only one NetWare/IP server.
3. Add an alert message when IPXRTR is loaded and NWIP server is configured as
non-forwarding gateway.
4. Add PSERVER.NLM to \NWIP\EXTRA\PSERVER directory. This NLM solves all
outstanding LPR_GWY interoperability problems.
DHCP Server
-----------
1. UI will allow the using of host name in preferred DSS and nearest NWIP
server fields.
2. DHCP server will handle NWIP for Win95 client DHCP requests correctly. The
rev 2.0 of DHCP server did not work with the original NWIP for Win95 client.
The Win95 client PPP release is changed to bypass this problem. This new rev
of DHCP server will work with all FCS releases of NWIP for Win95 client.
Features and Enhancements
=========================
1. Client Support
The following NetWare clients support NetWare/IP:
- NetWare Client 32 for Windows 95
- NetWare Client 32 for DOS and Windows
- NetWare DOS Requester (16-bit, VLM-based) Client that ships with NetWare/IP
2. Fully compatible with 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.
3. 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.
4. Supported on SFT3 including NetWare 4.1 SFT3
5. Can act as a Forwarding Gateway
6.NetWare/IP comes with the following components:
- DNS.NLM (BIND 4.8.3)- NetWare/IP can be deployed without DNS, with an
existing Unix DNS or with this NLM acting as the DNS.
- Domain RIP/SAP Service (DSS.NLM)- this NLM allows IP nodes to get server and
route info
- NetWare Server and Client Files- these NLMs insure 100% backward
compatibility
- NetWare IP/IPX Gateway-allows IP/IPX coexistence for phased migrations
- XCONSOLE, telnet and SNMP MIB Support for manageability
7. NetWare/IP version 2.2 for NetWare 4 is enhanced in the following ways:
- The addition of a DHCP Server for IP address leasing (backward compatible
with BOOTP clients) lpr/lpd support for NetWare to Unix or IP-based Printing
- Supports IP stacks from Microsoft that use the TDI Interface (Win95, Win NT)
- Supports 3rd party IP stacks (FTP Software and others to follow)
- Allows NetWare/IP to be deployed with or without DNS
- Reduces network traffic and CPU utilization with optimized algorithm for
service updates.
- The NetWare DHCP server can support those DHCP parameters (e.g NetBIOS) used
by Windows 95 and NT workstations.
8. NetWare/IP Version 2.2 is for NetWare 4 networks. NetWare/IP Version 2.2 is
a replacement/upgrade for NetWare/IP Version 2.1. NetWare 3 customers should
use NetWare/IP Version 1.1 plus some patches.
9. NetWare/IP greatly reduces WAN traffic and router overhead, and increases
the manageability of IP-based internetworks.
10. NetWare/IP version 2.2 is available free of charge to NetWare 4 customers
via www.novell.com or CompuServe's NetWire Forum.
Known Problems
==============
Remote installation of the DHCP Server does not work at this time.
Installation of the DHCP Server must be done locally.
Troubleshooting
===============
1. 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.
2. 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 <Enter>
Additional Issues
=================
1. 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 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 AUTOEXEC.NCF. The server needs to rebooted
for the NetWare/IP forwarding gateway to begin functioning.
2. PSERVER.NLM and LPR_GWY.NLM Interoperability
-----------------------------------------------
If your server experiences an abend when unloading PSERVER.NLM, try the
PSERVER.NLM file in /NWIP/EXTRA/PSERVER. This version fixed all known
interoperability problems between PSERVER.NLM and LPR_GWY.NLM.
3. 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.
4. Mixing NetWare/IP v2.2B 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.2B IP/IPX gateway, there might be an excessive number of checksum
errors, especially if the IPX network contains a lot of SAPs. This 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.
5. 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.
6. 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.
CD-ROM Contents
===============
This CD-ROM contains the following files and directories:
\README.1ST -- This document
\NWIP\EXTRA\INSTLL -- INSTALL patch to support server-to-server install on
NetWare 4.1
\NWIP\EXTRA\SFTIII -- SFT III patch for NetWare/IP
\NWIP\EXTRA\TCPIP -- TCP/IP patch for NetWare/IP
\NWIP\NWIP1\README.TXT -- The NetWare/IP server software Read Me . Read this
file before using NetWare/IP 2.2.
\NWIP\NWIP1 -- NetWare/IP server software disk #1
\NWIP\NWIP2 -- NetWare/IP server software disk #2
\NWIP\NWIP3 -- NetWare/IP server software disk #3
\DHCP\DHCPSRVR -- DHCP server software disk
\PSFILES -- NetWare/IP Administrator's Guide in PostScript file format
Installing the Online Documentation to a Network
================================================
You can use the NetWare INSTALL utility to install the NetWare/IP 2.2 online
documentation.
1. At the console prompt, type: LOAD INSTALL <Enter>
2. From "Installation Options," choose "Product Options."
3. From "Other Installation Action," choose "Choose an Item or Product Listed
Above."
4. Choose "Install Online Documentation and Viewers."
5. Press <F3> and enter the path to the NetWare/IP CD-ROM.
If the CD-ROM drive is installed as a DOS device, enter the drive letter. If
the CD-ROM drive is mounted as a NetWare volume, enter the volume name
followed by a colon. In this case, type: NWIP220: <Enter>
6. From the list of available file groups, select both the documentation
database and the DynaText viewer.
7. Accept the marked file groups by pressing <F10>.
8. When prompted, specify where to install the documentation database.
The default location is SYS:DOC. If you change the default, edit the system
configuration file, SYS:PUBLIC\SYSDOCS.CFG, as explained in "SYSDOCS.CFG" on
page 30 of the "Installing and Using Novell Online Documentation" manual.
Viewing the Online Documentation
================================
You can view the online documentation using one of the following methods:
- You can access the online viewer and documentation directly from the CD-ROM.
This method provides the slowest access speed but requires no disk space on a
server or workstation.
- You can access the online viewer and documentation directly from a NetWare
server.
- You can install both the online viewer and the documentation on a
workstation's hard drive. This method provides the fastest access speed, but
requires approximately 9 MB of disk space.
The following sections provide procedures for each method.
Viewing the Documentation from the CD-ROM
-----------------------------------------
Use the following procedure to view the online documentation from the CD-ROM:
1. From Windows Program Manager, select "Run" from the "File" menu.
2. Type the path to \DOCVIEW\DTAPPWIN\DTEXTRW.EXE. For example, if the CD-ROM
drive is D:, enter the following command in the Command Line field of the Run
box: D:\DOCVIEW\DTAPPWIN\DTEXTRW.EXE
3. Click "OK."
Viewing the Documentation from a NetWare Server
-----------------------------------------------
After installing the online documentation to a NetWare server, use the
following procedure to view the online documentation from the server:
1. To use a viewer installed on the network, map a drive to the volume
containing the viewer application files (usually servername\SYS:).
2. From Windows Program Manager, select "Run" from the "File" menu.
3. Type the path to SYS:\DOCVIEW\DTAPPWIN\DTEXTRW.EXE file on the server. For
example, if you mapped drive Y: to the SYS: volume, enter the following
command in the Command Line field of the Run box:
Y:\DOCVIEW\DTAPPWIN\DTEXTRW.EXE
4. Click "OK."
Viewing the Documentation from a Local Hard Drive
-------------------------------------------------
Use the following procedure to view the online documentation from the hard
drive:
1. Copy the following directories to the root of the local hard drive:
\DOC
\PUBLIC
\DOCVIEW
2. From Windows Program Manager, select "Run" from the "File" menu.
3. Type the path to \DOCVIEW\DTAPPWIN\DTEXTRW.EXE. For example, if you copied
the directories to C:, type the following command in the Command Line field of
the Run box:
C:\DOCVIEW\DTAPPWIN\DTEXTRW.EXE
4. Click "OK."
Printing the Hardcopy Documentation
===================================
You can print hardcopy manuals from the PostScript files included on the CDROM
in the \PSFILES directory.
To print the PostScript files included on the CD-ROM, enter the following
command at the DOS prompt of a workstation with a CD-ROM drive:
nprint cd_drive:\PSFILES\*.* Q=queue_name
where cd_drive is the drive letter for the CD-ROM drive and queue_name is the
name of a network print queue that is serviced by a network printer that
supports PostScript.
Installing the NetWare/IP 2.2B Server Software
==============================================
NIP22B.EXE (server) needs to be run in conjuction with NIPW22.EXE
(workstation). Download and install NIPW22.EXE.
It is important that you read and understand Chapters 1 through 5 of the
NetWare/IP Administrator's Guide before installing NetWare/IP 2.2B. Appendix
F contains worksheets that can help you plan your configuration. Proper
planning will help ensure a successful installation.
Chapters 1 through 5 will help you install NetWare IP 2.2B. However, do not
attempt to run NetWare/IP without reviewing the configuration information and
performing all the steps to properly configure NetWare/IP.
Installing the NetWare/IP 2.2B Server Software Remotely
=======================================================
If you are installing NetWare/IP via a network connection and are converting a
NetWare/IP client workstation to a NetWare/IP server with TCP/IP as the
transport protocol, you need to use the INSTLL patch from the NetWare/IP
Installation CD-ROM. The INSTLL patch is for the NetWare 4.1 INSTALL NLM and
is in the \NWIP\EXTRA\INSTLL directory. Copy the patch to the server from
which you are running the installation program. Follow the instructions
included with the patch to prepare for installing NetWare 4.1 via a NetWare/IP
connection.
Install from a CD-ROM Mounted as a NetWare Volume
-------------------------------------------------
This procedure assumes that you already have a NetWare CDROM driver loaded and
your drive is operational. Please refer to the NetWare 4.1 installation manual
for more information on the CD-ROM driver. If you are installing NetWare/IP
from NetWare 4.1 customized install, please do the following when prompted to
install NetWare/IP:
1. Press <Alt>+<ESC> to go to system console
2. At the console prompt, load the CDROM.NLM driver. For example, if the DOS
NetWare boot drive is C:, type:
LOAD C:NWPA <Enter>
LOAD C:CDROM <Enter>
CD MOUNT NWIP220 <Enter>
3. Press <Alt>+<ESC> to go back to the install screen and choose <YES> to
install NetWare/IP
4. When prompted to insert a diskette into Drive A, press <F3> and type the
following path: NWIP220:NWIP
5. Complete Steps 5 through 15 in "Installing NetWare/IP on a NetWare 4
Server" on page 75 of the NetWare/IP Administrator's Guide.
When you finish installing and configuring NetWare/IP, the INSTALL utility
resumes control. Continue with "Installing NetWare Directory Services" on
page 130 of the NetWare 4.1 Installation manual.
Installation Notes
==================
1. 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.
2. The SYS:ETC\HOSTS that installs with NetWare 4.10 contains several sample
host entries that do not belong in the file. Before you install NetWare/IP
2.2B, edit SYS:ETC\HOSTS 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 NetWare/IP 2.2B before deleting these entries, and you use
local DNS, you can use UNICON to delete the entries.
3. Installing with the UnixWare NUC Package
--------------------------------------------
If your server runs the NUC.NLM package delivered with UnixWare, you must
unload NETDB.NLM before installing NetWare/IP 2.2B. To unload this module,
type the following at the server console prompt:
UNISTOP <Enter>
4. Installing the UNICON Management Groups Manually
---------------------------------------------------
If you are able to log in as ADMIN when you install NetWare/IP 2.2B, 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 <Enter>
5. NetWare Language Support
---------------------------
NetWare/IP 2.2B only supports the English language. If NetWare/IP 2.2B is
installed 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.
6. NetWare/IP 2.2B Support on SFT3
----------------------------------
Use the following procedures to set up NetWare/IP 2.2B on NetWare SFT3
servers:
Over an IPX/IP network:
1. Load the NetWare IPX client.
2. Install the NetWare server software from a remote installation path.
3. Reload the NetWare IPX client.
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.
2. Install the NetWare server 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.)
7. 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 \NWIP\EXTRA\SFTIII\IO 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 IOSTART.NCF 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 \NWIP\EXTRA\SFTIII\MS to another directory under the
server boot directory. For example, you might copy the files to:
C:\NWSERVER\PATCHES\SFTIII\MS\START
4. Modify the MSSTART.NCF to include the following commands:
LOAD C:\NWSERVER\PATCHES\SFTIII\MS\START\PM410.NLM
LOAD C:\NWSERVER\PATCHES\SFTIII\MS\START\RIPFIX.NLM
8. Procedure to Configure NetWare/IP 2.2B 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.
9. NetWare/IP client for SFT3
-----------------------------
You must upgrade your client to the NetWare/IP 2.2 client for SFT3 to work.
