tyt10fi.htm

一个学习tcp/ip协议的教程

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

arps transmitted: 2 (2 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.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.