menu home menu services menu help menu radio menu youtube video menu news menu friends menu search menu directions menu end cap

Network Troubleshooting and Problem Resolution Procedure

Back to Step 3.

STEP 4, STEP 5 and STEP 6

STEP 4 -- Run PING 192.168.n.1 to your network Gateway – Router.

Next try the PING command. Use the number from IPCONFIG /ALL for n in the command. Proper response is shown below. The n=30 in my network.

   C:\Documents and Settings\Pete>ping 192.168.30.1

   Pinging 192.168.30.1 with 32 bytes of data:

   Reply from 192.168.30.1: bytes=32 time<1ms TTL=64
   Reply from 192.168.30.1: bytes=32 time<1ms TTL=64
   Reply from 192.168.30.1: bytes=32 time<1ms TTL=64
   Reply from 192.168.30.1: bytes=32 time<1ms TTL=64

   Ping statistics for 192.168.30.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
   Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

   C:\Documents and Settings\Pete>

The 192.168.n.1 address is typically the Default Gateway or network router address.

   Default Gateway . . . . . .: 192.168.30.1
   DHCP Server . . . . . . . . . .: 192.168.30.5
   DNS Servers . . . . . . . . . .: 192.168.30.5
                                    151.196.0.38
                                    71.252.0.71
                                    151.203.0.86
                                    192.168.30.20

It should always respond to the PING command. A response says that your internal network is working properly.

No response suggests that there is an internal network problem.�This could be network hardware, a firewall blocking responses, or a higher layer software problem.

   C:\Documents and Settings\Pete>ping 192.168.30.1

   Pinging 192.168.30.1 with 32 bytes of data:

   Request timed out.
   Request timed out.
   Request timed out.
   Request timed out.

   Ping statistics for 192.168.30.1:
   Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
   C:\Documents and Settings\Pete>

First check the network connections, and then try the PING command using another PC to see that it is working. If the PING command works on another PC, the problem lies in the subject PC.

When the PING command gives the proper response for IP addresses within your network, then you need to test to see if you can get a response from the Internet.

STEP 5 -- Run PING www.dialanerd.com to an Internet Site say DialANerd.com.

   C:\Documents and Settings\Pete>ping www.dialanerd.com

   Pinging dialanerd.com [173.69.132.44] with 32 bytes of data:

   Reply from 173.69.132.44: bytes=32 time=1ms TTL=63
   Reply from 173.69.132.44: bytes=32 time=1ms TTL=63
   Reply from 173.69.132.44: bytes=32 time=1ms TTL=63
   Reply from 173.69.132.44: bytes=32 time=1ms TTL=63

   Ping statistics for 173.69.132.44:
     Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
   Approximate round trip times in milli-seconds:
     Minimum = 1ms, Maximum = 1ms, Average = 1ms

   C:\Documents and Settings\Pete>

Proper response says that your PC is connected to the Internet at the lower networking layers. �This means that your PC's Network Interface Card (NIC), the network (Ethernet) cable, any internal network hardware connecting you to your Internet Gateway - Router, the Internet Gateway - Router, and the Internet Service Provider (ISP) communications facilities connecting you to the Internet are all working.

When running PING to DialANerd does not work and .COM sites do not work or try this site.

   C:\Documents and Settings\Pete>ping 151.196.0.38

   Pinging 151.196.0.38 with 32 bytes of data:

   Reply from 151.196.0.38: bytes=32 time=10ms TTL=249
   Reply from 151.196.0.38: bytes=32 time=9ms TTL=249
   Reply from 151.196.0.38: bytes=32 time=9ms TTL=249
   Reply from 151.196.0.38: bytes=32 time=9ms TTL=249

   Ping statistics for 151.196.0.38:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
   Approximate round trip times in milli-seconds:
    Minimum = 9ms, Maximum = 10ms, Average = 9ms

   C:\Documents and Settings\Pete>

This site is an old Bell Atlantic DOMAIN NAME SERVICE (DNS) server. DNS computers respond to PING commands. Domain Name Service translates web site names into their IP addresses, similar to the telephone book translating our name into our telephone number.� It is possible that the DIALANERD name to address translation is not working somewhere in the Internet or in your PC. Alternatively, this site may be down. Using the PING command to a specific IP address would bypass that translation step.�

STEP 6 -- Run TRACERT www.dialanerd.com to an Internet Site say DialANerd.com.

   C:\Documents and Settings\Pete>tracert www.dialanerd.com

   Tracing route to dialanerd.com [173.69.132.44]
   over a maximum of 30 hops:

   1�<1 ms�<1 ms�<1 ms static-72-81-252-76.bltmmd.fios.verizon.net [173.69.132.44]
   2�<1 ms�<1 ms�<1 ms static-72-81-252-76.bltmmd.fios.verizon.net [173.69.132.44]


   Trace complete.

   C:\Documents and Settings\Pete>

REVIEW

If the PING command works and the TRACERT command works, you have sent information to the INTERNET and received a response. You are connected to the Internet. This does not guarantee that your web browser surfs the web properly because there could be software corruption at higher layers.

===========Internal Local Area Network (LAN) =====|======Internet=====

YOUR PC ======= > YOUR INTERNET GATEWAY ======== > INTERNET WEB SITE

192.168.n.n ===== > 192.168.n.1 ===================== > 173.69.132.44

When you have several PCs in your facility and one of them connects to and works on the Internet properly, then it means that one PC, the connection to the Router, the Router, the ISP connection to the Internet and the Internet are all working. The PCs that are not working have problems connecting to the Router and to the Internet. If Steps 1, 2, 3, 4, 5, and 6 all work on those PCs then there is a software problem at the higher layers. If the steps fail, they should permit you to pin point the problem and resolve it PC by PC.

I hope that this helps. Questions please call.

Wireless connections can use many of these basic procedures, but they have additional considerations. Higher layer problems need to be discussed as well. Finally, Vista presents its own unique problems that are extremely frustrating when Internet connectivity fails. We hope to address these problems as well in subsequent postings.

Please Click Here to return to the Help Page.

� 2000-2013 P. D. Moulton

Link to Network Troubleshooting

� 2000-2013 P. D. Moulton
DialANerd
7146 Rivers Edge Road Columbia, MD 21044 US
Phone: 410-531-5890 Website: dialanerd.com

DialANerd Columbia, MD Network Troubleshooting and Problem Resolution Procedure - Steps 4, 5, and 6