═══ 1. TCP/IP Installation ═══ Use the TCP/IP installation program to install one or more of the kits that comprise IBM* TCP/IP Version 2.0 for OS/2*. When you initiate the TCP/IP installation program, the TCP/IP Installation Tool window is displayed. To install TCP/IP for OS/2, do the following: 1. Select the kits that you want to install. 2. If you want to install TCP/IP for OS/2 to a directory other than the default directory, specify base directory for installation. 3. Specify whether you want TCP/IP for OS/2 to update your CONFIG.SYS. 4. If you are installing the Base Kit, specify whether you want TCP/IP to configure your network connection. 5. Specify whether you want TCP/IP for OS/2 to install the LAN Adapter and Protocol Support. 6. If you selected Configure network connection, specify the following: o Host name o IP address o Subnet mask o Router IP address When you have completed all appropriate fields, select Install to proceed with the installation. Installing from the TCP/IP Product Diskettes If you selected to install LAPS, the installation program prompts you to insert the LAPS diskette. The TCP/IP installation program then invokes the LAPS installation program, allowing you to install and configure LAPS. When you exit the LAPS installation program, the TCP/IP installation program begins prompting you for the product diskettes. Installing from an Established Network Drive If you selected to install LAPS, the installation program invokes the LAPS installation program, allowing you to install and configure LAPS. When you exit the LAPS installation program, the TCP/IP installation program begins unpacking the product files. ═══ 2. Overview of the TCP/IP for OS/2 Kits ═══ TCP/IP for OS/2 is packaged in kits; a Base Kit and several component kits. The Base Kit provides the protocol stack necessary to support all the functions of TCP/IP for OS/2. It also provides a base set of applications, including telnet, ftp, and sendmail. There are other products that provide the same protocol stack. Therefore, TCP/IP for OS/2 has been designed to allow you to install the component kits either on the TCP/IP for OS/2 Base Kit or on another product that provides the necessary protocol stack. The component kits available for TCP/IP for OS/2 are: o Applications Kit o Domain Name Server Kit o DOS/Windows Access Kit o Extended Networking Kit o OSF/Motif Kit o Network File Server Kit o Programmer's Toolkit o X Window System Server Kit o X Window System Client Kit ═══ 2.1. Applications Kit ═══ The Applications Kit provides the TCP/IP for OS/2 applications included in the Base Kit without the underlying TCP/IP protocol stack. ═══ 2.2. Domain Name Server Kit ═══ The Domain Name Server Kit provides support for a hierarchical naming system for naming hosts, allowing system administrators to name local domains with in an internet. ═══ 2.3. DOS/Windows Access Kit ═══ The DOS/Windows Access Kit enables DOS or Windows** TCP/IP user-written applications that use the WinSock API to run over an OS/2 environment through TCP/IP for OS/2. This kit also enables character-based DOS applications, which have been written to the programming interfaces of IBM TCP/IP for DOS, to run in an OS/2 DOS session. The DOS/Windows Access Kit requires OS/2 Version 2.1 or later. ═══ 2.4. Extended Networking Kit ═══ The Extended Networking Kit enables you to install and configure an X.25 or SNALINK interface. ═══ 2.5. OSF/Motif Kit ═══ The OSF/Motif** Kit is comprised of two parts; the OSF/Motif Runtime Services and the OSF/Motif Programmer's Toolkit. The Runtime Services provide the DLLs that enable users to run Motif applications on OS/2. The Programmer's Toolkit provides the standard OSF/Motif widgets and header files that enable users to create Motif applications on OS/2. The Motif Kit requires the X Window Client Kit and the TCP/IP Programmer's Toolkit. ═══ 2.6. Network File Server Kit ═══ The Network File Server** Kit enables you to share drive resources across networks as if the resources were local. It uses the User Datagram Protocol (UDP) for communication between clients and servers. ═══ 2.7. Programmer's Toolkit ═══ The Programmer's Toolkit provides routines for application programming in TCP/IP for OS/2. These routines include sockets, RPCs, the File Transfer Protocol (FTP) application programming interface (API), and the Simple Network Management Protocol (SNMP) distributed programming interface. These routines use the 32-bit compiler, IBM C Set/2 Version 1.0. ═══ 2.8. X Window System Server Kit ═══ The X Window System** Server Kit enables you to display and control X Window System client applications in an OS/2 Presentation Manager windowed session. Because the X Window System server uses OS/2 Presentation Manager as the window manager, it supports all of the keyboard, display, and pointer devices that are supported by OS/2 Presentation Manager. ═══ 2.9. X Window System Client Kit ═══ The X Window System** Client Kit is comprised of two parts; the X Window System Client Runtime Services and the X Window System Client Programmer's Toolkit. The Runtime Services provide the DLLs that enable users to run X Window applications on OS/2. The Programmer's Toolkit provides the standard X Window System APIs from the MIT Consortium that enable users to create X Window applications for OS/2 or to port X Window applications from other platforms. The X Window Client Kit requires the TCP/IP Programmer's Toolkit. ═══ 3. Base Directory ═══ If you want to install TCP/IP for OS/2 to a directory other than the default directory, specify the target drive and directory in the Base directory for the installation field. For example, D:\TCPIP , where D is the target drive and TCPIP is the name of the target directory on that drive. Ensure that the directory specified is located on a drive that has enough free disk space to store all the TCP/IP kits that you want to install. The required disk space for each kit is noted in parentheses beside the kit name on the TCP/IP Installation Tool window. If you already have components of TCP/IP for OS/2 installed on your workstation, we recommend that you install any additional components to the same base directory. Note: If you are installing a TCP/IP customer service diskette, specify the same directory that was used for the original installation. ═══ 4. Update CONFIG.SYS ═══ In most cases, you will want TCP/IP to update your CONFIG.SYS, however if you do not want TCP/IP to make the necessary changes to the PATH, LIBPATH, HELP, and other statements in your CONFIG.SYS, deselect Update CONFIG.SYS. If TCP/IP updates your CONFIG.SYS, your current CONFIG.SYS is saved to a file called CONFIG.TCP. If TCP/IP does not update your CONFIG.SYS, it makes a copy of your CONFIG.SYS, modifies the copy and saves it to CONFIG.TCP. Note: If the necessary modifications are not made to your CONFIG.SYS, you will not be able to access the TCP/IP configuration notebook. ═══ 5. Configure network connection ═══ If you are installing the Base Kit, you need to configure your network connection. To create a basic network configuration, select this check box and enter information in the following fields: o Host name o IP address o Subnet mask o Router IP address If you have an existing TCP/IP already installed, the basic network configuration information will be migrated. Therefore, you do not need to select this check box or fill in the associated fields. If you do not create your basic network configuration during installation, or if any of the information changes, you can use the TCP/IP configuration notebook to create or modify the basic network configuration. Note: This field is not available if you have not selected to install the Base Kit. ═══ 6. LAN Adapter and Protocol Support (LAPS) ═══ TCP/IP requires the TCP/IP network driver provided by the current version of LAPS. Unless you have a current version of LAPS and an existing TCP/IP already installed, you need to install and configure LAPS. Select this check box to install and configure LAPS as part of this TCP/IP installation. When you have completed the fields on this window and select Install, you will be prompted to insert the LAPS diskette. The TCP/IP installation program will invoke the LAPS installation and configuration program. When you install and configure LAPS, your CONFIG.SYS is modified. Your current CONFIG.SYS is saved to a file called CONFIG.LAP. Warning: When you install and configure LAPS, your current PROTOCOL.INI file is replaced. Therefore, ensure that you configure each protocol for each adapter. Note: This field is not available if you have not selected to install the Base Kit. ═══ 7. Host Name ═══ Your host name is the unique name assigned to your workstation. It is provided by your network administrator, and can be 1 to 30 alphanumeric characters. It cannot contain blanks or special characters. This field is optional. However, if you do not provide a host name at installation, you will need to use the TCP/IP configuration notebook to specify a host name before you can use TCP/IP. Note: This field is not available if you have not selected Configure network connection. ═══ 8. IP Address ═══ Your Internet Protocol (IP) address is the unique internet address assigned to your workstation. It is provided by your network administrator, and is in the format of nnn.nnn.nnn.nnn. This field is optional. However, if you do not provide an IP address at installation, you will need to use the TCP/IP configuration notebook to specify an IP address before you can use TCP/IP. Note: This field is not available if you have not selected Configure network connection. ═══ 9. Subnet Mask ═══ Your subnet mask is a mask used to separate the subnet address from the host portion of the address. It is provided by your network administrator, and is in the format of nnn.nnn.nnn.nnn. Each nnn is one of the following: 255, 254, 252, 248, 240, 224, 192, 128, or 0. If one of the numbers in the subnet mask is not 255, the numbers that follow must all be 0. This field is optional. If you do not provide a subnet mask, the default netmask for the class of your IP address is used. You can use the TCP/IP configuration notebook to modify your subnet mask after installation. Note: This field is not available if you have not selected Configure network connection. ═══ 10. Router IP Address ═══ Your router IP address is a the internet address of your default router or gateway. A router allows your workstation to communicate with other hosts that are not on your local area network (LAN). Your router IP address is provided by your network administrator, and is in the format of nnn.nnn.nnn.nnn. This field is optional. However, if you do not provide a router IP address, you will need to use the TCP/IP configuration notebook to specify a router IP address before you can communicate with hosts that are on other LANs. Note: This field is not available if you have not selected Configure network connection. ═══ IBM Trademarks ═══ The following terms, denoted by an asterisk (*) at their first occurrences in this online help, are trademarks of IBM Corporation in the United States or other countries: IBM Micro Channel Operating System/2 OS/2 Presentation Manager PS/2 ═══ Non-IBM Trademarks ═══ The following terms, denoted by a double asterisk (**) at their first occurrences in this online help, are trademarks of other companies: Trademark Owned By Network File System Sun Microsystems, Inc. NFS Sun Microsystems, Inc. X Window System Massachusetts Institute of Technology Windows Microsoft Corporation