How can you identify the intermediate nodes along the path using ping ONLY

microsoft.public.windows.networking.wireless

2 Aug 2006 3:49 PM

aamircheema

Hi,

Is this possible to identify intermediate nodes by using pin command
olnly? Somebody told me that it is. Can anyone please elaborate how?

Thanks,
Aamir

2 Aug 2006 4:54 PM

Greg Lindsay [MSFT]

Hi Aamir,

I believe you are talking about the "record route" (-r) option in ping.

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/ping.mspx?mfr=true

For example, "ping -r 9 -n 1 x.x.x.x" will send one echo request to x.x.x.x
and "trace" up to 9 hops along the way.

You can also use pathping and tracert.

I hope this helps!

--
Greg Lindsay [MSFT]
greg.lind***@microsoft.com

Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

<aamirche***@gmail.com> wrote in message

Show quoteHide quote

news:1154533771.407466.56500@h48g2000cwc.googlegroups.com...
> Hi,
>
> Is this possible to identify intermediate nodes by using pin command
> olnly? Somebody told me that it is. Can anyone please elaborate how?
>
> Thanks,
> Aamir
>

3 Aug 2006 10:09 PM

Jaffser

Yes indeed, the Pathping and Tracert functions are quite useful. I was able
to identify where there was a bottleneck in the traffic from end user out
through our VPN to global sites. It was good to be able to point the finger
at someone else and clearly identify that the device causing the problems is
not under your control.

Use the syntax: Pathping/Tracert (www.?.?) to ping to a server outside if
you do not have a specific address to ping to.

The only drawback is the delay repeating the function due to the amount of
packets being sent out per hop.

Otherwise, fab tools.

Jaf