netsh diag ping

[office politics]

http://articles.techrepublic.com.com...ml?tag=nl.e064

When you use the ping command, you may ping several systems in order to determine where the breakdown is occurring. However, you can save yourself time and effort by using the Netsh command-line scripting utility and special command line that instantly test the full TCP/IP configuration of the adapter, including IP, DHCP, DNS, and WINS, as well as the default gateway. Here's how:

Open a Command Prompt.
Type Netsh Diag Ping Adapter 1.
Press [Enter].

my output

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>netsh diag ping adapter 1

Network Adapters ([00000001] Broadcom NetXtreme Gigabit Ethernet)
    DefaultIPGateway = 172.18.1.1 Same Subnet
            Pinging 172.18.1.1 with 32 bytes of data:
            Reply from 172.18.1.1: bytes=32 time=11ms TTL=11
            Reply from 172.18.1.1: bytes=32 time<1ms TTL=0
            Reply from 172.18.1.1: bytes=32 time<1ms TTL=0
            Reply from 172.18.1.1: bytes=32 time=1ms TTL=1
            Ping statistics for 172.18.1.1:
                Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
            Approximate round trip times in milli-seconds:
                Minimum = 0ms, Maximum = 11ms, Average = 3ms
    DHCPServer = 172.18.1.151
            Pinging 172.18.1.151 with 32 bytes of data:
            Reply from 172.18.1.151: bytes=32 time<1ms TTL=0
            Reply from 172.18.1.151: bytes=32 time<1ms TTL=0
            Reply from 172.18.1.151: bytes=32 time<1ms TTL=0
            Reply from 172.18.1.151: bytes=32 time<1ms TTL=0
            Ping statistics for 172.18.1.151:
                Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
            Approximate round trip times in milli-seconds:
                Minimum = 0ms, Maximum = 0ms, Average = 0ms
    DNSServerSearchOrder = 172.18.1.150
            Pinging 172.18.1.150 with 32 bytes of data:
            Reply from 172.18.1.150: bytes=32 time<1ms TTL=0
            Reply from 172.18.1.150: bytes=32 time<1ms TTL=0
            Reply from 172.18.1.150: bytes=32 time<1ms TTL=0
            Reply from 172.18.1.150: bytes=32 time<1ms TTL=0
            Ping statistics for 172.18.1.150:
                Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
            Approximate round trip times in milli-seconds:
                Minimum = 0ms, Maximum = 0ms, Average = 0ms
    IPAddress = 172.18.5.37
            Pinging 172.18.5.37 with 32 bytes of data:
            Reply from 172.18.5.37: bytes=32 time<1ms TTL=0
            Reply from 172.18.5.37: bytes=32 time<1ms TTL=0
            Reply from 172.18.5.37: bytes=32 time<1ms TTL=0
            Reply from 172.18.5.37: bytes=32 time<1ms TTL=0
            Ping statistics for 172.18.5.37:
                Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
            Approximate round trip times in milli-seconds:
                Minimum = 0ms, Maximum = 0ms, Average = 0ms


C:\>