home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
us8210b1.dsk
/
WR08210.INF
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1996-05-09
|
42KB
|
1,151 lines
ΓòÉΓòÉΓòÉ 1. Introduction ΓòÉΓòÉΓòÉ
IBM MPTS LAN Adapter and Protocol Support ServicePak WR08210
IBM PTF WR08210.
This package is a refresh of the MPTS LAN Adapter and Protocol Support (MPTS)
program and is intended to replace (upgrade) only LICENSED instances of MPTS.
As such, its use is limited to the license agreement under which you obtained
the original licensed copy.
The versions which are suitable for replacement are:
Version Product in which MPTS was included
LAPS V2.60.5 WARP Connect
LAPS V2.60.6 CM/2 2.0
LAPS V2.60.7 WARP CONNECT FIXPAK WR08152
LAPS V5.00.0 WARP Server
Title to the contents herein and any copies made is retained by the
International Business Machines Corporation, Armonk, New York, 10504.
CAUTION:
If TCP/IP 3.0 is installed on the system to be updated with this ServicePak,
TCP/IP 3.0 must also be upgraded to the TCP/IP FixPak UN00067 level in order
for TCP/IP, SLIP and PPP to function properly. (TCP/IP 3.1 does not need an
upgrade to be compatible with this updated MPTS.)
Warning: - Installation of this ServicePak is for English versions only (US
and UK.) Installing this MPTS ServicePak on other language versions of OS/2 is
not supported.
This package includes the separately installable MPTS BonusPak containing MAC
drivers for OEM adapter cards, new applets, and an upgraded CID installation
utility. See the BONUSPAK.INF on the BonusPak diskette for additional
information about the BonusPak content and installation.
An updated publications diskette is also included as diskette 6 of this
package.
ΓòÉΓòÉΓòÉ 1.1. Affected SYSLEVEL Files ΓòÉΓòÉΓòÉ
After installation of this ServicePak, the Current CSD level of the following
SYSLEVEL files will indicate WRx8210 (where x is the country code):
SYSLEVEL.TRP IBM OS/2 LAN Adapter and Protocol Support
SYSLEVEL.MPT IBM OS/2 LAN Server - Multi-Protocol Transport Services
ΓòÉΓòÉΓòÉ 1.2. Trademarks ΓòÉΓòÉΓòÉ
The following are trademarks of IBM Corporation:
o Communication Manager/2
o IBM
o LAN Support Program
o OS/2
o Operating System/2
o PC LAN Program
o Presentation Manager
o WARP Connect
o WARP Server
o Win-OS/2
The following are trademarks of other Corporations:
o ComPaq (ComPaq Computer Corporation)
o Extra! (Attachmate Corporation)
o Lotus 1-2-3 (Lotus Development Corporation)
o Lotus Notes (Lotus Development Corporation)
o Microsoft (Microsoft Corporation)
o Pentium (Intel Corporation)
o SmartStart (ComPaq Computer Corporation)
o Windows (Microsoft Corporation)
ΓòÉΓòÉΓòÉ 1.3. MPTS History ΓòÉΓòÉΓòÉ
The IBM Transports product has been under development for several years. It
was initially released for IBM's OS/2 Operating System as NTS/2. NTS/2
provided the transport device drivers for the NetBIOS protocol and a limited
number of hardware (MAC) adapters. NTS/2 was shipped with IBM products such as
Communications Manager, TCP/IP, and LAN Server/Requester Versions 2.0 and 3.0.
The NTS/2 product served as the code base for the Multi-Protocol Transport
Services (MPTS) product. MPTS was enhanced to include Sockets Support for
TCP/IP, NetBIOS over TCP/IP (TCPBEUI) protocol, and support for the NetBIOS
LM10 interface. As the number of IBM and OEM hardware adapters proliferated,
support for these were added. Multi-Protocol Transport Services was first
released with LAN Server 4.0 in 1994.
With the development of the IBM Warp Connect product, enhancements were made to
MPTS. This became MPTS Version 2.60.5 which was released with the IBM Warp
Connect product in 1995. TCP/IP Version 3.0 Base Kit Applications product,
also released in WARP Connect, requires MPTS Version 2.60.5.
Because MPTS Version 2.60.5 includes the TCP/IP stack, the TCP/IP Version 3.0
Base Kit Applications Product shipped with Warp Connect no longer includes the
stack and now is a prerequisite for MPTS Version 2.60.5.
With the development of IBM's Warp Server, MPTS was enhanced again to include
support for IBM's Dynamic IP Strategy, which includes support for Dynamic Host
Configuration Protocol (DHCP) and Dynamic Domain Name System (DDNS). In
addition, function was added for TCPBEUI to support 1000 sessions. This became
MPTS Version 5.0.
ΓòÉΓòÉΓòÉ 1.4. MPTS Diskette Organization ΓòÉΓòÉΓòÉ
The MPTS WRx8210 product now has six diskettes.
o MPTS Disk 1 - LAPS
o MPTS Disk 2 - MPTS Socket - TCP/IP Support Files
o MPTS Disk 3 - Transport Protocol Drivers and XPG/4 National Language Support
o MPTS Disk 4 - MAC Adapter Drivers
o MPTS Disk 5 - Utilities
o MPTS Disk 6 - PUBS and Symbol Tables for Debug
ΓòÉΓòÉΓòÉ 2. Installation ΓòÉΓòÉΓòÉ
This version of MPTS is installed using the MPTS Program Product Installation
Aid, MPTS.EXE The installation uses XCOPY to copy the files from diskette into
the appropriate subdirectories and then uses PKUNZIP2 to unzip the files. There
is NO selective install of MPTS sub-components. All components of MPTS are
installed, including all of the MAC drivers. Please refer to the MPTS
Configuration Guide on diskette 6 for complete Installation and Configuration
details.. Sample files for unattended or redirected installation are included
on Diskette #5 in the SAMPLE directory.
Use the following procedure for manual (diskette based) installation.
o Ensure that adequate disk space is available for MPTS install. MPTS Warp
Server/WRx8210 versions require 11.5 mb of disk space for both new
installations and re-installations of MPTS.
o With the MPTS refresh diskette (ServicePak Diskette #1) in drive A:, run MPTS
by entering "A:\MPTS", and follow the prompts.
o Shut Down and Reboot the system.
ΓòÉΓòÉΓòÉ 2.1. Installing Additional Network Drivers ΓòÉΓòÉΓòÉ
Additional network drivers may be found on other media. When the LAPS diskette
(Diskette 1) cannot hold all the network drivers, they are placed in separate
directories on another diskette. See the MPTS Configuration Guide on diskette 6
of this ServicePak for details on installing additional network drivers. A
list of supported network drivers can be found in:
o the Supported Network Adapters section of the MPTS Configuration Guide, or
o the \IBMCOM\MACS\READMAC.TXT file on the MACS.ZIP file on diskette 4 of this
ServicePak, or
o the World Wide Web at
http://www.europe.ibm.com/getdoc/psmemea/progserv/device/networka.html
ΓòÉΓòÉΓòÉ 2.2. Upgrading RIPL Servers ΓòÉΓòÉΓòÉ
MPTS does not install Transport Services to the \IBMLAN\RPL\IBMCOM directory.
To service the RIPL tree:
1. XCOPY the entire tree structure of the Server's IBMCOM directory to the
IBMCOM directory used for Remote IPL.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Example ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé
Γöé XCOPY /S C:\IBMCOM\*.* D:\IBMLAN\RPL\IBMCOM Γöé
Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
2. Run GETRPL to update Access Control Profiles, etc. This requires that the
RIPL server be started and that a LAN administrator be logged on.
ΓòÉΓòÉΓòÉ 3. MPTS Enhancements ΓòÉΓòÉΓòÉ
The sections that follow describe enhancements that have been incorporated into
MPTS by release.
ΓòÉΓòÉΓòÉ 3.1. Enhancements for the Warp Connect Product ΓòÉΓòÉΓòÉ
The following enhancements were incorporated into MPTS to support the Warp
Connect product:
o Functional enhancments to the TCP/IP stack
o THINLAPS.EXE enhancement to allow use of MAC drivers that are not packaged
with MPTS
o Support to add/update the hostname statement in the CONFIG.SYS using a CID
response file
o The ability to update the NETBIOS section in the protocol.ini file via the
CID response file
o NetWare NetBIOS Emulation over IPX Support
o Additional MAC Driver Support:
- IBM FDDI-FI Adapter Device Driver
- IBM wIReless LAN Network Adapter for workstation
- IBM wIReless LAN ISA Adapter
- IBM wIReless LAN MCA Adapter
- IBM wIReless LAN PCMCIA Adapter
- Madge Smart 100 Ringnodes
- Madge Smart Ringnodes for OS/2 2.x
- Madge Smart Ringnodes for OS/2 1.3
- IBM Parallel Port
Note: More Adapter Support information can be found in the
\IBMCOM\MACS\READMAC.TXT file in MACS.ZIP on diskette 4 of this
ServicePak and on the World Wide Web at
http://www.europe.ibm.com/getdoc/psmemea/progserv/device/networka.html
ΓòÉΓòÉΓòÉ 3.2. Enhancements for the Warp Server Product ΓòÉΓòÉΓòÉ
The following enhancements were incorporated into MPTS to support the Warp
Server product:
o The MPTS icon is now placed in the OS/2 System Setup folder and is identified
as "Adapters and Protocol Services."
o 1000 Session Support of NetBIOS over TCP/IP (TCPBEUI)
NetBIOS over TCP/IP for OS/2 supports up to 1000 sessions over one physical
LAN adapter card.
o Dynamic Host Configuration Protocol (DHCP) Support
DHCP services allows the user workstation to work in conjunction with a DHCP
server to dynamically generate Internet Protocol information for TCP/IP
communication.
o Dynamic Domain Name System (DDNS) Support
DDNS support provides the ability to dynamically update a Domain Name Server
that has been properly configured for DDNS support with Internet Protocol and
Hostname information.
o XPG/4 Support
MPTS provides the main XPG/4 support for Warp Server. It provides all the
necessary NLS LOCALE DLLs for Warp Server.
o Additional MAC Driver Support:
- SMC EtherCard PLUS (8003EB)
- SMC EtherCard PLUS/A (8003E/A)
- SMC EtherCard PLUS Elite (8003EP)
- SMC EtherCard PLUS Elite 10T (8003WC)
- SMC EtherCard PLUS Elite 16T (8013WC)
- SMC EtherCard PLUS Elite 16 (8013EPC)
- SMC EtherCard PLUS Elite 16 Combo (8013EWC)
- SMC EtherCard PLUS Elite/A (8013EP/A)
- SMC EtherCard PLUS Elite 10 T/A (8013WP/A)
- SMC EtherCard Elite 16 Ultra (8216)
- SMC EtherCard Elite 16C Ultra (8216C)
- SMC EtherCard Elite 16T Ultra (8216T)
- SMC EtherEZ 10BASE-T ISA (8416T)
- SMC EtherCard Elite32C Ultra (82M32C)
- SMC TokenCard Elite (8115T)
- SMC TokenCard Elite/A (8115T/A)
- SMC TokenCard Elite Master 32 (83M32)
- IBM Infrared NDIS MAC Driver for the ThinkPad 755 (built-in infarred
ports)
- Kingston TokenRx MC 16/4 Token-Ring (new NIF file only)
- Kingston TokenRx ISA 16/4 Token-Ring (new NIF file only)
- Olicom USA, Inc. EISA/32 Adapter (OC-3135)
- SSW Parallel Port NIC-less Adapter Driver
The SMC8000.OS2 driver replaces the MACWD.OS2 driver. The SMC8000.OS2
driver continues to support old SMC cards and adds supports for the new
SMC cards through EtherEz.
Note: More Adapter Support information can be found in the
\IBMCOM\MACS\READMAC.TXT file in MACS.ZIP on diskette 4 of this
ServicePak and on the World Wide Web at
http://www.europe.ibm.com/getdoc/psmemea/progserv/device/networka.html
o The old Parallel Port driver (PRNANDIS.OS2) has been replaced with the SSW
Parallel Port NIC-less Adapter driver (PMAC.OS2). Performance is a lot
better than with the old Parallel Port driver.
o MAC driver date and time stamp fix. All the MAC drivers were level-set with
the date and time stamp set to 6/1/95. Now whenever a newer version of the
MAC driver is delivered, it is stamped with the date and the time that it was
officially built.
o WarpSRV.ZIP - MPTS provides a sample of CID response files and a default LCU
command file in order to CID install all of the products in Warp
Server/WRx8210. The LCU command file is modeled after the Warp Server local
installation and uses the same procedures that the local Warp Server
installation uses. The sample LCU command file was created in order to
install the various Warp Server products directly off the Warp Server CD-ROM.
However, with minor modifications, it can be used to install the various
products from a hard disk as well.
o Adapter Detection Enhancements:
- Detection of most SMC Ethernet and Token-Ring adapter cards
- Detect IRQs of all SMC adapter cards that are detected
- Detection of IBM Token Ring 4/16 ISA adapter
- Detection of D-link De-320CT EtherSmart coax/10baseT card
o A /TC command line option has been added for the convenience of the TCP/IP
install program.
This option prevents the configuration of TCP/IP information using MPTS
during the install process when it is executed through the TCP/IP product
install.
o MPTS now provides the ability to modify or update parameter values in the
MPTCONFG.INI file using the CID Response file
o New and Enhanced Applets:
- New Applets
-- XTRACE
-- NB64K
-- NETTRACE
-- HOSTID
- Enhanced Applets
-- OS2SNIFF
-- DTF5 (enhancement of DTF4)
Note: LAPSDUMP - Due to a bug fix, the LAPSDUMP Applet that ships with the
Warp Server product will only work with the NETBEUI.OS2 that is
shipped with Warp Server. It is not backward compatible.
See the MPTS Configuration Guide on diskette 6 of this ServicePak for more
information on the MPTS Applets.
ΓòÉΓòÉΓòÉ 3.3. WRx8210 ΓòÉΓòÉΓòÉ
The follwing enhancements were incorporated into WRx8210 MPTS.
o NetBIOS over TCP/IP supports P-Node and H-Node RFC 1001.
NetBIOS over TCP/IP protocol stack is IBM's OS/2 RFC 1001/1002 B-Node
protocol stack. The NetBIOS over TCP/IP protocol stack in MPTS CSD WRx8210
implements the P-Node and H-Node mode of operation. RFC 1001 P-Node and
H-Node mode of operation rely on and require two NetBIOS support servers:
NetBIOS Name Server (NBNS) and NetBIOS Datagram Distributor Server (NBDD). P
and H nodes use the NBNS to resolve NetBIOS Names into IP addresses. P and H
nodes use the NBDD to distribute datagrams to NetBIOS group name members.
Packets are sent point to point between network nodes and these support
servers. In a P-Node network, all broadcasting is eliminated (except arp
packets). Likewise in a H-Node network, broadcasting is used as a last
resort. Packets will flow point to point unless all support servers go
off-line. An H-Node will then continue to operate (in a limited fashion) by
using broadcasting to resolve NetBIOS names.
NetBIOS over TCP/IP also:
- supports the configuration of multiple adapters over the same LAN segment
- switches automatically from SLIP to LAN connections without re-booting
- redial SLIP and PPP servers without re-booting system.
o Additional MAC Driver Support:
- IBM NULL MAC Driver (to support systems that do not have a LAN Adapter
Card)
- IBM EtherJet ISA Ethernet Adapter
- 3Com EtherLink III PC Card OS/2
- 3Com EtherLink III LAN+Modem PC Card for OS2 v1.5 - Card Services
- 3Com TokenLink III PC Card Adapter - OS/2
Updates for various other MAC drivers including the IBM Token-Ring Network
Adapter (IBMTOK.OS2) to version 3.1. This version of the IBM Token-Ring
device driver is now known as the IBM T-R Shared RAM Family (UP/SMP,
IBMTOK.OS2) and supports SMP systems.
Note: More Adapter Support information can be found in the
\IBMCOM\MACS\READMAC.TXT file in MACS.ZIP on diskette 4 of this
ServicePak and on the World Wide Web at
http://www.europe.ibm.com/getdoc/psmemea/progserv/device/networka.html
ΓòÉΓòÉΓòÉ 4. MPTS and Compatibility with TCP/IP ΓòÉΓòÉΓòÉ
This section discusses topics related to TCP/IP as implemented by MPTS. These
topics include:
o MPTS TCP/IP Support
o TCP/IP Configuration
o The ETC Environment Variable
o Attended TCP/IP Configuration
o The MPTCONFG.INI File
o The SETUP.CMD File
o The MPTSTART.CMD File
o DHCP and DDNS Support (Warp Server)
ΓòÉΓòÉΓòÉ 4.1. MPTS TCP/IP Support ΓòÉΓòÉΓòÉ
MPTS provides support for the TCP/IP protocol for use by application programs
written to use TCP/IP. MPTS supplies the TCP/IP protocol stack (device
drivers).
Note: Sockets Support allows application programs written using the Sockets
APIs along with the Socket DLL (supplied with the toolkit on MPTS
diskette 5) to perform Inter Process Communication with other
processes.
ΓòÉΓòÉΓòÉ 4.2. TCP/IP Configuration ΓòÉΓòÉΓòÉ
This section discusses topics dealing with TCP/IP configuration through MPTS.
The following topics are covered:
o Configuring IP Information
o Slip or Point to Point Protocol
o LAN Adapter Network Access
o How MPTS Determines if an IBM TCP/IP Product is Installed
ΓòÉΓòÉΓòÉ 4.2.1. Configuring IP Information ΓòÉΓòÉΓòÉ
The method for configuring IP information depends on the products that are
installed and whether the user has bound the protocol to an adapter (selected
the TCP/IP protocol under LAPS).
The user can use either of the following access methods:
o Serial Line Internet Protocol (SLIP) or Point to Point Protocol (PPP)
o LAN Adapter Network Access
ΓòÉΓòÉΓòÉ 4.2.2. Slip or Point to Point Protocol ΓòÉΓòÉΓòÉ
If users want, they can use TCP/IP in a SLIP ONLY or Point to Point Protocol
(PPP) environment. In this situation, users do not need to bind the TCP/IP
protocol to an adapter because they will be using Serial I/O or a modem for
access. IBM product installation software (such as Dialer and others)
configures the device statements in the CONFIG.SYS file. If this does not
occur, users can enter the MPTS program, select Configure, and then close or
end the MPTS program. During this process, users will be asked if they want
to update the CONFIG.SYS file and they should answer "yes". This will
configure the minimum number of TCP/IP stack device statements in the
CONFIG.SYS file. Users can then use the dialer application to access TCP/IP.
ΓòÉΓòÉΓòÉ 4.2.3. LAN Adapter Network Access ΓòÉΓòÉΓòÉ
If users want to use TCP/IP to access another workstation on the network
attached to it, they must bind the TCP/IP protocol to an adapter using the LAPS
panel in MPTS. They must also configure the IP information for the
workstation.
After the TCP/IP protocol is bound to an adapter in the LAPS panel, users
return to the previous Configure panel to configure the IP information. Users
should select one of the following, depending the version of MPTS that is
installed on the machine:
TCP/IP Socket Access - Warp Connect
TCP/IP Configuration - Warp Server/WRx8210
Under the Warp Connect version of MPTS, the status indicated either not
configured, configured, or must configure (when TCPBEUI protocol has been
selected in LAPS). Under the Warp Server/WRx8210 version of MPTS, the status
may also be Use TCP/IP Product Configuration Notebook.
If the system does not have an IBM TCP/IP product installed, when the user
selects the Configure button, a series of panels allows the user to enter IP
configuration information (for example, IP address, routing, domain name, name
server address, and so on). If the user does have an IBM TCP/IP product
installed (except for the IBM TCP/IP V 2.0 Applications Kit) the following
occurs, depending on the version of MPTS that is installed:
o Warp Connect
- The status changes to configured.
o Warp Server/WRx8210
- This option is unavailable. Both the radio button and the Configure
button are not selectable. The status indicates that the TCP/IP product
configuration function should be used to configure IP information.
ΓòÉΓòÉΓòÉ 4.3. The ETC Environment Variable ΓòÉΓòÉΓòÉ
The ETC environment variable is used by MPTS during both installation and the
configuration process. It is also used by the TCP/IP kits during installation
and configuration. Depending on the order of installation (TCP/IP Application
Kits and MPTS), the ETC environment variable setting may have different
settings as follows:
o If MPTS is installed before TCP/IP products
SET ETC=<d>:\MPTN\ETC
o If TCP/IP products are installed before MPTS
SET ETC=<d>:\<TCP/IP Path>\ETC
ΓòÉΓòÉΓòÉ 4.4. Attended TCP/IP Configuration ΓòÉΓòÉΓòÉ
When configuring MPTS, there are three sockets access flags that are set. These
flags are used to control the creation and content of files, and the placement
of statements in the CONFIG.SYS file. These flags are stored in the
MPTCONFG.INI file in the MPTN\BIN directory. Each of these flags has a YES and
NO setting:
o Local_lPC = YES default = NO
- The Local IPC flag is used to configure the appropriate device driver in
the CONFIG.SYS file. Local IPC access permits applications that are
written using the Sockets APIs to perform Interprocess Communication with
other processes on the same workstation.
- This flag is always set to YES when performing configuration through MPTS
directly.
- This flag is set to NO when configuring through the LAN products (LAN
Requester, LAN Server, or Peer). This configuration uses the MPTS
provided IBMLXCFG.DLL.
This flag adds the following statement to the CONFIG.SYS file for Warp
Connect and Warp Server/WRx8210:
DEVICE=<d>:\MPTN\PROTOCOL\AFOS2.SYS
o Inet_Access = YES default=NO
- Inet Access permits application programs written using the TCP/IP Socket
APIs to communicate with other Socket applications over the LAN.
- The Inet Access flag is used to configure the following TCP/IP device
driver statements in the CONFIG.SYS file for WARP Connect and WARP
Server/WRx8210:
Note: When the TCP/IP Base product is on the system, this information
must be entered through the TCP/IP configuration notebook utility
provided with the TCP/IP product.
DEVICE=<d>:\MPTN\PROTOCOL\SOCKETS.SYS
DEVICE=<d>:\MPTN\PROTOCOL\AFINET.SYS
DEVICE=<d>:\MPTN\PROTOCOL\IFNDIS.SYS
RUN=<d>:\MPTN\BIN\CNTRL.EXE
CALL=<d>:\OS2\CMD.EXE /Q /C<d>:MPTN\BIN\MPTSTART.CMD
SET ETC=<d>:\MPTN\ETC
/Q NO ECHO function to start the secondary
command processor from an existing
CMD.EXE
/C Passes a command to CMD.EXE and automatically
returns to the previous command process after the
command is completed.
Note: The SET ETC statement is added only if it is not already present
in the CONFIG.SYS file.
- It also triggers the creation of the SETUP.CMD file in the \MPTN\BIN
directory.
- This flag is set differently depending on the version of MPTS that is
installed.
Warp Connect When configuring through MPTS, this flag is set when the
TCP/IP socket access option is configured. When using the LAN
product integrated configuration, this flag is set to YES
automatically.
This flag is not required if the user is using SLIP, or Point to
Point Protocol support.
Warp Server/WRx8210 This flag is set to YES when the TCP/IP protocol is
selected in LAPS.
o NetBIOS_Access = YES default = NO
- NetBIOS Sockets Access allows application programs written using Socket
APIs to communicate with other NetBIOS applications over the LAN.
- When this flag is set to YES, the following statement is added to the
CONFIG.SYS file for Warp Connect and Warp Server/WRx8210 :
DEVICE=<d>:\MPTN\PROTOCOL\AFNB.SYS
- It also triggers the creating of the NBSETUP.CMD file in the \MPTN\BIN
directory. For more information, see the NBSETUP.CMD file.
ΓòÉΓòÉΓòÉ 4.5. The MPTCONFG.INI File ΓòÉΓòÉΓòÉ
This file is used by MPTS for the TCP/IP and NetBIOS sockets configuration
process. It stores Sockets Control Flag settings. When the TCP/IP base
product is not on the system, the TCP/IP configuration and routing parameters
are stored here.
The file format is:
[CONTROL]
Local_IPC = YES
INET_Access = YES
NETBIOS_Access = YES
[IFCONFIG]
Interface = 0,,,
Address = 129.35.71.65,,,
Brdcast = ,,,
Dest = ,,,
Enable = UP,DOWN,,
Netmask = 255.255.240.0,,,
Metric = 0,,,
Mtu = 1500,,,
Trailers = NO ,,,
Arp = NO ,,,
Bridge = NO ,,,
Snap = NO ,,,
Allrs = NO ,,,
802.3 = NO ,,,
Icmpred = NO ,,,
Canonical = NO ,,,
EnableDhcp = NO ,YES,, ***
[DHCP] ***
Adapter = 1 ***
ClientID = MAC ***
DDNS = YES ***
NumLogFiles = 0 ***
LogFileSize = 0 ***
LogFileName = ***
SYSERR = NO ***
OBJERR = NO ***
PROTERR = NO ***
WARNING = NO ***
EVENT = NO ***
ACTION = NO ***
INFO = NO ***
ACNTING = NO ***
TRACE = NO ***
[NETBIOS] ***
SESSIONS = 50 ***
NCBS = 80 ***
NAMES = 21 ***
HOSTNAME = YANKEE ***
[ROUTE]
Type = default
Action = add
Dest =
Router = 129.35.64.1
Metric = 1
Note: *** Available in Warp Server/WRx8210 MPTS only.
ΓòÉΓòÉΓòÉ 4.6. The SETUP.CMD File ΓòÉΓòÉΓòÉ
This file is created through MPTS during configuration if the TCP/IP base
product is not on the system.
Note: If the TCP/IP base product is on the system, the SETUP.CMD file is
created by the TCP/IP Configuration Notebook utility. MPTS does not
allow you to configure these parameters.
This file is stored in the MPTN\BIN directory.
The following examples illustrate the SETUP.CMD file that is created by MPTS:
The first example shows a SETUP.CMD file for an adapter that was configured
with TCP/IP IP information:
route -fh
arp -f
ifconfig lan0 129.35.71.65 129.35.74.64 netmask 255.255.240.0 metric 0 mtu 1500
route add default 129.35.64.1 1
route add net 129.35 129.35.64.1 1
The second example shows a SETUP.CMD file for an adapter that was configured
for DHCP:
route -fh
arp -f
DHCPSTRT -i lan0
ΓòÉΓòÉΓòÉ 4.7. The MPTSTART.CMD File ΓòÉΓòÉΓòÉ
The MPTSTART.CMD file provides the initial TCP/IP startup during the boot
phase. It executes the SETUP.CMD file and the NBSETUP.CMD files if they are in
the MPTN\BIN directory. The following examples illustrate the file formats for
the Warp Connect and Warp Server/WRx8210 products.
o File Format for Warp Connect product:
@ECHO OFF
IF NOT EXIST <d>:\MPTN\BIN\SETUP.CMD GOTO END
INETWAIT
CALL <d>:\MPTN\BIN\SETUP.CMD
:END
o File Format for Warp Server/WRx8210 product:
@ECHO OFF
IF NOT EXIST C:\MPTN\BIN\SETUP.CMD GOTO NBSETUP
INETWAIT 1>NUL
CALL C:\MPTN\BIN\SETUP.CMD
:NBSETUP
IF NOT EXIST C:\MPTN\BIN\NBSETUP.CMD GOTO END
CALL C:\MPTN\BIN\NBSETUP.CMD
:END
ΓòÉΓòÉΓòÉ 5. DHCP and DDNS Support (Warp Server/WRx8210) ΓòÉΓòÉΓòÉ
DHCP stands for Dynamic Host Configuration Protocol. It is one of the two
components of the IBM strategy known as Dynamic IP. The second component of
Dynamic IP is DDNS or Dynamic Domain Name System. The Dynamic IP strategy was
developed to reduce the burden on LAN Administrators with respect to the
administration of Internet addresses.
DHCP has been around for a while and is defined in the appropriate Requests For
Comments (RFCs) of the International Standards Organization (ISO). DDNS is not
currently defined by any approved ISO RFC. DHCP and DDNS support is being
provided for the first time in the Warp Server version of MPTS.
When DHCP support is enabled and used with a properly configured DHCP server,
the workstation can request an IP address from the server. The server can
provide an address from its pool to the workstation for communication.
However, because most people communicate with each other using host names that
are mapped to the IP addresses and kept in the Domain Name Server, the Domain
Name server must be updated. This support is provided by the DDNS component.
When DDNS support is configured on the workstation and is used in conjunction
with a properly configured DDNS server, the Domain Name Server is updated with
the current IP address.
For additional information and a discussion of DHCP and DDNS, refer to OS/2
Warp DHCP System Administration.
ΓòÉΓòÉΓòÉ 5.1. Configuring DHCP and DDNS Support ΓòÉΓòÉΓòÉ
Configuring DHCP and DDNS support depends on whether the TCP/IP Base Kit is
installed on the system and the version that is installed.
If there is no TCP/IP Base Kit installed on the system, configuration is
accomplished through MPTS as follows:
1. Configure the TCP/IP protocol for an adapter through the LAPS panel.
2. Select TCP/IP configuration on the Configure panel.
3. Enable the physical adapter that had TCP/IP protocol assigned to it under
the LAPS panel.
4. Check the DHCP Support box on the panel. This causes the remainder of the
panel to be hidden and a box for DDNS Support to display.
5. Check the Use DDNS box if a properly configured DDNS server is available.
It should be emphasized here that in order to use DHCP and DDNS support, you
must have installed and properly configured a DHCP Server and a DDNS Server
(only required if you intend to use DDNS). These products are supplied with the
IBM Warp Server product.
If there is a TCP/IP Base Kit installed on the system, the Configure TCP/IP
option will not be available on the Configure panel. Configuration of DHCP and
DDNS has to be done using the TCP/IP Configuration Notebook utility.
Note: This feature is available only if TCP/IP V 3.1 is installed. This is
the version supplied with the Warp Server product.
ΓòÉΓòÉΓòÉ 5.2. National Language Support (NLS) XPG/4 for DHCP ΓòÉΓòÉΓòÉ
The DHCP Monitor program, which is part of the DHCP component shipped with
MPTS, is NLS-enabled in compliance with the ISO XPG/4 standard. MPTS for the
Warp Server/WRx8210 product packages and installs the NLS files unique to each
NLS release.
ΓòÉΓòÉΓòÉ 5.3. Dynamic IP ΓòÉΓòÉΓòÉ
IBM TCP/IP for OS/2 Warp Server provides support for a new networking
technology called Dynamic IP. Dynamic IP allows you to define network host
configuration parameters at a central location and to automate configuration of
IP hosts. Therefore, it simplifies both IP network access and IP network
administration, and is well-suited for supporting mobile hosts.
Dynamic IP is the integration of the DHCP, which provides configuration
information to IP hosts, and the Dynamic DNS (DDNS), which provides dynamic
host name-to-IP address (and IP address-to-host name) mapping for the Dynamic
IP clients.
The design of Dynamic IP evolved from customer requirements for addressing the
challenges associated with network administration, particularly for large IP
networks.
o Because each host on an IP network is typically configured and maintained
individually, the task of implementing changes to the network infrastructure
or services requires a massive, coordinated effort to reconfigure all
affected hosts.
o Similarly, when a host attaches to a new location in a network, the network
administrator typically must assign a new IP address for the host as well as
manually change the host's host name-to-IP address mappings in the host's
authoritative DNS server.
o For mobile hosts, an IP address must be "reserved" for each and every
subnetwork location at which the mobile host may possibly attach.
Unfortunately, the end-user of the mobile host typically must manually
reconfigure the IP software with the IP address and other IP network
parameters appropriate to a given attachment location.
The goal of Dynamic IP is to simplify these tasks and to provide an easier way
to access and administer IP networks. And because Dynamic IP uses only
open-standard networking technologies, it is fully compatible and interoperable
with existing IP network hosts.
ΓòÉΓòÉΓòÉ 6. MPTS Configuration ΓòÉΓòÉΓòÉ
Documentation on the configuration of MPTS can be found in the MPTS
Configuration Guide (MPTSCFG.INF) located in the pubs.zip on diskette 6 of this
ServicePak.
ΓòÉΓòÉΓòÉ 7. MPTS CID Response Files ΓòÉΓòÉΓòÉ
MPTS response files are used to configure MPTS through CID. The configuration
involves mostly the PROTOCOL.INI and MPTCONFG.INI files. Response files
contain various sections. If a section is specified more than once, the last
occurrence is used. An MPTS response file may contain the following sections:
o Install (inst_section)
o Protocol module (prot_section)
o Protocol (protocol)
o Socket/MPTS (mpts)
o Names list (rfcnames)
o Broadcast list (rfcbcst)
o TCP/IP Resolv (resolv)
o Netbios (prot_netbios )
o Hostname (hostname - set hostname in config.sys)
See the MPTS Configuration Guide for a detailed description of the response
files. Only the Socket/MPTS section is described in this document.
ΓòÉΓòÉΓòÉ 7.1. Response File Socket/MPTS Section ΓòÉΓòÉΓòÉ
The MPTS section of the CID Response file contains information that is stored
in the MPTCONFG.INI file in the MPTN\BIN directory. The information in this
file is used to configure TCP/IP, the DHCP CLIENT, and NETBIOS Sockets support.
Prior to the Warp Server product, this section in the response file was a
replacement section only. That is, it would not modify an existing
MPTCONFG.INI file, but would overwrite the file with the new information. Since
the release of the Warp Server product, there are several features that permit
the user to modify an existing MPTCONFIG.INI file using a CID Response file.
Refer to the MPTS Configuration Guide for information on these features.
The following example illustrates an MPTS section that creates a new (or
overwrites an old) MPTCONFG.INI file. It also discusses the configuration
control flags.
*****************************************************
* *
* A SAMPLE MPTCONFG.INI FILE *
* *
*****************************************************
**** MPTS response file is replacement only, not a modification. *****
**** This applies even if TCPIP is currently on the system. *****
MPTS = (
[CONTROL]
LOCAL_IPC = YES ; This flag triggers the addition of the afos2.sys
; device statement to the CONFIG.SYS file. This function
; permits an application to use sockets APIs to
; perform Inter-Process Communication on the LOCAL
; system. This flag is set automatically when doing
; an attended configuration (not CID). During a CID
; Install/Configuration, this flag is set using the
; MPTS section of the response file.
; Warp Connect set this flag unconditionally.
; ** MPTS response file is replacement only, not
; a modification.
INET_Access = YES ; This function permits an application to use Sockets
; APIs to perform Inter-Process Communication
; using the TCP/IP protocol.
;
; This flag triggers the following actions:
; 1. Addition of the following statements to
; the CONFIG.SYS file:
; A. SOCKETS.SYS
; B. AFINET.SYS
; C: IFNDIS.SYS
; D. CNTRL.EXE
; E. MPTSTART.CMD call
; F. SET ETC= if not currently in the CONFIG.SYS file.
; 2. Creation of the SETUP.CMD file if the TCP/IP
; base product is not on the system. Note: If
; the TCP/IP base product is on the system, the
; SETUP.CMD file from the base product is used.
; The SETUP.CMD file is placed in the MPTN\BIN
; subdirectory. If the TCP/IP v2.0 base product
; is present on the system, it will be copied
; from the <TCPIPPath>\BIN subdirectory to the
; MPTN\BIN directory during configuration.
; In the case where the TCP/IP base product is on
; the system. the SETUP.CMD file MUST be changed
; using the TCP/IP Configuration Notebook.
; During configuration in a product OS/2 environment,
; MPTS determines if the TCP/IP base product is on
; the system by searching the path for the TN3270.EXE
; (it is in the <TCPIPPath>\BIN directory) and
; CNBSTK.DLL (in the <TCPIPPath\DLL directory).
; A search is also made for the SYSLEVEL.IAK (TCP/IP
; Internet Access Kit) and the SYSLEVEL.APP (TCP/IP
; V 2.0 Applications Kit).
NETBIOS_Access = NO ; This function permits an application to use sockets APIs
; to perform Inter-Process Communication on the network using
; the NETBIOS protocol.
; This flag triggers the addition of the AFNBINI.EXE DEVICE
; statement to the CONFIG.SYS file.
*******************************************************************
* *
* The following information is used to create the SETUP.CMD file *
* if the TCP/IP base product is not on the system, otherwise *
* it is ignored by MPTS. *
* *
*******************************************************************
[IFCONFIG]
Interface = 0,,,
Address = 129.35.71.65,,,
Brdcast = ,,,
Dest = ,,,
Enable = UP,DOWN,,
Netmask = 255.255.240.0,,,
Metric = 0,,,
Mtu = 1500,,,
Trailers = NO ,,,
Arp = NO ,,,
Bridge = NO ,,,
Snap = NO ,,,
Allrs = NO ,,,
802.3 = NO ,,,
Icmpred = NO ,,,
Canonical = NO ,,,
EnableDhcp = NO ,YES,,
[DHCP] Note 1
Adapter = 1 Note 1
ClientID = MAC Note 1
DDNS = YES Note 1
NumLogFiles = 0 Note 1
LogFileSize = 0 Note 1
LogFileName = Note 1
SYSERR = NO Note 1
OBJERR = NO Note 1
PROTERR = NO Note 1
WARNING = NO Note 1
EVENT = NO Note 1
ACTION = NO Note 1
INFO = NO Note 1
ACNTING = NO Note 1
TRACE = NO Note 1
[NETBIOS] Note 1
SESSIONS = 50 Note 1
NCBS = 80 Note 1
NAMES = 21 Note 1
HOSTNAME = YANKEE Note 1
[ROUTE]
Type = default
Action = add
Dest =
Router = 129.35.64.1
Metric = 1
)
Note: These sections are new with the release of the Warp Server
product.
The MPTCONFG.INI file is made up of several sections (CONTROL, IFCONFIG, DHCP,
NETBIOS, and ROUTE). Depending on the configuration options selected under
MPTS, one or more of these sections may be present in the file after the
configuration process (using attended Presentation Manager) is complete. At a
minimum, the MPTCONFG.INI file always contains a CONTROL section.
The IFCONFIG section is created if the user chooses to configure TCP/IP
information and does NOT have the IBM TCP/IP Base Kit installed on the system.
The DHCP section is present if the user chooses to configure an adapter for
DHCP Support using MPTS and does NOT have the IBM TCP/IP Base Kit installed on
the system.
The NETBIOS section is created if the user configures NETBIOS Sockets Access.
The ROUTE section is created if the user configures Routing information while
configuring TCP/IP information using MPTS and does NOT have the IBM TCP/IP Base
Kit installed on the system.
ΓòÉΓòÉΓòÉ 8. Things that Changed ΓòÉΓòÉΓòÉ
The following sections describe changes that have been made to the product's
executables, and messages/helps.
ΓòÉΓòÉΓòÉ 8.1. MPTS Version WR08210 ΓòÉΓòÉΓòÉ
The following APARS are included in WR08210.
o APAR IC09186 NETBIOS.OS2 DOES NOT LOCK THE USERS DATA SEGMENT, CAUSING A TRAP
D IF THE SEGMENT IS SWAPPED OUT BEFORE NCB COMPLETION.
o APAR IC11290 SRVATTCH INTERMITTENTLY FAILS WITH XI10066 RC=59.
o APAR IC11751 ADDING STARGATE PORTS TO WARPCONNECT MPTS CAUSES DRIVERNAME=
PARM TO BE CORRUPTED (ONE ZERO IS DROPPED FROM THE DRIVER NAME).
o APAR IC12097 TRAP D IN NETBIOS.OS2 (WR08152).
o APAR IC12559 MPTS CRAY ETHENET ADAPTER PC04.OS2 NOT APPEARING CORRECTLY IN
PROTOCOL. INI.
ΓòÉΓòÉΓòÉ 8.2. TCP/IP Version 3.0 ServicePak and MPTN ServicePak ΓòÉΓòÉΓòÉ
The following APARS are included in TCP/IP ServicePak UNx0067 or MPTN
ServicePak WRx8210. A single asterisk indicates that the APAR is shipped with
the MPTN ServicePak WRx8210. A double asterisk indicates that some of the
files are in the TCP/IP CSD and some of the files are in the MPTN CSD.
o APAR IC10294 ** MPTSTART CALLING IFCONFIG BEFORE CNTRL COMPLETES RESULTING
IN TCP/IP NOT ACTIVATING.
o APAR IC10309 * IPGATE.EXE DOES NOT WORK ON WARP CONNECT AND TCP/IP V3.
o APAR IC10390 * GETHOSTNAME & GETHOSTID DON'T WORK ON SLIP CONNECTIONS.
o APAR IC10970 * TCP/IP 3.0: SEARCH COMMAND OF RESOLV2 DOESN'T LOOK FOR OTHER
DOMAIN.
o APAR IC11133 * ROUTED CAUSES UNCONTROLLED GROWTH OF THE SWAPPER.DAT FILE
CAUSING EVENTUAL SYSTEM LOCKUP.
o APAR IC11608 * SO_LINGER FUNCTION FROM THE PROGRAMMER'S TOOLKIT FOR TCP/IP ON
OS /2 2.0 AND 2.1 CAUSES WARP CONNECT TCP/IP WORKSTATION TO HANG.
o APAR IC11795 * NETSTAT -N REPORTS A VERY HIGH NUMBER OF PACKETS DROPPED FOR
8272 SWITCH.
o APAR IC11834 * OS/2 TCP/IP UPDATING ARP TABLE WITH SLOWEST PATH, WHEN ARP
REQUEST IS INITIATED BY OTHER MACHINES.
o APAR IC11892 * GETHOSTBYNAME() FAILS TO RETURN ADDRESS LIST.
o APAR IC12128 * AFTER APPLYING CSD8152, STARTING NETSCAPE 122 (OR BETA 200)
YIELDS A TRAP D.
o APAR IC12289 * HANG WHEN RUNNING WARP SERVER AND INTERNET CONNECTION SERVER
CAUSED BY ERROR IN SO32DLL.DLL MEMORY OPTION.
o APAR IC12347 DOCUMENTATION APAR CONCERNING PROT_SECTION WHEN DOING A CID
INSTALL OF MPTS AND USING IBMTCS$ INSTEAD OF IBMTOK$.
o APAR IC12446 * GETHOSTBYNAME SOCKET CALL DOES NOT FUNCTION AS NSLOOKUP.
o APAR IC12657 ** OS/2 TCP/IP V3.0 STACK, SLIP, PPP, HOSTID, ROUTED
CONSOLIDATED FIXES FOR WARP CONNECT CUSTOMERS.
o APAR IC12732 * COMMMGR PROBLEM WITH SELECT().
ΓòÉΓòÉΓòÉ 8.3. MPTS DHCP client ΓòÉΓòÉΓòÉ
The following APARS are included in WR08210.
o APAR IC12680 ADD SUPPORT FOR PREDEFINED DDNS.DAT.
o APAR IC12681 DHCPEXEC GIVES REXX ERROR "INCORRECT CALL TO FUNCTION".
ΓòÉΓòÉΓòÉ 9. Appendix ΓòÉΓòÉΓòÉ
Appendix of other interesting topics.
ΓòÉΓòÉΓòÉ 9.1. Printing Information from this On-line Document ΓòÉΓòÉΓòÉ
The OS/2 view function provides a print capability to the printer defined as
the "default" printer for your system. From the "Services" popup, selecting
print provides several options; Print All, Marked, or This Section(s),
Contents, or Index.
All but the Print Marked Sections are fairly self explanatory. To Print
"Marked" sections one must first know how to "Mark". It is best to do this with
the contents window fully expanded, ie. every section shows up in the content
panel. Then simply press the space bar when the section you chose is
highlighted or point and click the left mouse button while also holding the
ctrl key to "mark" a section for print.
The highlighting for "marked sections" is slightly larger than normal
highlighting. To notice the difference, select an item in the contents and
repeatedly press the space bar.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The item in the title line is a trademark of IBM Corporation
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The item in the title line is a trademark of Microsoft Corporation
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The item in the title line is a trademark of Wall Data Corporation
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The item in the title line is a trademark of Attachmate Corporation