C:\> ping 147.120.0.1

host responding, time = 25 ms

Debugging information for interface ifcust  Addr(6): 00 aa 00 20 18 bf

interrupts: 0 (5 receive, 0 transmit)

packets received: 5, transmitted: 6

receive errors: 0, unknown types: 0

     runts: 0, aligns: 0, CRC: 0, parity: 0, overflow: 0

     too big: 0, out of buffers: 0, rcv timeout: 0, rcv reset: 0

transmit errors: 0

     collisions: 0, underflows: 0, timeouts: 0, resets: 0

     lost crs: 0, heartbeat failed: 0

ARP statistics:

arps received: 2 (0 requests, 2 replies)

     bad: opcodes: 0, hardware type: 0, protocol type: 0

arps transmitted: 3 (3 requests, 0 replies)

5 large buffers; 4 free now; minimum of 3 free

5 small buffers; 5 free now; minimum of 4 free

C:\>

C:\> ping 147.120.0.10

ping failed: Host unreachable: ARP failed

Debugging information for interface ifcust  Addr(6): 00 aa 00 20 18 bf

interrupts: 0 (5 receive, 0 transmit)

packets received: 5, transmitted: 7

receive errors: 0, unknown types: 0

     runts: 0, aligns: 0, CRC: 0, parity: 0, overflow: 0

     too big: 0, out of buffers: 0, rcv timeout: 0, rcv reset: 0

transmit errors: 0

     collisions: 0, underflows: 0, timeouts: 0, resets: 0

     lost crs: 0, heartbeat failed: 0

ARP statistics:

arps received: 2 (0 requests, 2 replies)

     bad: opcodes: 0, hardware type: 0, protocol type: 0

arps transmitted: 4 (4 requests, 0 replies)

5 large buffers; 4 free now; minimum of 3 free

5 small buffers; 5 free now; minimum of 4 free</FONT></PRE>

<P>The message ping failed: Host unreachable for the last attempt is expected. PC/TCP provides the user with diagnostic messages with each ping command. To suppress these messages and simply get a success or fail message, the -z option can be used:

<BR>

<PRE>

<FONT COLOR="#000080">C:\&gt; ping -z 147.120.0.11

host responding, time = 25 ms

C:\&gt;

C:\&gt; ping -z 147.120.0.1

host responding, time = 25 ms

C:\&gt;

C:\&gt; ping -z 147.120.0.10

ping failed: Host unreachable: ARP failed</FONT></PRE>

<P>If the ping command is not successful with the local address, either the network interface card is configured incorrectly or the software installation has incorrect parameters. Check the network card for the correct IRQ and memory settings and then check the cable to ensure that it is connected properly and network terminators are in place. The software must have the correct drivers loaded, as well as the machine name, IP address, and similar information.

<BR>

<P>If the local machine responds but the remote machines do not, check the network connections. Try ping from one of the remote machines to ensure that the DOS machine can be reached by the other machines. Experience has shown that PC-based TCP/IP implementations can be quirky when booting. It is not unusual to have a ping command fail four or five times and then start working properly. Repeat the commands several times, waiting a few seconds between each attempt.

<BR>

<P>Once the machines can successfully respond to a ping request, try ftp or telnet from the DOS-based machine. An ftp attempt to log onto the SCO UNIX machine is shown here:

<BR>

<PRE>

<FONT COLOR="#000080">FTP Software PC/TCP File Transfer Program 2.31    01/07/94 12:38

Copyright  1986-1993 by FTP Software, Inc.  All rights reserved.

FTP Trying....Open

