Trusted
It seems it wont go past a hop that doesnt respond like tracert does.
Is there a way to make it go past a hop that doesnt respond?
C:\Users\Richard>pathping richms.com
Tracing route to richms.com [202.37.194.80]
over a maximum of 30 hops:
0 DESKTOP3.home.local [192.168.1.45]
1 home.richms.com.richms.com [192.168.1.1]
2 * * *
Computing statistics for 25 seconds...
vs tracert
C:\Users\Richard>tracert richms.com
Tracing route to richms.com [202.37.194.80]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.richms.com.richms.com [192.168.1.1]
2 * * * Request timed out.
3 10 ms 13 ms 9 ms 202.180.81.31
4 8 ms 25 ms 63 ms vlan94-cpcak3-e1.tranzpeer.net [202.180.82.82]
5 9 ms 9 ms 22 ms vlan7-cpcak3-s1.tranzpeer.net [202.180.81.49]
6 18 ms 32 ms 19 ms vibe.ape.net.nz [192.203.154.59]
7 9 ms 28 ms 15 ms richms.com [202.37.194.80]
Trace complete.
C:\Users\Richard>
(yes I know I have a messed up reverse internally on the firewalls internal name)
the hop after it is the adsl router, which for some reason doesnt respond the first time you try to trace/ping anything, but will a second time at least for tracert
C:\Users\Richard>tracert richms.com
Tracing route to richms.com [202.37.194.80]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.richms.com.richms.com [192.168.1.1]
2 * * * Request timed out.
3 9 ms 8 ms 9 ms ^C
C:\Users\Richard>tracert richms.com
Tracing route to richms.com [202.37.194.80]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.richms.com.richms.com [192.168.1.1]
2 12 ms 12 ms 4 ms netgear.home.local [10.20.0.1]
3 10 ms 8 ms 10 ms 202.180.81.31
4 9 ms 8 ms 9 ms vlan94-cpcak3-e1.tranzpeer.net [202.180.82.82]
5 9 ms 9 ms 9 ms vlan7-cpcak3-s1.tranzpeer.net [202.180.81.49]
6 12 ms 12 ms 22 ms vibe.ape.net.nz [192.203.154.59]
7 9 ms 10 ms 10 ms richms.com [202.37.194.80]
Trace complete.
C:\Users\Richard>
