(c) Copyright 1997 International Business Machines Corp. All rights reserved. IBM TCP/IP V4.2.1 Readme File Contents -------- 1. General Information 2. Operating Systems Supported 3. Approximate Disk Space Required 4. Prerequisite Software 5. Installation Instructions 6. Uninstall Instructions 7. Dynamic IP Changes 8. Known Problems, Restrictions, and Considerations 9. Service 10. Trademarks ------------------------------------------------------- 1. General Information The IBM TCP/IP V4.2.1 for OS/2 software product (TCP/IP V4.2.1) is now available. The TCP/IP Programmer's Toolkit has been updated to support TCP/IP V4.2.1. It is available on the IBM Developer Connection, Release 2 Volume 2. ------------------------------------------------------- 2. Operating Systems Supported TCP/IP V4.2.1 can be installed on these operating systems: o OS/2 Warp 4 o OS/2 Warp Server o OS/2 Warp Server SMP You should use a computer with a Pentium processor and at least 32MB memory (16MB per processor with SMP). ------------------------------------------------------- 3. Approximate Disk Space Required MPTS Warp 4 Warp Svr Previous release . . . . . . . . 4MB 3MB Increase from previous release . 8MB 8MB Total . . . . . . . . . . . . . . 12MB 11MB TCP/IP Warp 4 Warp Svr Previous release . . . . . . . . 34MB 20MB Increase from previous release . -1MB 28MB Total . . . . . . . . . . . . . . 33MB 48MB Temporary space used during MPTS and TCP/IP installation tcp41.zip . . . . . . . . . . . . 29MB Expansion of tcp41.zip . . . . . 51MB Prerequisite program disk space: Netscape Communicator 4.04 Expansion of comm404.exe 8MB Installed 10MB Java for OS/2 v1.1.6: Expansion of javainrt.zip 14MB Runtime installed 23MB OS/2 Feature Install Version 1.2 Expansion of firunpkg.zip 6MB Notes: Numbers shown are approximate and may change. For current information, see the Java and Feature Install information on Software Choice. ------------------------------------------------------- 4. Prerequisite Software Before installing TCP/IP V4.2.1, this software must be installed on your computer: 1) A Generally Available version of one of the supported operating systems noted in Section 2. (Do not use a pre-release version of an operating system.) 2) These Software Choice packages, in this order: a) Netscape Communicator 4.04 b) OS/2 Feature Install Version 1.2 c) Java for OS/2 v1.1.6 (you only need the Java 1.1.6. Runtime) d) MPTS 5.40 Note: For Netscape Communicator, Feature Install, Java and MPTS instructions, see Section 5. ------------------------------------------------------- 5. Installation Instructions (Note: For more information on CID installation, see the TCP/IP Guide.) a) Create a high level temporary directory called tempdirs. Go to the tempdirs directory and create the following temporary directories as necessary: - nstemp (Netscape Communicator) - fitemp (Feature Installer 1.2.2) - javatemp (Java 1.1.6) - mptstemp (MPTS 5.40) - tcptemp (TCP/IP 4.2.1) b) Copy x:\util\pkunzip2.exe to c:\ibmcom (where "x" is the letter of your CD-ROM drive). c) Copy x:\util\pkzip.exe to c:\ibmcom. d) Install Netscape Communicator 4.04 (if necessary): Go to the tempdirs\nstemp directory and enter the command 'x:\os2\ns\en\comm404' to execute the self-extracting file. Enter 'install'. After installation is complete, reboot the system. e) Install Feature Installer 1.2.2 (if necessary): Go to the tempdirs\fitemp directory and enter the command 'pkunzip2 -d x:\os2\fi\en\firunpkg.zip'. Enter 'fisetup'. After installation is complete, reboot the system. f) Install Java 1.1.6 RunTime (if necessary): Go to the tempdirs\javatemp directory and enter the command 'pkunzip2 -d x:\os2\java\en\javainrt.zip'. Enter 'install'. After installation is complete, reboot the system. NOTE: Java RunTime is the only REQUIRED java component for TCP/IP installation. You may choose to install the tool kit package (javaintk.zip) or the unicode font package (javainuf.zip) by using a similar pkunzip2 command. g) MPTS 5.40 (if necessary): Go to the tempdirs\mptstemp directory and enter the command 'pkunzip2 -d x:\os2\mpts\en\mpts540x.zip'. Enter 'install'. After the installation is complete, reboot the system. h) TCP/IP V4.2.1: Go to the tempdirs\tcptemp directory and enter the command 'pkzip /ext /dir x:\os2\tcpip\en\tcpapps.zip'. To upgrade over a previous version of TCP/IP without installing the new function in Secure Remote IP Client, enter 'install /a-'. When asked whether to install a more recent version of MPTS, click 'Yes'. Reboot the system after the installation completes. If you want to install Secure Remote IP Client, enter 'install' and continue with the following steps: 1) When asked whether to install a more recent version of MPTS, Click Yes. 2) Click OK on the Multi-Protocol Transport Services logo window, if necessary. 3) Click Install on the Multi-Protocol Transport Services window. 4) Click OK on the MPTS Target Drive window. Do not change the Target Drive letter. 5) If a Reinstall MPTS window appears, click OK. 6) When the Installation Complete window appears, click OK. Note: Do NOT click Configure on the Multi- Protocol Transport Services window. Your current MPTS configuration will not be changed. 7) When the Multi-Protocol Transport Services window appears, click Exit. 8) When the Update CONFIG.SYS window (that is, allow the installation program to update your CONFIG.SYS file), click Exit. 9) When the CONFIG.SYS Updated window appears, click OK. 10) When the Exiting MPTS window appears, click Exit. Note: Do NOT shut down or restart your computer now. Continue with the next step. 11) At the bottom of the TCP/IP V4.2.1 for OS/2 Installation window, click the Forward (right arrow) button. 12) On the Welcome to TCP/IP V4.2.1 for OS/2 Installation window, click Guided Path. 13) In the next TCP/IP V4.2.1 for OS/2 window, select any new components you wish to install. TCP/IP components that have been previously installed will be preselected. Leave them selected. 14) Click Forward. 15) Enter your Administrator Password in the Drive Selection for TCP/IP 4.2.1 for OS/2 window, if you plan to do any remote TCP/IP configuration or administration. (A utility shipped with TCP/IP V4.2.1, ADMIN_PW, may be used from the OS/2 command line to set or reset this password at a later time.) Your current TCP/IP path will also be displayed on this page. Do NOT change this path. 16) Click Forward. 17) Click the Install (diagonal arrow) button at the bottom of the Ready to Install TCP/IP 4.2.1 for OS/2 window. 18) Click the Exit (X) button at the bottom of the Installation Complete for TCP/IP V4.2.1 for OS/2 window. 19) Shut down and restart your computer. Messages for errors that occur during installation are recorded in these files: TCP/IP install log: :\os2\install\tcpinst.log Feature-Install install logs: :\os2\install\current.log :\os2\install\fisetup.log :\os2\install\wpinstal.log MPTS install log: :\os2\install\lapshist.log Locked-file log: :\os2\install\ibmlshst.log After installing TCP/IP V4.2.1 and verifying that the installation(s) completed successfully, you can delete the entire tempdirs directory structure. (Selecting Edit and then Delete for the tempdirs structure when viewed using Drives within the OS/2 System folder.) ------------------------------------------------------- 6. Uninstall Instructions If you install TCP/IP V4.2.1 once and then uninstall TCP/IP using the Remove TCP/IP Version V4.2.1 for OS/2 utility, your CONFIG.SYS file will be restored to its previous state and certain TCP/IP-related files will be removed. If you install TCP/IP V4.2.1 more than once, however, the Remove utility will behave differently. After removing TCP/IP V4.2.1 and restarting your computer, do these additional steps: 1) Click the Drives icon and open: C:\OS2\INSTALL\"Installed Features" 2) Click TCPINST - Inventory. 3) Click Uninstall, and then restart your computer. 4) Some file cleanup in the TCPIP subdirectory may be required. ------------------------------------------------------- 7. Dynamic IP Changes Please read this section carefully before using the new Dynamic IP (DHCP) programs and functions provided in this release. o New DHCP Server Configuration File Format: The DHCP Server (DHCPSD.EXE) configuration file (DHCPSD.CFG) format has changed. To allow greater flexibility in using and configuring your DHCP server, the "network" statement has been disallowed. To convert the DHCP server configuration file to the new format, do this: 1) Make a backup copy of DHCPSD.CFG (your server configuration file). 2) Do a or b: a) Use the configuration converter utility, OLD2NEW.EXE, to read your existing configuration file and convert it to the new format. OLD2NEW.EXE can be found in the tcpip\samples directory. Run OLD2NEW using your existing and new configuration file names and extensions: old2new b) Edit the DHCPSD.CFG file to remove any "network" statements and the braces, { }, which scope them. Any options remaining from the network statements now become global options. Options can be scoped under individual subnets. The subnet mask must be added to the subnet statement as the second parameter. 3) After doing a or b above, view the modified configuration file using the new DHCP Server Configuration Program. This will identify any errors in the configuration file. After converting the DHCPSD.CFG file to the new format, use the DHCP Server Configuration Program to make any future modifications to the server configuration. o The DHCP Server address and client database formats have changed. The first time you run the new DHCP server (DHCPSD.EXE) in TCP/IP V4.2.1, it will detect the existing address and client database files, back them up, and convert them to the new format. The original files DHCPS.AR and DHCPS.CR are backed up to DHCPS.ARB and DHCPS.CRB. The converted files cannot be used by DHCP server versions prior to TCP/IP V4.2.1. o If you are upgrading existing Dynamic IP servers to this new support and you have multiple servers (OS/2 or AIX) in your network, you should upgrade your primary Dynamic Domain Name Servers (primary DDNSs) first, followed by your DHCP servers and Secondary DNS servers. Previous versions of DDNS servers for OS/2 and AIX have some limitations: - DHCP servers using the new Protected proxyAREC support will not work with prior versions of DDNS Servers. - Clients using the new DHCP option 192 (labels) support will not work with back-level versions of DDNS Servers. Obtain the latest service level fix for the Warp 4 DDNS server from IBM Service to eliminate this restriction. o If a DDNS server will be configured using the DDNS Server Administrator, the TCP/IP host name of the server must be resolvable when DDNSAPS.CMD is started (usually during startup). To ensure resolution, add the server's hostname to the %ETC%\HOSTS file. The line should have this format: # IP Address Hostname.Domain_name Hostname 1.2.3.4 myhost.ibm.com myhost If a HOSTS file does not exist, you can create one which only contains a line similar to the above line. This is only necessary on DDNS Servers which will be configured with the DDNS Server Administrator. o For information on setting up the TCP/IP login file, see Configuring the Remote Login Page in the TCP/IP Guide. ------------------------------------------------------- 8. Known Problems, Restrictions, and Considerations Known problems, restrictions, and considerations with TCP/IP V4.2.1 include: Java Considerations: o There are several known problems in Java 1.1.1 that affect these TCP/IP V4.2.1 Java programs (particularly on OS/2 Warp Server): - TCP/IP Configuration Notebook Program - DDNS Server Administration Program - DHCP Server Configuration Program - DHCP Server Management Program - Create TCP/IP Administration Password Program o The TCP/IP V4.2.1 Java programs may run slowly, particularly on low-end computers. o TCP/IP V4.2.1 command files set the JAVA_COMPILER environment variable (SET JAVA_COMPILER=xxx) which turns off the JIT compiler. This improves the performance of the Java programs if your configuration contains a small amount of data. You may want to remove (comment out) this SET statement to get better performance if your configuration contains a lot of data. Note: If you see this message, when running TCP/IP Java applications with the JIT compiler turned off, you can ignore it: "Unable to load DLL 'xxx' (errcode = 'XXX')". o Occasional traps have been observed in various Java components. If a trap occurs, reboot your machine. Usually the traps cannot be recreated. o Scrolling with the mouse may result in a hung application. If this happens, press the Ctrl and Esc keys simultaneously to get a window that may let you end the application. You can avoid the problem by scrolling with the Page Up and Page Down keys or with the up arrow and down arrow keys. Using the slider bar always results in a hung application whenever the mouse pointer moves off the slider bar. Using the up and down arrows on the scroll bar sometimes results in a hung application. This problem is fixed in Java 1.1.3 and subsequent releases. o 16-color display may appear less than optimal. Select 256-colors or higher (if possible). Note: Higher screen resolution may use more storage. o To save on storage you may want to set the Java heap size to 2 MB (the default is 8 MB). To do this, change the command files in \tcpip\bin that run the JAVA programs (admin_pw.cmd, dadmgui.cmd, ddnsapc.cmd, ddnsaps.cmd, dhcpscpc.cmd, dhcpscps.cmd, tcpcfg2.cmd, tcpcfg2d.cmd, and tcpcfg2r.cmd). Add the -ms option after the Java keyword. For example: Java -ms2 o If you use HPFS386, setting the HPFS cache size smaller (for example, 2048) than the default in :\IBM386FS\HPFS386.INI can improve performance of the configuration notebook when a large amount of data is involved. o When running the TCP/IP Java configuration programs (for DDNS, DHCP and TCP/IP) remotely, if you are running on Windows 95, you may encounter an Out of Environment Space error while trying to start the program. If this happens, edit the properties for your MS-DOS prompt. On the Memory tab, increase the value for Initial environment. o If you try to run the Java configuration programs through the applet viewer on a machine which is low on memory, you may get this exception: JAVAI.DLL 0002:0001ECAD P1=00000001 P2=011A2800 EAX=011A2800 EBX=001B0004 ECX=0 EDX=FFFFCA00 ESI=8 EDI=0168CA68 Try freeing up more memory before restarting the program. Dynamic IP status: o If you experience a hang while scrolling, see the scrolling with a mouse description in the Java Considerations, above. o The DDNS on-line help file, DDNSBK1.INF, incorrectly states that the NSSIG -IOT command generates output to the file NAMED.STS. The correct file is NAMED.STA. Installation status: o If you are reinstalling TCP/IP V4.2.1, make sure that the configuration notebook is not running during the reinstall. o When using the TCP/IP V4.2.1 Install graphical user interface (GUI), wait for each page to completely display before doing any mouse or keyboard actions. Manipulating the GUI too soon may hang your computer; if so, you will have to restart it. o If you move MPTS to a different drive when installing the TCP/IP V4.2.1 package, after the MPTS install completes, you must shutdown and reboot before installing TCP/IP. o When installing TCP/IP V4.2.1 from a LAN directory, if a message asks you to insert a CDROM, your LAN may have gone down. Cancel that message and reinstall after your LAN comes back up. o For more information, see the MPTS V5.3 readme file (that is, \temp\tcpip41\mpts\readme.mpt). Configuration status: o If you experience a hang while scrolling, see the scrolling with a mouse description in the Java considerations section, above. o PMX and NFS users who want to autostart their programs must do so using the TCP/IP V4.2.1 Configuration Notebook and not the PMX/NFS Configuration Notebook. There is no Autostart tab in the PMX/NFS notebook. o PMX and NFS will not appear in the selection list on the Autostart tab unless these programs are installed on your computer. o It is possible to edit the trusers file manually and migrate that file to tcpnbk.lst rather than make changes using the configuration notebook. ***************** Attention ********************** If you change tcpnbk.lst using the Configuration notebook, and subsequently edit and migrate the trusers file, the files will not be synchronized. Making changes through the configuration notebook is the recommended solution. **************** End of Attention***************** Before the initial install, edit the trusers file in the etc directory (find it by entering set etc at a command prompt). Changes made before the initial install will be properly reflected in tcpnbk.lst. After the initial install, to add a new user: 1) Edit trusers and add the new user 2) Run "install /a- /c" (config-no-install) After the initial install, to change or delete a user: 1) Edit trusers and change or delete the user 2) Delete tcpnbk.lst 3) run "install /a- /c" (config-no-install) o When using the instructions in the TCP/IP Guide for Installing the TCP/IP Java Configuration Applications on a Remote Workstation, step 4b is not necessary. You can supply the IP address on the command line when you start the program. For example, DDNSAPC 1.2.3.4 would start the DDNS Server configuration program connecting to the machine with the IP address 1.2.3.4. o Multicast Configuration - By default, TCP/IP V4.2.1 uses the functional addressing mode for multicast transmissions. Some industry standard routers by default listen for multicast frames in broadcast mode. To configure an interface for broadcast mode multicast, add the MULTIBC parameter to the ifconfig statement in \mptn\bin\setup.cmd for that interface. For example: ifconfig lan0 multibc For Cisco 4700 series routers and IOS version 11.2(7), changing the router multicast mode to use functional addressing may cause the router to have boot problems. TCP/IP Stack - MPTS o If you are running any applications using EMX (for example, the Apache Web Server) you must be using emx.dll 0.9c fix 4, revision 50 or higher. o If you use VMODEM from the shareware SIO package and VMODEM will not start after installing TCP/IP V4.2.1, you may need to install a newer version of VMODEM. VMODEM must be at version 1.21 or later, dated 9/4/97 or later. o The new 32-bit stack fully supports DIX/802.3 encapsulation on an ethernet. This allows a variety of interfaces on a LAN, we can have mix of interfaces, some using DIX while others may be configured as 802.3. However, when an ethernet interface is configured as 802.3, the MTU size is automatically reduced to 1492 (DIX interface MTU size is 1500). Whenever a DIX interface sends a frame to an 802.3 frame, the payload by the DIX interface will be encapsulated in a form as desired by the remote end, which in this case would be 802.3. As a result, the total size of this frame will be 1522 btyes: 1500 + 14-byte MAC header + 8-byte SNAP/LLC header = 1522 bytes This exceeds the ethernet maximum frame size standard of 1514 bytes. As a result, the frame will be dropped by the ethernet interface card. To prevent this, the network administrator must reduce the MTU size to 1492 across this LAN. This is required for bridged LANs, also. All segments of a bridged LAN should have their MTU size reduced to 1492. o Support has been added to restrict domain names to the character set specified in RFC 1123 (that is, letters, digits, and dash). If you try to resolve a hostname with illegal characters, you will receive an unknown host message. To disable this feature, add this line to the mptn\etc\resolv2 file: options no1123 TCP/IP applications status: o If you are currently using the UNIX-like login program (LOGINUNX.EXE) to authenticate telnet clients connecting to your telnet server, the client userids and passwords in the PASSWD file will NOT be migrated to the new configuration. The passwords in the new configuration are encrypted using a different algorithm than the passwords in the PASSWD file. o If you install only the new 4.1 stack (MPTS 5.3) and not the new base applications, the telnet server and the RSH/REXEC servers (when under the control of InetD) will appear to hang their respective clients when the connection is closed. This problem can be resolved by installing APARs to the respective applications on the indicated platforms: Warp 4: IC17026 - telnetd IC17027 - rshd IC17028 - rexecd Warp Server: IC17023 - telnetd IC17024 - rshd IC17025 - rexecd Warp Server SMP: IC17029 - telnetd IC17030 - rshd IC17031 - rexecd NFS status: o NFS is a separate product that is not part of TCP/IP V4.2.1. However, TCP/IP V4.2.1 will automatically upgrade your NFS to contain the latest fixes. NewsReader, Gopher, WebExplorer status: o These programs are not being upgraded in TCP/IP V4.2.1 because Netscape Navigator has similar functions. IBM Service has created year-2000 fixes for NR2.EXE, and the fixed module is installed with TCP/IP V4.2.1. Ultimail status: o This program is not being upgraded in TCP/IP V4.2.1. ------------------------------------------------------- 9. Service o For additional assistance, see the Service and Support brochure in your OS/2 package for instructions about calling IBM Service. ------------------------------------------------------- 10. Trademarks IBM IBM, OS/2, and WebExplorer are trademarks of IBM Corporation. Other Companies Cisco is a trademark of Cisco Systems, Inc. Java is a trademark of Sun Microsystems, Inc. Other company, product, and service names may be trademarks or service marks of others.