MCSE Boot Camp by MCSE Camp MCSE $3750,CCNA $1500
MCSE Boot Camp by MCSE Camp 98% Success Ratio           
MCSE Boot Camp by MCSE Camp Boot Camp Since 1999
      

Get Certify Get Ahead

MCSE Boot Camp Schedule Schedule  MCSE Boot Camp FAQ FAQ  MCSE Boot Camp Vibrant Why Vibrant   MCSE Boot Camp location Location                                                                                                                                                   

Leading MCSE, CCNA, CCNP Certification boot camp training provider in India, USA, UK.

 

[Contents] [Back] [<< Prev] [Next >>]

Pinging a Remote Host

As a final test in using Ping, you can Ping the IP address of a remote host, a computer on another subnet, or even the IP address of a Web server or FTP server on the Internet. If you can successfully Ping a remote host, your problem doesn’t lie with the IP configuration; you are probably having trouble resolving host names. Figure 16.26 shows the results of a successful remote host Ping, in this case a Web server at Microsoft. Figure 16.27 shows a failed remote host Ping.

If Pinging the remote host fails, your problems may be with the router, the subnet mask, or the local IP configuration. However, if you have followed the earlier steps of Pinging the loopback, local host address, and the default gateway address, you have already eliminated many of the problems that could cause this Ping to fail.

When a remote host Ping fails after you have tried the other Ping options, the failure may be due to other routers beyond the default gateway used for your subnet. If you know the physical layout of your network, you can Ping other router addresses along the path to the remote host to see where the trouble lies. Remember to Ping the addresses on both sides of the router: the address that receives the packet and the address that forwards the packet on. You can also use the Route command, as described in the following section, to find the path used to contact the remote host.

It is also possible that there is not a physical path to the remote host due to a router crash, a disruption in the physical network, or a crash on the remote host.


[note.gif]

Many troubleshooters prefer to simply try this last step when using Ping to troubleshoot IP configuration and connectivity. If you can successfully Ping a remote host, then the other layers of TCP/IP must be working correctly. In order for a packet to reach a remote host, IP must be installed correctly, the local client address must be configured properly, and the packet must be routed. If a Ping to the remote host works, then you can look to other sources (usually name resolution) for your connection problems. If the Ping fails, you can try each preceding step until you find the layer where the problem is located. Then you can resolve the problem at this layer. Figure 16.28 shows the methodology used to test IP with Ping. You can either start by Pinging the loopback address and working up through the architecture, or you can Ping the remote host. Of course, if Pinging the remote host works you can stop. If not, you can work back through the architecture until you find a layer where Ping succeeds. The problem must therefore be at the next layer.

 Vibrant Advantage :

MICROSOFT Training PartnerMCSE Camp No Prestudy
MCSE Camp Longest Duration Camp
MCSE Camp Chalk Talk TrainingRed Hat Training Partner
MCSE Camp Highest Passing Rate
MCSE Camp Bootcamp since 1999
MCSE Camp Guaranteed Certification ...

Testimonials :

MCSE Certification boot camp

The instructor taught real world experience and did not just teach us to pass the test. He knew the subject well and was encouraging. His lectures were very well delivered....

Colver Dennis, USA 

 | MCSE Boot Camp India | MCSE Camp UKMCSE CampMCSE Camp USAMCSE Camp|MCSE CampIndia InformationMCSE Camp|MCSE CampCard PaymentMCSE Camp|MCSE CampSite MapMCSE Camp|MCSE CampContactMCSE Camp|MCSE CampHomeMCSE Camp ref1 | Ref2 | RHCE | RHCT | Redhat | RHCE / RHCT | RHCE Boot Camp
© Copyright 2007 MCSE Camp