This appendix provides some examples of using the Windows NT/2000 console IP utilities.
Netstat is a very useful tool for looking at various aspects of the IP configuration. Here, we illustrate the IP routing table on a Windows 2000 PC.
C: etstat -r Route Table Interface List 0x1 .................... MS TCP Loopback interface 0x1000003 ...00 b0 d0 16 48 97 ... 3Com EtherLink PCI Active Routes: Network Dest Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 142.159.65.17 142.159.65.29 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 142.159.65.0 255.255.255.0 142.159.65.29 142.159.65.29 1 Default Gateway: 142.159.65.17 Persistent Routes: None
Ping is an indispensable tool for determining if specified IP interfaces are up.
C:>ping 127.0.0.1
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milliseconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
In the above session, four ICMP request packets are sent to the loopback interface, and four ICMP response packets are received.
Traceroute is very useful for determining the route taken for a specified IP destination. Try the following and substitute something like www.microsoft.com (or an IP address internal or external to your intranet) to see the IP route traced to the destination.
C:>tracert localServer Tracing route to localServer [142.159.65.17] over a maximum of 30 hops: 1 <10 ms <10 ms <10 ms hostServer [140.140.211.1] 2 <10 ms <10 ms <10 ms localServer [142.159.65.17] Trace complete.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.