tracert is similar to ping, but it shows each device the packet passes through on its way to the destination. So if you can't connect, it can give you an idea of whether the problem is in your router or your ISP. This shows a successful trace:
C:\Users\jonwi>tracert ftp.homepatrol.com
Tracing route to ftp.homepatrol.com [69.15.51.147]
over a maximum of 30 hops:
1 3 ms 3 ms 12 ms 10.0.0.1
2 41 ms 54 ms 45 ms 96.120.9.209
3 16 ms 63 ms 24 ms te-0-0-0-11-sur02.chambersburg.pa.pitt.comcast.net [162.151.68.165]
4 42 ms 15 ms 83 ms be-8-ar01.lancaster.pa.pitt.comcast.net [69.139.194.53]
5 90 ms 23 ms 26 ms be-34-ar01.mckeesport.pa.pitt.comcast.net [69.139.168.141]
6 74 ms 28 ms 69 ms 4.68.71.133
7 168 ms 100 ms 101 ms ae-3-5.edge5.Dallas3.Level3.net [4.69.208.229]
8 114 ms 91 ms 61 ms CBEYOND-COM.edge5.Dallas3.Level3.net [4.71.120.114]
9 * * * Request timed out.
10 * * * Request timed out.
11 70 ms 108 ms 94 ms mail.dcius.com [69.15.51.147]
Trace complete.
C:\Users\jonwi>
Line 1 is my router.
Line 2 is the ISP device it connects to.
Lines 3-8 are various devices the data travels through on its way.
Lines 9 and 10 block pings and so they didn't respond.
Line 11 is the destination IP address, which apparently has multiple domain registrations.
If there is a blockage, the trace will fail before it gets to the destination. Where it fails will tell you where the problem is.
C:\Users\jonwi>tracert ftp.homepatrol.com
Tracing route to ftp.homepatrol.com [69.15.51.147]
over a maximum of 30 hops:
1 3 ms 3 ms 12 ms 10.0.0.1
2 41 ms 54 ms 45 ms 96.120.9.209
3 16 ms 63 ms 24 ms te-0-0-0-11-sur02.chambersburg.pa.pitt.comcast.net [162.151.68.165]
4 42 ms 15 ms 83 ms be-8-ar01.lancaster.pa.pitt.comcast.net [69.139.194.53]
5 90 ms 23 ms 26 ms be-34-ar01.mckeesport.pa.pitt.comcast.net [69.139.168.141]
6 74 ms 28 ms 69 ms 4.68.71.133
7 168 ms 100 ms 101 ms ae-3-5.edge5.Dallas3.Level3.net [4.69.208.229]
8 114 ms 91 ms 61 ms CBEYOND-COM.edge5.Dallas3.Level3.net [4.71.120.114]
9 * * * Request timed out.
10 * * * Request timed out.
11 70 ms 108 ms 94 ms mail.dcius.com [69.15.51.147]
Trace complete.
C:\Users\jonwi>
Line 1 is my router.
Line 2 is the ISP device it connects to.
Lines 3-8 are various devices the data travels through on its way.
Lines 9 and 10 block pings and so they didn't respond.
Line 11 is the destination IP address, which apparently has multiple domain registrations.
If there is a blockage, the trace will fail before it gets to the destination. Where it fails will tell you where the problem is.