PathPing

Windows 2000 includes a utility called PathPing for troubleshooting network problems. It's a route tracing tool that combines features of the ping and tracert commands with additional information that neither of those commands provides. I've played around with it a bit, looks like it might be worthwhile. Has anyone used it?

For a better description and switch info, see Windows 2000 help

I have used it, works about the same as a tracert.
guess it is a "feature" that they decided to add, that had no real point other than to combine the two together in one utility

C:\>pathping

Usage: pathping [-n] [-h maximum_hops] [-g host-list] [-p period]
[-q num_queries] [-w timeout] [-t] [-R] [-r] target_name

Options:
-n Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-g host-list Loose source route along host-list.
-p period Wait period milliseconds between pings.
-q num_queries Number of queries per hop.
-w timeout Wait timeout milliseconds for each reply.
-T Test connectivity to each hop with Layer-2 priority tags.

-R Test if each hop is RSVP aware.

--------------------------------------------
--------------------------------------------

C:\>tracert

Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout] target_name

Options:
-d Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-j host-list Loose source route along host-list.
-w timeout Wait timeout milliseconds for each reply.


they added a few features..

I'm not sure how useful.

tracert is used for fast troubleshooting..

if I need something better I use dedicated network analayzers.. such as the ones from fluke..

Traceroute gets back the response from the INCOMING interface which gets the request at the next hop...
As I know other ping options from routers, this pathping will probably do just the same... it sends back the response from the OUTGOING interface at the next hop, where the packet is sent further...

The major difference is the information when troubleshooting network setups... you can get an answer with traceroute from a direct connected next-hop-routers interface (as it IS on the same network like you), but if it's configured wrong, you won't get an answer from the outgoing interface of the next-hop (as it will surely be on a different network).

I work for a web hosting company and when ever there a connectivity issue to the server I would always tell them to use the tracert > trace.tx command and attachit to a message. However since the new util came out I have been giving the following command pathping > trace.txt coomand. It helps out the Network Ops people when resolving issues.