(c) Copyright 2000 International Business Machines Corp. All rights reserved. IBM TCP/IP 4.3 Readme File Contents -------- 1. TCP/IP 4.3 Enhancements 2. Operating Systems Supported 3. Prerequisite Software 4. Uninstalling previous versions of TCP/IP 5. Installing TCP/IP 4.3 6. Uninstalling TCP/IP 4.3 instructions 7. Dynamic IP Changes 8. Known Problems, Restrictions, and Considerations 9. Service 10.Trademarks ------------------------------------------------------- 1. TCP/IP 4.3 ENHANCEMENTS The following enhancements are provided with TCP/IP 4.3 - Sendmail function for controlling spamming - DNS Enablement in Name resolution algorithm for TCPBEUI - Redundant token ring adapter support and recovery - Fault isolation and recovery for default routes(RFC 816) - Passive FTP support in REXX FTP functions. - PXE 2.1 Enhancement for NetPC booting. TCP/IP 4.3 is available as a feature on IBM Software Choice ------------------------------------------------------- 2. OPERATING SYSTEMS SUPPORTED This version of TCP/IP 4.3 can only be installed only on o OS/2 WARP Server for e-business. o OS/2 Warp 4.0. ------------------------------------------------------- 3. PREREQUISITE SOFTWARE Before installing TCP/IP V4.3, make sure the following prerequisite software is installed on your system. 1. OS/2 Feature Install Version 1.2 or greater. 2. Java for OS/2 Version 1.1.7 or Version 1.1.8. To run Java applications provided in this release, you need install only the Runtime portion of Java for OS/2. NOTE: TCP/IP V4.3 Java Configuration programs (ie. tcpcfg2.cmd) are not supported on Java for OS/2 Version 1.3. Java for OS/2 Version 1.3 cannot be used as the system JVM if installing TCP/IP V4.3. 3. Netscape Navigator or Netscape Communicator. - Netscape Navigator 2.02 or greater. - Netscape Communicator 4.04 or greater. 4. MPTS version 6.0 (included with this package). ------------------------------------------------------- 4. UNINSTALLING PREVIOUS VERSIONS OF TCP/IP It is not required to uninstall previous versions of TCP/IP but if you choose to, the following steps are recommended. NOTE: Be sure to get all the required ZIP (tcpip43.zip) files for installing TCPIP 4.3 prior to start this UNINSTALLATION process. Go to TCP/IP Shadows ICON and click on Uninstall TCP/IP 4.21 Icon. Go through the uninstallation screen(s) select all the components in the component selection page and proceed to complete the uninstallation of all the components (TCPIP APPS, DHCP/DDNS, NFS, VPN). NOTE: On OS/2 Warp 4.0 machine you might not find the TCP/IP Shadow icon. In such case install TCP/IP 4.3 over the present TCPIP. 1. Go to CONFIG.SYS and remove all the statements which refer to TCPIP directory. 2. Reboot the system. 3. You may have to manually remove some files in the TCPIP subdirectory. ------------------------------------------------------- 5. INSTALLING TCP/IP 4.3 NOTE: Before you install TCP/IP V4.3, make sure all of the prerequisite software are installed on your system. To install TCP/IP V4.3: 1. Make a subdirectory for: o TCP/IP V4.3(includes MPTS 6.0) To make a subdirectory, from an OS/2 window: a. Make a root-level temporary directory; type: 'md temp' b. Go to temp; type: 'cd temp' c. Make a temp\tcpip43 subdirectory for TCP/IP V4.3; type: 'md tcpip43' 2. Download and install TCP/IP V4.3 (with MPTS 6.00): Note: This procedure will install the new MPTS and TCP/IP programs in the directories that contain your existing MPTS and TCP/IP. a. With your Web browser, navigate to the IBM TCP/IP V4.3 for OS/2 download page. b. Click on the Download push button and download the TCP/IP V4.3 for OS/2 package to the temp directory you created in step 1. c. Make temp\tcpip43 your current directory. d. Using an unzip program that can create subdirectories, unzip the tcp43.zip file. (For example, enter 'unzip tcp43.zip' or an equivalent command like 'pkunzip2 -d tcp41.zip'.) e. Type 'cd tcpip' (that is, make temp\tcpip43\tcpip your current directory) f. If you are upgrading over a previous version of TCP/IP and you do not wish to install the function in Secure Remote IP Client, you can type 'install /a-' from a command prompt and skip to step z. If you want to install Secure Remote IP Client, type 'install' and continue with step g. For more information on CID installation, see the TCP/IP Guide. g. When asked whether to install a more recent version of MPTS, Click Yes. h. Click OK on the Multi-Protocol Transport Services logo window, if necessary. i. Click Install on the Multi-Protocol Transport Services window. j. Click OK on the MPTS Target Drive window. Do not change the Target Drive letter. It should point to the drive where MPTS is currently installed. k. If a Reinstall MPTS window appears, click OK. l. When the Installation Complete window appears, click OK. Note: If the system is configured for "IBM OS/2 NetBIOS over TCP/IP" then the following configuration change must be made, otherwise proceed to step m to keep the current MPTS configuration. l-1. Click Configure on the Multi-Protocol Transport Services window. l-2. In the Configure window, the LAN Adapters and protocols radio button should be selected and click on Configure. l-3. In the LAN Adapter and Protocol Support window, under "Current Configuration", double click on the first instance of "IBM OS/2 NetBIOS over TCP/IP". l-4. In the NetBIOS over TCP/IP window, the driver parameters radio button should be highlighted and click on Configure. l-5. Look for "TCP-Frame descriptors" parameter and decrease the current value by 20. For example, if it's currently configured for 132, change it to 112. l-6. Click OK to save. l-7. Click Close at the NetBIOS over TCP/IP window. l-8. Click OK to complete the configuration change in the Adapter and Protocol Configuration window. l-9. Click Close at the Configure window to save the configuration change. Note: Failure to make this configuration change to "IBM OS/2 NetBIOS over TCP/IP" protocol, may result in the following error during re-ipl: sys1201: The device driver C:\IBMCOM\PROTOCOL\TCPBEUI.OS2 specified in the DEVICE statement on line xx of the CONFIG.SYS was not installed. Line xx is ignored. This error will cause other errors to follow during ipl. m. When the Multi-Protocol Transport Services window appears, click Exit. n. When the Update CONFIG.SYS window appears, verify that "Update CONFIG.SYS" is selected. If there is more than one boot drive on your system, verify that the only the current boot drive is highlighted. Click Exit. o. When the CONFIG.SYS Updated window appears, click OK. This completes the MPTS install. p. Wait for the TCP/IP installation program to continue. Note: Netscape is used by the TCP/IP install program. If Netscape has never been started on this system, the Netscape "New Profile Setup" panels will display. If this happens, click on "Next" on all panels, then click on "Finish" to complete the Netscape profile setup. q. When the TCP/IP V4.3 for OS/2 Installation window displays, click the Forward (right arrow) button at the bottom of the window. r. On the Welcome to TCP/IP V4.3 for OS/2 Installation window, click Guided Path. s. In the next TCP/IP V4.3 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. t. The NFS checkbox will be preselected whether or not NFS is installed. If NFS is already installed on the system and you try to unselect NFS an information window is displayed that says NFS 2.0 is no longer supported and will be upgraded to NFS 3.0. u. Click Forward. v. Type your Administrator Password in the Drive Selection for TCP/IP 4.3 for OS/2 window, if you plan to do any remote TCP/IP configuration or administration. (A utility shipped with TCP/IP V4.3, 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. w. Click Forward. x. Click the Install (diagonal arrow) button at the bottom of the Ready to Install TCP/IP 4.3 for OS/2 window. y. Click the Exit (X) button at the bottom of the Installation Complete for TCP/IP V4.3 for OS/2 window. z. 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.3 and verifying that the installation(s) completed successfully, you can delete the entire \temp directory tree. ------------------------------------------------------- 6. UNINSTALLING TCP/IP 4.3 INSTRUCTIONS Once you have installed TCP/IP V4.3, it can be uninstalled by using the Uninstall TCP/IP V4.3 icon in the TCP/IP Shadows folder. After running the uninstall program and rebooting the system, you may need to clean up any files still remaining in the TCPIP subdirectory. ------------------------------------------------------- 7. Dynamic IP Changes o DHCP Server and BINL Server : The DHCP Server has modifications supporting the Wired for Management Specification 2.0. This caters to the clients using Preboot eXecution Environment (PXE) 2.1 specifications of INTEL. This specification also requires another server called the Boot Image Negotiation Layer (BINL) Server. The BINL Server works in conjunction with the DHCP Server and provides certain parameters to the Network Computer enabling them to Bootup. ------------------------------------------------------- 8. Known Problems, Restrictions, and Considerations Known problems, restrictions, and considerations with TCP/IP V4.3 include: Java Considerations: o The TCP/IP V4.3 Java programs may run slowly, particularly on low-end computers. o Occasional traps have been observed in various Java components. If a trap occurs, reboot your machine. Usually the traps cannot be recreated. o One of the traps observed was when Lotus Domino 4.6.3 Server was also installed. The trap occurred on running tcpcfg2 from the icon. (This is the TCIP/IP Configuration icon found in TCP/IP Configuration folder in the TCP/IP Shadows folder). The following error was encountered: SYS2070 Segment Load Error: JAVA->JAVAR._strtodiee The error can be corrected as follows. In the LIBPATH in CONFIG.SYS move all strings related to JAVA (Eg: X:\JAVA11\DLL, X:\JAVA11\ICATJAVA ) before the occurrence of "X:\NOTES" An example is given below. Change the following LIBPATH LIBPATH=x:\netscape\program;x:\notes;x:\java11\dll;x:\java11\icatjava\dll;x:\java11\icatjava\daemon; to the one given below LIBPATH=x:\netscape\program;x:\java11\dll;x:\java11\icatjava\dll;x:\java11\icatjava\daemon;x:\notes Note: Here X: is a generic reference to indicate a drive. It might not be the same on your machine. 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 : ex: admin_pw.cmd, dadmgui.cmd, binlscpc.cmd, binlscps.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 that 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. Installation status: o If you are reinstalling TCP/IP V4.3, make sure that the configuration notebook is not running during the reinstall. o When using the TCP/IP V4.3 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 When installing TCP/IP V4.3 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 If you are using Netscape Navigator 4.61, you may notice some anomalies or errors in the Display of Installation GUI. You will have to refresh your screen to clear these errors. Refresh can be done by pressing the Ctrl-R key together. The following anomalies and errors were seen during installation of TCP/IP 4.3. The following anomalies/errors were noted during Installation. - In the "Selected Components" screen the DHCP/DDNS SERVER checkbox might come up checked even though you do not have the DHCP/DDNS Server installed. In this case, if you do not wish to install the DHCP/DDNS Server feature, uncheck the box and continue. - In the "Select and Configure Components" screen the Drive combo box and the Configure button are not clear. Refresh the screen and the correct icons will appear. The following anomalies/errors were noted during Uninstallation. - In the "Select Components" screen the DHCP/DDNS Server checkbox comes up abled and unchecked. This should not be present. Refresh the screen and you will see the correct screen. 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.3 Configuration Notebook and not the PMX Configuration Notebook. There is no Autostart tab in the new PMX notebook(tcpcfg.exe). 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. o To mount the file systems exported by NFS2.0 Servers, using NFS3.0 Client, -soff option needs to be specified in the mount command. Example: mount -soff k: 9.184.209.22:c:\temp In the above example, mount command is run on NFS3.0 client and "c:\temp" is a file system exported by NFS2.0 Server. o FSATB.INI is used in conjunction with NFSSTART.EXE. Each entry in FSTAB.INI is a valid "MOUNT" command entry. NFSSTART picks up each line of this file and mounts the drives as specified. Example: mount k: 9.184.209.22:c:\temp mount -soff p: 9.184.209.44:c:\docs . . . etc., ***************** Attention ********************** If you change tcpnbk.lst using the Configuration notebook, and subsequently edit and migrate the trusers file, the files will not be synchronised. 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 typing 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.3 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. PMX status: PMX is not supported in TCP/IP V4.3, but those users who already had PMX on their machines before TCP/IP V4.3 was installed shall continue to use PMX with the new PMX CONFIGURATION NOTEBOOK (tcpcfg.exe). Those who install PMX separately after having installed TCP/IP V4.3 need to manually bring in the file TCPCFG.EXE from the TCPIP\SAMPLES\BIN directory into the TCPIP\BIN directory and use it. NFS status: If you have NFS 2.0 installed on your system, installation of this package automatically upgrades NFS 2.0 to NFS 3.0 ------------------------------------------------------- 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. -------------------------------------------------------