220 tpci.tpci.com FTP Server (Version 5.60 #1) ready.

Userid for logging in on 147.120.0.1? tparker

331 Password required for tparker.

Password for logging in as tparker on 147.120.0.1? abcdefg

230 User tparker logged in.

ftp:147.120.0.1&gt; ls

.profile

.lastlogin

.odtpref

trash

Initial.dt

XDesktop3

Transferred 265 bytes in 0 seconds

226 Transfer complete.

ftp:147.120.0.1&gt; exit</FONT></PRE>

<P>This session, which displayed the listing of files on the SCO UNIX server, shows that the ftp command worked properly. The FTP session was closed with the command exit.

<BR>

<P>Following the DOS-based test, start Windows (if it was installed) and ensure that the applications within the PC/TCP Applications program group are available and working. If problems are encountered with Windows starting, it is likely that an error was made in the SYSTEM.INI file. Check the previous instructions for the correct configuration.

<BR>

<P>After all that, the ftp Software PC/TCP system is installed and configured properly. The DOS machine can now be used for TCP/IP applications such as ftp and telnet. If some of the more powerful protocol features were installed, they are also usable. The DOS-based machine installation is now completed. The PC/TCP documentation contains instructions for using the system, as well as fine-tuning the kernel. It also helps users create gateways, routers, mail servers, and several other TCP/IP-related features.

<BR>

<BR>

<A ID="E68E98" NAME="E68E98"></A>

<H3 ALIGN=CENTER>

<CENTER>

<FONT SIZE=5 COLOR="#FF0000"><B>Windows-Based TCP/IP: NetManage's Chameleon</B></FONT></CENTER></H3>

<BR>

<P>NetManage produces a line of TCP/IP-based software specifically for Windows, Windows 95, and Windows for Workgroups. These applications are designed to provide full access to TCP/IP utilities through the Windows environment. NetManage's line of products includes a basic TCP/IP stack (called Newt), as well as full TCP/IP application packages in several forms, all called Chameleon. The system is also available for Windows NT. You are installing Chameleon on a Windows for Workgroups 3.11 machine on the sample network.

<BR>

<P>Chameleon uses the standard NDIS (Network Device Interface Specification) or the ODI (Open Data Link Interface) for communicating with the network interface card. This enables any card that uses either NDIS or ODI to be used with Chameleon.

<BR>

<P>Prior to installation of Chameleon, the same steps are performed as for the DOS-based TCP/IP package. The network interface card must be installed with suitable IRQ and memory address settings. If Chameleon is being added to an existing Windows for Workgroups system, the network card should already be installed and properly configured. The same information is required as for all TCP/IP installations: the host name, IP address, broadcast mask, subnetwork mask, and any information about gateways or routers that needs to be included.

<BR>

<P>The version of ChameleonNFS used for the sample network had its installation information slightly jumbled because of updates to both Chameleon and Windows for Workgroups. The information supplied today applies to Windows for Workgroups 3.1 and 3.11 and ChameleonNFS version 4.0, although other versions should be similar.

<BR>

<BR>

<A ID="E69E135" NAME="E69E135"></A>

<H4 ALIGN=CENTER>

<CENTER>

<FONT SIZE=4 COLOR="#FF0000"><B>Installing Chameleon</B></FONT></CENTER></H4>

<BR>

<P>Chameleon can be installed over a fully functioning Windows or Windows for Workgroups system. If Windows for Workgroups is used, ensure that the network performs properly (if possible) when talking to other NetBEUI-compatible machines. In this case, that's not possible because the sample network uses only TCP/IP.

<BR>

<P>The installation procedure for Chameleon is simple. From the Program Manager's File menu, select Run, then execute the SETUP.EXE program from the first Chameleon disk. As with most Windows applications, this starts the installation program.

<BR>

<P>The changes made to the system files might cause problems, affecting Windows' capability to boot. Before installing the Chameleon software, make copies of the AUTOEXEC.BAT, CONFIG.SYS, PROTOCOL.INI, WIN.INI, and SYSTEM.INI files. If problems are encountered, these files can return the system to its original state. You should consider making a full system backup before any major changes to software, of course.

<P>The Chameleon installation program requires a lengthy serial number and an activation key to ensure that there is only one such version on a network (this locks out multiple installations using the same serial number and activation key.) The installation script prompts for the distribution disks in order and copies all the necessary files.

<BR>

<P>Following the installation process, Chameleon builds the program group with the Chameleon applications included. The ChameleonNFS program group is shown in Figure 10.3. After creating the program group, Chameleon starts a customization screen that lets you specify your IP address, host name, network mask, and broadcast address. Save this information and then exit out of Windows to the DOS prompt to complete the check of the installation.

<BR>

<P><B><A HREF="10tyt03.gif" tppabs="http://www.mcp.com/817948800/0-672/0-672-30885-1/10tyt03.gif">Figure 10.3. The Chameleon program group.</A></B>

<BR>

<P>Because of the different installation variables encountered with different network drivers, it is advisable to check the following configuration files manually:

<BR>

<UL>

<UL>

<P>AUTOEXEC.BAT

</UL></UL>

<UL>

<UL>

<P>CONFIG.SYS

</UL></UL>

<UL>

<UL>

<P>PROTOCOL.INI

</UL></UL>

<BLOCKQUOTE>

<BLOCKQUOTE>

<P>SYSTEM.INI

<BR>

</BLOCKQUOTE></BLOCKQUOTE>

<P>The following sections discuss each of these files in more detail. If the files do not have the information specified in them, add them with a text editor. Failure to check the files properly can result in Windows being unable to boot properly. If this happens, copy the backup files in place of the newly modified files, restart Windows, and reinstall or reconfigure as necessary.

<BR>

<BR>

<A ID="E70E39" NAME="E70E39"></A>

<H5 ALIGN=CENTER>

<CENTER>

<FONT SIZE=4 COLOR="#FF0000"><B>The AUTOEXEC.BAT File</B></FONT></CENTER></H5>

<BR>

<P>The changes to the AUTOEXEC.BAT file necessary to enable Chameleon to run are the inclusion of the installation directory in the PATH environment variable and a network startup command. If Chameleon is installed on a Windows for Workgroups system, the network startup command should already exist.

<BR>

<P>The PATH environment variable must be modified to include the Chameleon installation directory, which by default is C:\NETMANAG. An existing PATH statement can be altered, or a new line can be added below the existing PATH statement that looks like this:

<BR>

<BR>

<PRE>

<FONT COLOR="#000080">PATH=C:\NETMANAG;%PATH%</FONT></PRE>

<P>Of course, the correct drive and subdirectory should be substituted. This chapter assumes default values throughout.

<BR>

<P>The command

<BR>

<BR>

<PRE>

<FONT COLOR="#000080">C:\WINDOWS\NET START</FONT></PRE>

<P>is already in the AUTOEXEC.BAT file if a Windows for Workgroups system is used (either version 3.1 or 3.11). If Chameleon is installed on a Windows (not Windows for Workgroups) system, the NETBIND command included with the distribution software should be called as well:

<BR>

<BR>

<PRE>

<FONT COLOR="#000080">C:\NETMANAG\NETBIND</FONT></PRE>

<P>Chameleon might install a SHARE command in the AUTOEXEC.BAT file if one does not exist. If one doesn't exist, it is advisable to add it if others can access the machine. SHARE is a DOS utility that activates file-sharing and record-locking. If other machines will be accessing the machine, SHARE is necessary to prevent error messages and potential system freezes when file conflicts occur.

<BR>

<P>The completed AUTOEXEC.BAT file looks like this for a Windows for Workgroups 3.1 or 3.11 installation:

<BR>

<PRE>

<FONT COLOR="#000080">PATH=C:\NETMANAG;%PATH%

C:\WINDOWS\NET START

SHARE</FONT></PRE>

<P>and like this for a Windows installation:

<BR>

<PRE>

<FONT COLOR="#000080">PATH=C:\NETMANAG;%PATH%

C:\NETMANAG\NETBIND

SHARE</FONT></PRE>

<P>If the NET START or NETBIND command is not executed properly, Windows displays an error message when it loads. In some cases, Windows can lock up while it tries to access the network drivers.

<BR>

<BR>

<A ID="E70E40" NAME="E70E40"></A>

<H5 ALIGN=CENTER>