home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Encyclopedia 96-1
/
novell-nsepro-1996-1-cd2.iso
/
download
/
netware
/
lo30t1.exe
/
LO30T1.TXT
next >
Wrap
Text File
|
1995-06-26
|
11KB
|
347 lines
NOVELL TECHNICAL INFORMATION DOCUMENT
TITLE: Updated Stack for LWP for OS/2 v3.0
README FOR: LO30T1.EXE
NOVELL PRODUCTS and VERSIONS:
LAN WorkPlace for OS/2 3.0
ABSTRACT:
LO30T1.EXE documents the TCP/IP transport update for the LAN
WorkPlace for OS/2 version 3.0 product. Please read this file
carefully before attempting to install the patch.
-----------------------------------------------------------------
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:
TABLE OF CONTENTS
1.0 INTRODUCTION
2.0 CHANGES IMPLEMENTED BY THIS PATCH
2.1 Changes to TCPIP.OS2
2.2 Changes to PTCPIP.OS2, SKTDRV.OS2 and VTCPIP.OS2
2.3 Changes to Protocol TCPIP Settings in NET.CFG
2.3.1 Directory Path Settings
2.3.2 Address Settings
2.3.3 TCP/IP Settings
2.3.4 NETBIOS Settings
2.4 Changes to NET.CFG Link Driver Settings
3.0 IMPORTANT INSTALLATION NOTES
3.1 HOW TO APPLY THIS PATCH
---------------------------------------------------------------
1.0 INTRODUCTION
This document is formatted as a reference document. Rather than
reading this entire document, use the Table of Contents to
determine which sections to read in detail.
1.1 - DESCRIPTION
LO30T1.EXE documents the TCP/IP transport update for the LAN
WorkPlace version 3.0 for OS/2 product. Please read this file
carefully before attempting to install the patch.
1.2 - PATCH HISTORY
None - First updated patch for the TCP/IP transport
2.0 CHANGES IMPLEMENTED BY THIS PATCH
This section lists the changes implemented by this patch.
2.1 Changes to TCPIP.OS2
* Does not support NETSTAT.EXE utility.
* Supports static route.
* 16-bit WINSOCK supported. All 16-bit WINSOCK compliant
applications should run without modification.
* Supports BOOTP.
* Allows multiple default routers configuration (up to 3
routers can be specified), and detects dead router and switches
automatically to the next router.
* Able to send out-of-band (OOB) urgent data byte for
applications that require the urgent data delivery service.
* Supports automatic protocol registration for frame types
FDDI_SNAP and IBM_PCN2_SNAP. Refer to section 2.3 for details.
* Detects duplicate IP addresses. TCPIP.OS2 will not load if
the assigned local IP address is being used by another node on
the local network. An error message will be displayed with a
hardware address of the node currently using that IP address.
2.2 Changes to PTCPIP.OS2, SKTDRV.OS2, and VTCPIP.OS2
* Suppots new WLIBSOCK.DLL.
2.3 Changes to Protocol TCPIP Settings in NET.CFG
2.3.1 Directory Path Settings
Support for the following NET.CFG keywords has been added:
* PATH SCRIPT [[drive:] path[;...]]
Specifies the directory or directories that contain script
files. The syntax is the same as the DOS PATH command.
* PATH PROFILE [[drive:] path[;...]]
Specifies the directory or directories that contain profile
files. The syntax is the same as the DOS PATH command.
* PATH LWP_CFG [[drive:] path[;...]]
Specifies the directory or directories that stores the LAN
WorkPlace internal configuration and data files. The syntax is
the same as the DOS PATH command.
* PATH TCP_CFG [[drive:] path[;...]]
Specifies the directory or directories that stores the LAN
WorkPlace database configuration files HOSTS, NETWORKS, PROTOCOL.
SERVICES, and RESOLV.CFG. The syntax is the same as the DOS PATH
command.
Example: Protocol TCPIP
PATH SCRIPT C:\LANWP\SCRIPT
PATH PROFILE :\LANWP\PROFILE
PATH LWP_CFG :\LANWP\HSTACC
PATH TCP_CFG C:\LANWP\TCP
2.3.2 Address Settings
Support for the following NET.CFG keywords has been added:
* ROUTE [NET | HOST] [net_address;host_address]
[router_address]
Specifies network or host based static route. Up to 5
static routes can be specified.
Example: Protocol TCPIP
#
# the following "route" parameter line configures
# a host specific static route to host with IP
# address 128.57.225.24 through the router
# 128.57.4.19
#
route host 128.57.225.24 128.57.4.19
#
# the following "route" parameter line configures
# a static route to class B network 128.90.0.0
# through the router 128.57.6.55
#
route net 128.90.0.0 128.57.6.55
* ARP [Yes | No]
Specifies enabling or disabling ARP packets transmission.
The default value is Yes. User may use this parameter to disable
sending of ARP packets on a ARCNET environment.
* Multiple default routers can be specified and configured.
"IP_ROUTER" keyword can be specified up to 3 times for each
network interface to enter IP addresses of a default router and
alternative routers.
Example: Protocol TCPIP
ip_router 128.57.4.254
#
# the following "ip_router" parameter line
# specifies a secondary default router to use when
# the primary (the first router specified above) fails
#
ip_router 128.57.4.19
2.3.3 TCP/IP Settings
Support for the following NET.CFG keywords has been added:
* TCP_WINDOW [maximum TCP receive window size]
Specifies the initial (maximum) TCP receive window size.
In prior version of TCPIP.OS2, TCP receive window size was not
changeable and was determined by the underlying MLID's maximum
receive datagram size.
Example: Protocol TCPIP
#
# the following "tcp_window" parameter sets the
# maximum TCP receive window size to 8192 bytes
#
tcp_window 8192
* TCP_MAXSEGSIZE [maximum TCP packet segment size]
Specifies the maximum TCP packet segment size to be used
when communicating with other nodes. Prior version of TCPIP.OS2
used the maximum packet size of the underlying LAN driver to
determine this value.
Example: Protocol TCPIP
#
# the following "tcp_maxsegsize" parameter sets the
# maximum TCP segment size to 512 bytes
#
tcp_maxsegsize 512
* TCP_MINRXMIT [minimum TCP retransmit interval ticks]
Specifies a minimum value for retransmit interval that TCP
will use. If omitted, the default value is 1 tick.
Default value: 1 tick
Minimum value: 1 tick
Maximum value: 540 ticks
Example: Protocol TCPIP
#
# the following "tcp_minrxmit" parameter sets the
# minimum TCP retransmit interval to 18 ticks
#
tcp_minrxmit 18
* TCP_MAXRXMIT [maximum TCP retransmit interval ticks]
Specifies a maximum value of the retransmit interval TCP
will use. If omitted, the default value is 540 ticks.
Default value: 540 ticks
Minimum value: 1 tick
Maximum value: 540 ticks
Example: Protocol TCPIP
#
# the following "tcp_maxrxmit" parameter sets the
# maximum TCP retransmit interval to 240 ticks
#
tcp_maxrxmit 240
* RT_TRIGGER [number of TCP retransmit]
Specifies a value to set TCP retransmit threshold for
triggering router switch when dead router is detected. If
omitted, the default value is 3 TCP retransmits.
Default value: 3 retransmits
Minimum value: 1 retransmit
Maximum value: 255 retransmits
Example: Protocol TCPIP
#
# the following "rt_trigger" parameter sets a TCP
# retransmit threshold for triggering router
# switch
#
rt_trigger 5
* NO_BOOTP
Specifies whether to bypass BOOTP and use Reverse ARP to
identify a LAN WorkGroup client's IP address or to get the
client's IP address from BOOTP from the LAN WorkGroup server. If
omitted, the default is to use BOOTP first and Reverse ARP
second.
2.3.4 NETBIOS Settings
Support for the following NET.CFG keyword has been added:
* NB_BRDCAST [0|1]
Specifies the format of IP broadcast used when RFCNBIOS.EXE
sends broadcast messages. Setting NB_BRDCAST to 0 sets the host
portion of a broadcast address to zeros. For example, a Class B
network with a network address of 129.47 would have a broadcast
address of 129.47.0.0. Setting NB_BRDCAST to 1 on the same Class
B network would set the broadcast address to 129.47.255.255.
2.4 Changes to NET.CFG Link Driver Settings
* User no longer needs to specify frame types for FDDI_SNAP
and IBM_PCN2_SNAP.
3.0 IMPORTANT INSTALLATION NOTES
This section describes important information about applying this
patch to the LAN WorkPlace TCPIP transport version 3.0 for OS/2
product.
3.1 HOW TO APPLY THIS PATCH
Backup the old files before applying this patch.
Copy the following files to the installed LAN WorkPlace TCPIP
version 3.0 for OS/2 directory \LANWP\BIN40:
WINSOCK.DLL, WLIBSOCK.DLL, NOVASYNC.EXE
NOVASYNC.EXE is called by WINSOCK.DLL, you do not have to load
it into memory.
Copy the following files to \LANWP\TCPIP directory:
TCPIP.OS2, PTCPIP.OS2, SKTDRV.OS2, VTCPIP.OS2
This patch is now ready to run. Reboot your system to use the
new TCP transport system.
TCPIP will look for the NET.CFG file in the root of your boot
drive.
You will still need to set the LANWP environment variable to
point to your LWP installation. (default: LANWP=C:\LANWP).
This lets your LWP applications find the HOSTS file, or
RESOLV.CFG.
Self-Extracting File Name: lo30t1.exe
Files Included Size Date Time
..\
LO30T1.TXT (This file)
NOVASYNC.EXE 4960 10-19-94 9:35:22 am
PTCPIP.OS2 2226 11-2-94 2:53:56 pm
SKTDRV.OS2 11131 11-2-94 3:52:16 pm
TCPIP.OS2 59144 11-2-94 10:53:14 am
VTCPIP.OS2 20536 11-2-94 2:53:10 pm
WINSOCK.DLL 35696 10-19-94 10:20:02 am
WLIBSOCK.DLL 46670 10-27-94 11:18:36 am
Installation Instructions:
See the installation instructions in Issue:
-----------------------------------------------------------------
Any trademarks referenced in this document are the property of
their
respective owners. Consult your product manuals for complete
trademark
information.
-----------------------------------------------------------------