Académique Documents
Professionnel Documents
Culture Documents
When you troubleshoot a TCP/IP networking problem, begin by checking the TCP/IP configuration on the computer that is experiencing the problem. You can use the ipconfig command to get host computer configuration information, including the IP address, subnet mask, and default gateway. Note
For Windows 95 and Windows 98 clients, use the winipcfg command instead of ipconfig.
When you use the ipconfig command with the /all option, a detailed configuration report is produced for all interfaces, including any configured serial ports. With ipconfig /all, you can redirect command output to a file and paste the output into other documents. You can also use this output to confirm the TCP/IP configuration of each computer on the network or to further investigate of TCP/IP network problems. For example, if a computer is configured with an IP address that is a duplicate of an existing IP address, the subnet mask appears as 0.0.0.0. The following example shows the output of the ipconfig /all command on a computer that is configured to use the DHCP server for automatic TCP/IP configuration, and WINS and DNS servers for name resolution.
Windows 2000 IP Configuration Node Type . . . . . . . . . : Hybrid IP Routing Enabled. . . . . : No WINS Proxy Enabled. . . . . : No Ethernet adapter Local Area Connection: Host Name . . . . . . . . DNS Servers . . . . . . . Description . . . . . . . Physical Address. . . . . DHCP Enabled. . . . . . . Autoconfiguration Enabled IP Address. . . . . . . . Subnet Mask . . . . . . . Default Gateway . . . . . DHCP Server . . . . . . . Primary WINS Server . . . Secondary WINS Server . . Lease Obtained. . . . . . 10:32:13 AM Lease Expires . . . . . . 10:32:13 AM . . . . . . . . . . . . . : : : : : : : : : : : : : host.grape-info.com 10.1.0.200 3Com 3C90x Ethernet Adapter 00-60-08-3E-46-07 Yes Yes 192.168.0.112 255.255.255.0 192.168.0.2 192.168.0.1 192.168.0.1 192.168.0.3 Wednesday, September 02, 1998
If no problems appear in the TCP/IP configuration, the next step is testing the ability to connect to other host computers on the TCP/IP network.
For Windows 95 and Windows 98 DHCP-enabled clients, use the release and renew options of the winipcfg command instead of ipconfig /release and ipconfig /renew to perform manual release or renewal of the IP configuration lease for a client.
Display or reset the DNS cache. Refresh registered DNS names. Display the DHCP class IDs for an adapter. Set the DHCP class IDs for an adapter.
It is usually best to verify that a route exists between the local computer and a network host by first using the ping command and the IP address of the network host to which you want to connect. Try pinging the IP address of the target host to see if it responds, as follows: ping IP_address You should perform the following steps when using ping: 1. Ping the loopback address to verify that TCP/IP is installed and configured correctly on the local computer. ping 127.0.0.1 2. Ping the IP address of the local computer to verify that it was added to the network correctly. ping IP_address_of_local_host 3. Ping the IP address of the default gateway to verify that the default gateway is functioning and that you can communicate with a local host on the local network. ping IP_address_of_default_gateway 4. Ping the IP address of a remote host to verify that you can communicate through a router. ping IP_address_of_remote_host The ping command uses Windows Socketsstyle name resolution to resolve a computer name to an IP address, so if pinging by address succeeds, but pinging by name fails, then the problem lies in address or name resolution, not network connectivity. If you cannot use ping successfully at any point, confirm that:
The computer was restarted after TCP/IP was installed and configured. The IP address of the local computer is valid and appears correctly on the General tab of the Internet Protocol (TCP/IP) Properties dialog box. IP routing is enabled and the link between routers is operational.
You can use different options with the ping command to specify the size of packets to use, how many packets to send, whether to record the route used, what Time-to-Live (TTL) value to use, and whether to set the "don't fragment" flag. You can type ping ? to see these options.
The following example illustrates how to send two pings, each 1,450 bytes in size, to IP address 192.168.0.1:
C:\>ping -n 2 -l 1450 192.168.0.1 Pinging 192.168.0.1 with 1450 bytes of data: Reply from 192.168.0.1: bytes=1450 time<10ms TTL=32 Reply from 192.168.0.1: bytes=1450 time<10ms TTL=32 Ping statistics for 192.168.0.1: Packets: Sent = 2, Received = 2, Lost = 0 (0% loss), Approximate roundtrip times in milli-seconds: Minimum = 0ms, Maximum = 10ms, Average = 2ms
By default, ping waits 1,000 ms (1 second) for each response to be returned before displaying the "Request Timed Out" message. If the remote system being pinged is across a high-delay link, such as a satellite link, responses may take longer to be returned. You can use the w (wait) option to specify a longer time-out.
nbtstat n displays the names that were registered locally on the system by programs such as the server and redirector. nbtstat c shows the NetBIOS name cache, which contains name-to-address mappings for other computers. nbtstat R purges the name cache and reloads it from the Lmhosts file.
nbtstat RR releases NetBIOS names registered with a WINS server and then renews their registration. nbtstat a name performs a NetBIOS adapter status command against the computer specified by name. The adapter status command returns the local NetBIOS name table for that computer plus the media access control address of the adapter. nbtstat S lists the current NetBIOS sessions and their status, including statistics, as shown in the following example:
NetBIOS connection table Local name State In/out Remote Host Input Output ----------------------------------------------------------------CORP1 <00> Connected Out CORPSUP1<20> 6MB 5MB CORP1 <00> Connected Out CORPPRINT<20> 108KB 116KB CORP1 <00> Connected Out CORPSRC1<20> 299KB 19KB CORP1 <00> Connected Out CORPEMAIL1<20> 324KB 19KB CORP1 <03> Listening
Bytes Unicast packets Non-unicast packets Discards Errors Unknown protocols C:\>netstat -a Active Connections Proto Local Address TCP myhost:1572 TCP myhost:1589 TCP myhost:1606 TCP myhost:1632 TCP myhost:1659
TCP myhost:1714 TCP myhost:1719 TCP myhost:1241 UDP myhost:1025 UDP myhost:snmp UDP myhost:nbname UDP myhost:nbdatagram UDP myhost:nbname UDP myhost:nbdatagram C:\>netstat -s IP Statistics
Packets Received = 5378528 Received Header Errors = 738854 Received Address Errors = 23150 Datagrams Forwarded = 0 Unknown Protocols Received = 0 Received Packets Discarded = 0 Received Packets Delivered = 4616524 Output Requests = 132702 Routing Discards = 157 Discarded Output Packets = 0 Output Packet No Route = 0 Reassembly Required = 0 Reassembly Successful = 0 Reassembly Failures = 0 Datagrams Successfully Fragmented = 0 Datagrams Failing Fragmentation = 0 Fragments Created = 0 ICMP Statistics Messages Errors Destination Unreachable Time Exceeded Parameter Problems Source Quenches Redirects Echoes Echo Replies Timestamps Timestamp Replies Address Masks Address Mask Replies TCP Statistics Active Opens Passive Opens Failed Connection Attempts Reset Connections Current Connections Segments Received Segments Sent Segments Retransmitted = = = = = = = = 597 135 107 91 8 106770 118431 461 Received 693 0 685 0 0 0 0 4 0 0 0 0 0 Sent 4 0 0 0 0 0 0 0 4 0 0 0 0
UDP Statistics Datagrams Received No Ports Receive Errors Datagrams Sent = = = = 4157136 351928 2 13809
The Tracert utility is useful for troubleshooting large networks where several paths can be taken to arrive at the same point.
Function Does not resolve addresses to host names. Maximum number of hops to search for target. Loose source route along host list. Number of milliseconds to wait between pings. Number of queries per hop. Waits this many milliseconds for each reply. Attaches a layer-2 priority tag (for example, for IEEE 802.1p) to the packets and sends it to each of the network devices in the path. This helps in identifying the network devices that do not have layer-2 priority configured properly. The -T switch is used to test for Quality of Service (QoS) connectivity. Checks to determine whether each router in the path supports the Resource Reservation Protocol (RSVP), which allows the host computer to reserve a certain amount of bandwidth for a data stream. The -R switch is used to test for Quality of Service (QoS) connectivity.
-T
Layer 2 tag
-R
RSVP test
The default number of hops is 30, and the default wait time before a time-out is 3 seconds. The default period is 250 milliseconds, and the default number of queries to each router along the path is 100. The following is a typical pathping report. The compiled statistics that follow the hop list indicate packet loss at each individual router.
D:\>pathping www.grape-info.com Tracing route to www.grape-info.com [202.144.128.220] over a maximum of 30 hops: 0 hoge.grape-info.com [192.168.0.24] 1 192.168.0.2 2 gw-dit.grape-info.com [202.144.158.206] 3 tpu-gw1.grape-info.com [202.144.159.195] 4 e0-0.tpu-br2.grape-info.com [202.144.129.2] 5 w3ext.grape-info.com [202.144.128.220] Computing statistics for 125 seconds... So