Network Troubleshooting Tools PDF
Network Troubleshooting Tools PDF
Network Troubleshooting Tools PDF
Page 1
Using Ipconfig:
1. Log on to the computer as a user with administrative rights.
2. Click Start and select Run (Windows Vista or Windows 7 Click the “Start” button and
type in the “Search for Programs and Files” text box).
3. Type cmd and press ENTER. The black Command Prompt window will appear.
4. Type ipconfig at the command prompt and press ENTER. The following screenshot gives an
example of the information shown when using “ipconfig”.
5. Write down any configuration information you will need. At a minimum, it will be the IP
address of your computer and the Default Gateway.
6. Sometimes you might need more information and you can add the “/all” to the above
“ipconfig” command. This screenshot gives an example of the information shown when
using “ipconfig /all”:
Page 2
Using Ping:
1. Log on to the computer as a user with administrative rights.
2. Click Start and select Run (Windows Vista or Windows 7 Click the “Start” button and
type in the “Search for Programs and Files” text box).
3. Type cmd and press ENTER. The black Command Prompt window will appear.
4. Type ping IP address or domain and press ENTER. If you are unable to ping a destination,
first check to see that there are no typing errors. If the address is correct, use the
Troubleshooting Routing Errors table below to examine what the cause could be.
A successful ping looks similar to this:
Use any or all of the following address options to determine where the connection is failing.
• ping the Ethernet card (NIC) in your computer — this will always be 127.0.0.1
• ping your own computer —use ipconfig to look up the IP address, if necessary.
• ping the Default Gateway (router) — you can find the Default Gateway on the
computer in the same spot as the IP address.
• ping an outside IP address — for example the Level3 DNS Server 4.2.2.2.
• ping a domain name to check DNS — for example: ping www.google.com.
Troubleshooting Ping Errors
Once all of the hardware connections are checked and verified, any of the following could be
the cause of your networking error(s).
Page 3
Using Tracert:
1. Log on to the computer as a user with administrative rights.
2. Click Start and select Run (Windows Vista or Windows 7 Click the “Start” button and
type in the “Search for Programs and Files” text box).
3. Type cmd and press ENTER. The black Command Prompt window will appear.
4. Type tracert IP address or domain and press ENTER.
The following screenshot shows an example using nslookup.
Tracert returns results in milliseconds (ms). Ideally, every hop should give an IP address and
time. After requesting information from the DNS server, the first hop is to the default gateway.
The hop to the default gateway should take 10-20 ms. After that, hops should take anywhere
from 80-120ms. Errors indicated by * on the route can show where there is a lot of network
traffic or possible line problems.
Using Nslookup:
1. Log on to the computer as a user with administrative rights.
2. Click Start and select Run (Windows Vista or Windows 7 Click the “Start” button and
type in the “Search for Programs and Files” text box).
3. Type cmd and press ENTER. The black Command Prompt window will appear.
4. Type nslookup IP address or domain and press ENTER.
The following screenshot shows two examples using nslookup. The first looks up an IP address
(4.2.2.2) while the second looks up a domain
name (www.yahoo.com).
• Server: the local DNS server used to look up the
information.
• Address: the IP address of the local DNS server.
• Name: The domain name of the server hosting the
remote domain or IP.
• Address(s): The IP address(s) of the remote server.
• Aliases: The common name(s) used to identify
multiple IP addresses or domain names.
Page 4