43HERE, WE WILL LOOK AT THE TWO MAIN TOOLS YOU MIGHT USE IN TROUBLES...

3.43Here, we will look at the two main tools you might use in troubleshooting IP routing andthe common problems that occur with IP routing, which you will be expected to knowhow to deal with in the exam.

N

OTEThere are entire books devoted to troubleshooting IP routing. Also, Microsoft’sonline help system is fairly good at suggesting probable causes and solutions formany common routing problems.

Identifying Troubleshooting Tools

Your best troubleshooting tools are those tools you should be using on a daily basis for net-work management and monitoring.Windows Server 2003 ships with the Network Monitortool (NETMON.exe), which is an excellent protocol analyzer that you can use to monitoryour network. As discussed in Chapter 3, this tool captures and displays information aboutthe IP packets moving in your network and can tell you about traffic patterns, broadcastrates, how the network is being used, what kinds of errors you might be experiencing, andmany other aspects concerning the behavior of your network.The Routing and Remote Access console is another excellent troubleshooting tool.Using this tool, you can show your network’s TCP/IP information, your IP routing table,the router’s RIP neighbors, its OSPF area, the LSDB, the router’s OSPF neighbors, and theOSPF virtual interface.Other familiar tools that you can use for troubleshooting include PING, pathping,tracert, mrinfo, and netsh. Let’s take a look at how you can these tools to verify and trou-bleshoot your connections.

Testing your TCP/IP Connections with PING

To use PING to test your TCP/IP connections, follow these steps: