|
|
This chapter shows you how to prepare for installing Cisco TCP/IP Suite, and covers these topics:
Cisco TCP/IP Suite 100 is a set of TCP/IP utilities and a TCP/IP stack. These utilities allow you to connect to and communicate with other computers on the Internet or your corporate intranet using standard TCP/IP protocols. When you install the suite, you can select the utilities you need, although some utilities require that you also install the Cisco TCP/IP stack.
Table 1-1 shows the utilities available with Cisco TCP/IP Suite 100, the Windows platforms supported, and whether the utility also requires that you install the Cisco TCP/IP stack. Because the Cisco TCP/IP stack is not available for Windows NT 4.0, you cannot install any utilities that require the stack on Windows NT.
| Utility | Use | Windows Platform | Cisco Stack Required |
|---|---|---|---|
| Netscape Navigator | Browse the World Wide Web; send and receive email; read newsgroups. | 3.x, 95, NT 4.0 | No |
| Telnet | Log into multi-user host systems such as UNIX, VMS, MVS, VM, and AS/400. | 3.x, 95, NT 4.0 | No |
| Kerberos | Authenticate your identity when accessing Kerberos-protected systems. | 3.x, 95, NT 4.0 | No |
| FTP Client | Get files from FTP servers, or put them there. | 3.x, 95, NT 4.0 | No |
| FTP Server | Allow other users to connect to your machine using an FTP client, so you can share files with them. | 3.x, 95 | No |
| Net Tools | General TCP/IP utilities: Ping, Finger, Host Lookup, Whois, TraceRoute. | 3.x, 95, NT 4.0 | No |
| Dialer | Connect to a network over a serial line, such as a modem connection. | 3.x, 95 | Yes |
| Ping | Troubleshoot network connections. | 3.x, 95 | Yes |
| Monitor | Monitor the TCP/IP stack activity for troubleshooting purposes. | 3.x, 95 | Yes |
| TCPDump | Help Cisco service representatives troubleshoot advanced problems with your TCP/IP stack setup. | 3.x, 95 | Yes |
| SNMP Agent | Allow SNMP network management software monitor and maintain your workstation. | 3.x, 95 | Yes |
| NFS and Print Assistant | Mount NFS server drives and attach NFS printers. | 95 | Yes |
| NFS Assistant | Mount NFS server drives. | 3.x | Yes |
| Print Assistant | Attach NFS printers. | 3.x | Yes |
The workstation on which you install Cisco TCP/IP Suite must meet the following requirements:
Cisco TCP/IP Suite supports NDIS 3.0, NDIS 2.0, and ODI drivers. The type you use depends on your interface card, version of Windows, and networking requirements.
For Windows 95 and Windows NT, the network drivers are handled when you install the network adapter for the network interface card. You do not select a driver as part of the Cisco TCP/IP Suite installation.
For Windows 3.x, you must choose a network driver during installation. You can choose NDIS 3.0 if you are running Windows for Workgroups 3.11. Otherwise, you must choose NDIS 2.0 or ODI.
We recommend that you install the network driver before beginning the installation.
Before you install Cisco TCP/IP Suite:
The following sections describe each step in more detail.
The installation procedure asks you a few questions about your workstation and network. We recommend that you gather the information before beginning the installation.
You need this information, which you can get from your network administrator:
daisy.
yoyodyne.com. This is used by DNS to resolve host names to IP addresses.
We recommend that you install the workstation's network interface card and test it with the diagnostics supplied with the card before installing Cisco TCP/IP Suite.
If you are running Windows 3.1 or 3.11, we also recommend that you install the NDIS or ODI driver and verify that it is running before installing Cisco TCP/IP Suite.
Verify that the hardware settings of the network interface card are configured and do not conflict with other boards in the workstation.
If your workstation already has a TCP/IP stack other than Microsoft's stack and you want to install the Cisco TCP/IP stack, you must first remove the other stack. If you need information on how to remove a stack, refer to that TCP/IP vendor's documentation.
If you install the Cisco TCP/IP stack, it automatically removes the Microsoft stack during installation.
Be sure to remove any configuration information pertaining to other stacks from the following files:
To verify that Windows 3.1 and 3.11 are running in enhanced mode, choose About Program Manager from the Program Manager Help menu. The About Program Manager dialog should display "386 Enhanced Mode" at the bottom of the dialog just above the Memory indicator.
Windows for Workgroups runs only in enhanced mode.
If you are installing on a Windows 95 or Windows NT workstation for LAN (local area network) use, locate your Windows 95 or Windows NT installation media because you might be required to insert it during the course of the installation. You will also need the installation media if you add network printers not previously configured on your workstation.
If you are a network administrator, you can simplify the installation of Cisco TCP/IP Suite on the workstations on your network by setting up for a network installation. Then, you can tell your users where the product is and have them install from the server, or you can go from machine to machine and install it yourself, without carrying the installation media with you.
You can also customize the Cisco TCP/IP configuration files so that users already have much of what they need to configure done for them.
The following are important requirements for using network installation:
To initially set up Cisco TCP/IP Suite for a network installation:
Step 1 Copy the contents of the Cisco TCP/IP Suite distribution media to the network server, mirroring the directory structure on the media. If your users do not use one of the supported versions of Windows, you do not need to copy that portion of the installation media to your server. Apply proper permissions to the directory to prevent unauthorized files from being created in the directory and its subdirectories.
Step 2 Create an MIS subdirectory in the same directory as the SETUP.EXE files for each version of Windows. For example, if you copied the contents of the Cisco TCP/IP Suite installation media to the root directory of your network server, the MIS directories are:
\Multinet\Win31\MIS
\Multinet\Win95\MIS
\Multinet\WinNT\MIS
Step 3 If you have not already done so, install Cisco TCP/IP Suite on your machine under each version of Windows you are supporting (or use a test machine) and use the Configuration Utility to customize the configuration for each platform. Add interface, routing, DNS, host table, NetBIOS over TCP/IP, LM hosts, and global parameters as appropriate for your network. When you are satisfied with the configuration, copy the MULTINET.INI file from the Windows installation directory to the MIS directory for the corresponding platform.
You can use NotePad to edit MULTINET.INI and remove information such as the workstation's host name. When users install Cisco TCP/IP Suite, the Configuration Wizard uses the information in this file when it prompts the user for the corresponding information. Therefore, you might want to remove any information that you definitely do not want users to use, which is normally the case with IP addresses and host names, which must be unique for each user.
Step 4 Optionally, customize the profiles for individual Cisco TCP/IP Suite applications.
Once you have set up the files on the network server, users can successfully install Cisco TCP/IP Suite from the network. However, you can further help users by customizing the profiles for the individual applications. This is especially helpful if your users will be using Dialer to make connections to your network over modems.
To customizes profiles and settings for the Cisco TCP/IP Suite applications, start each application and create and test the profiles or other settings. See the online help for each application for details on creating profiles for that application.
Table 1-2 describes the main files you can customize, where they are located if you used the default installation directory, and where you must place them on the network server for network installations:
| File Name | Use | Get Them From: | Put Them In: |
|---|---|---|---|
| *.tel | Profiles of hosts users will connect to using Telnet | \Multinet\Telprofs | \Multinet\MIS\Telprofs |
| *.kbd | Telnet Keyboard profiles | \Multinet\Telprofs | \Multinet\MIS\Telprofs |
| Hosts | Host table for use with the Cisco TCP/IP stack (not available on Windows NT) | \Multinet | \Multinet\MIS |
| Kerberos.cfg | Kerberos realm and ticket server configuration | \Multinet | \Multinet\MIS |
| Kerberos.rlm | Kerberos special realm mappings | \Multinet | \Multinet\MIS |
| Mndialer.ini | General Dialer settings and the Dialer Manual Connect configuration | \Multinet | \Multinet\MIS |
| Mndialer.mnd | Dialer profiles for automating serial connections | \Multinet | \Multinet\MIS |
| Mnftpcli.mnd | Profiles for hosts users will connect to using FTP Client | \Multinet | \Multinet\MIS |
| Mnkerb.ini | General Kerberos application settings | \Multinet | \Multinet\MIS |
| Mnnet.ini | NFS settings | \Windows\System
(The Windows installation directory.) For Windows 3.x systems, the file is in \Multinet. | \Multinet\MIS |
| Mnping.mnd | Profiles for hosts users will want to Ping (for example, to do rudimentary troubleshooting) | \Multinet | \Multinet\MIS |
| Socks.DAT | Identifies SOCKS servers, if you use them to allow connections outside your firewall. This is used by FTP Client and Telnet. See the online help for those applications for information on creating and using Socks.DAT | \Multinet | \Multinet\MIS |
During a network installation:
You can create installation diskettes from the CD-ROM by opening an MS-DOS prompt and running the MKDISKS.BAT program, which is in the MULTINET\WIN95, MULTINET\WIN31, and MULTINET\WINNT directories.
The MKDISKS program creates the disk images on the drive you select (which should be a hard drive), and then you copy each disk image to a separate diskette. MKDISKS creates the target directory if it does not exist, and names the diskette image directories DISK_n, where n is a number from 1 to the total number of diskettes in the distribution.
Run the program without options to show the help information. The command format is:
MKDISKS source_directory destination_directory
where source_directory is the directory on the CD-ROM that contains the version of Cisco TCP/IP Suite for which you want to create diskettes, and destination_directory is the directory where you want to create the diskette images.
For example, to create diskette images for the Windows 95 version of the product on your C: drive in the \MN_KIT\WIN95 directory (when your CD-ROM is the D: drive), enter:
MKDISKS D:\MULTINET\WIN95 C:\MN_KIT\WIN95
After running MKDISKS, create diskettes with the COPY command; for example:
COPY C:\MN_KIT\WIN95\DISK_1\*.* A:
COPY C:\MN_KIT\WIN95\DISK_2\*.* A:
and so on
Once you create diskettes, install Cisco TCP/IP Suite by double-clicking the SETUP.EXE program on the first diskette and following the prompts.
If you obtained Cisco TCP/IP Suite 100 for Windows as an evaluation copy, you need only change the license key to obtain full use of the product. To change your license key:
Step 1 
Start the Version Information application by doing one of the following:
Step 2 Select the evaluation license key and click the Modify button beside the license list.
Step 3 Enter the new license key.
|
|