Why can't I "pathping" ?

[stoofa]

Hi guys,
I'm aware of what the "pathping" command should allow me to do and I know, in the past I've been able to run it without an issue. However I cannot remember what router I was using, what OS I was using when it did all "just work".
So I'm using Win10 and I'm using a BT HH3. Command prompt opened with "administrator" privileges.
If I used the command: pathping -n xxx.xxx.xxx.xxx (any IP address you like) I get the following:

C:\>pathping -n 134.170.185.46

Tracing route to 134.170.185.46 over a maximum of 30 hops

0 192.168.1.82
1 192.168.1.254
2 * * *
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 192.168.1.82
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.254

Trace complete.

So in other words we have hop 0 which is my PC, we have hop 1 which is the router (BT HH3) and that is it. It always fails to get a hop 2 (as above) and then just processes the results to the HH (not much use when I'm trying to find an issue on a path elsewhere).
I'm on BT Infinity 2 as my ISP.
Any idea what is going on?
The abvoe happens no matter what IP address I try to get through to, so something BT are stopping me from doing?

Ta

 

[philip2009]

I've only been on BT for a couple of days so haven't looked into this before ... my pathping on Infinity also only displays the first couple of entries, mtr on a Linux VM also just gives the first couple of entries - WinMTR works OK.

 

[stoofa]

Thanks for the link to that app - working fine.
I can see the first couple of hops don't respond - I think that's why "pathping" fails.

Cheers.

 

[philip2009]

I'm not an expert on these things but perhaps it builds a list of hosts until it gets a "port unreachable" reply, wondering whether the hosts in the early hops are giving "port unreachable" rather than "time-to-live exceeded"? So you end up with a truncated hosts list for pathping.