much better:
C:\>tracert 44.60.44.10
Tracing route to
kb3vwg-010.ampr.org [44.60.44.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms
xtm520.wa4zlw.homedns.org [10.161.51.3]
2 1 ms <1 ms <1 ms
core100.wa4zlw.ampr.org [44.56.53.1]
3 19 ms 18 ms 19 ms
kb3vwg-001.ampr.org [44.60.44.1]
4 19 ms 18 ms 19 ms
kb3vwg-010.ampr.org [44.60.44.10]
Trace complete.
C:\>tracert 71.163.244.98
Tracing route to
pool-71-163-244-98.washdc.fios.verizon.net [71.163.244.98]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms
xtm520.wa4zlw.homedns.org [10.161.51.3]
2 * * * Request timed out.
3 9 ms 8 ms 8 ms
gateway-t2-1-flt3blocal1.flt.ptd.net
[207.44.126.57]
4 19 ms 16 ms 17 ms
te0-11-0-6.ccr41.iad02.atlas.cogentco.com [38.122.63.197]
5 16 ms 16 ms 16 ms
verizon.iad02.atlas.cogentco.com
[154.54.10.198]
6 * * * Request timed out.
7 18 ms 18 ms 20 ms
ae204-0.WASHDC-VFTTP-352.verizon-gni.net
[100.41.220.79]
8 18 ms 18 ms 21 ms
pool-71-163-244-98.washdc.fios.verizon.net [71.163.244.98]
Trace complete.
C:\>
On 5/30/2017 4:47 PM, lleachii--- via 44Net wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Ok, traceroute should work (except for 1 hop controlled by my Carrier).
---
This email has been checked for viruses by AVG.
http://www.avg.com