Code: Select all
Microsoft Windows [Version 10.0.18362.388]
(c) 2019 Microsoft Corporation. All rights reserved.
C:\Users\Wulfraed>ping pi-star-3b
Pinging pi-star-3b.attlocal.net [192.168.1.79] with 32 bytes of data:
Reply from 192.168.1.79: bytes=32 time=2ms TTL=64
Reply from 192.168.1.79: bytes=32 time=2ms TTL=64
Reply from 192.168.1.79: bytes=32 time=2ms TTL=64
Reply from 192.168.1.79: bytes=32 time=2ms TTL=64
Ping statistics for 192.168.1.79:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2ms, Average = 2ms
C:\Users\Wulfraed>tracert pi-star-3b
Tracing route to pi-star-3b.attlocal.net [192.168.1.79]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms pi-star-3b.attlocal.net [192.168.1.79]
Trace complete.
C:\Users\Wulfraed>
Google searches also state that tracert goes all the way back to Win95.
Hmmm, never knew about Windows pathping before reading https://en.wikipedia.org/wiki/Traceroute
Code: Select all
C:\Users\Wulfraed>pathping pi-star-3b
Tracing route to pi-star-3b.attlocal.net [192.168.1.79]
over a maximum of 30 hops:
0 ElusiveUnicorn.attlocal.net [192.168.1.66]
1 pi-star-3b.attlocal.net [192.168.1.79]
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 ElusiveUnicorn.attlocal.net [192.168.1.66]
0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% pi-star-3b.attlocal.net [192.168.1.79]
Trace complete.
C:\Users\Wulfraed>