PDA

View Full Version : Traceroute failing to complete tried 3 different DNS serveers




newmacuser23
Jul 4, 2012, 07:11 PM
I am trying to troubleshoot a backup uploading issue and in order to do this I need to run a traceroute to see how the data is traveling from my Mac to the DataCentre.

These are the results.

Google DNS

Traceroute has started…

traceroute: Warning: central.crashplan.com has multiple addresses; using 173.225.132.22
traceroute to central.crashplan.com (173.225.132.22), 64 hops max, 72 byte packets
1 192.168.1.254 (192.168.1.254) 5.799 ms 2.702 ms 1.683 ms
2 217.32.145.135 (217.32.145.135) 22.707 ms 216.284 ms 116.621 ms
3 217.32.145.158 (217.32.145.158) 60.511 ms 869.366 ms 23.114 ms
4 213.120.156.18 (213.120.156.18) 23.760 ms 44.574 ms 42.306 ms
5 217.41.168.177 (217.41.168.177) 26.358 ms 34.587 ms 23.764 ms
6 217.41.168.107 (217.41.168.107) 30.196 ms 55.477 ms 256.023 ms
7 109.159.249.118 (109.159.249.118) 35.547 ms 131.011 ms 80.609 ms
8 core1-te0-7-0-4.faraday.ukcore.bt.net (109.159.249.33) 50.213 ms 106.220 ms 48.977 ms
9 host213-121-193-10.ukcore.bt.net (213.121.193.10) 29.500 ms 55.978 ms 1967.495 ms
10 * core1-pos9-1.telehouse.ukcore.bt.net (194.74.65.114) 49.609 ms 67.093 ms
11 166-49-211-153.eu.bt.net (166.49.211.153) 66.653 ms 32.483 ms 144.143 ms
12 t2a1-ge4-0-0.uk-lon1.eu.bt.net (166.49.135.17) 1360.187 ms 148.915 ms 1553.028 ms
13 te0-3-0-6.ccr21.lon01.atlas.cogentco.com (130.117.14.49) 59.881 ms 28.285 ms 24.936 ms
14 te0-2-0-4.mpd21.lon13.atlas.cogentco.com (154.54.57.94) 265.711 ms 703.149 ms 169.236 ms
15 te0-2-0-4.ccr21.bos01.atlas.cogentco.com (66.28.4.189) 125.934 ms 120.639 ms 164.454 ms
16 te0-5-0-5.mpd21.ord01.atlas.cogentco.com (154.54.28.113) 320.094 ms 178.983 ms 311.376 ms
17 te7-2.ccr01.msp01.atlas.cogentco.com (154.54.84.102) 941.619 ms 221.799 ms 163.621 ms
18 38.104.196.86 (38.104.196.86) 136.051 ms 223.499 ms 189.982 ms
19 69.54.32.233 (69.54.32.233) 185.718 ms 864.032 ms 371.194 ms
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 *

OpenDNS

Traceroute has started…

traceroute: Warning: central.crashplan.com has multiple addresses; using 173.225.132.23
traceroute to central.crashplan.com (173.225.132.23), 64 hops max, 72 byte packets
1 192.168.1.254 (192.168.1.254) 16.639 ms 1.611 ms 1.624 ms
2 217.32.145.135 (217.32.145.135) 29.105 ms 891.345 ms 24.426 ms
3 217.32.145.174 (217.32.145.174) 21.795 ms 21.404 ms 21.666 ms
4 213.120.156.58 (213.120.156.58) 21.985 ms * 29.031 ms
5 217.41.168.177 (217.41.168.177) 33.006 ms 23.122 ms 22.527 ms
6 217.41.168.107 (217.41.168.107) 30.717 ms 25.221 ms 28.614 ms
7 acc1-10gige-0-0-0-5.l-far.21cn-ipp.bt.net (109.159.249.78) 34.551 ms 29.486 ms 81.224 ms
8 core1-te0-0-0-7.faraday.ukcore.bt.net (109.159.249.5) 25.946 ms 22.663 ms 28.745 ms
9 core1-pos0-11-0-0.ealing.ukcore.bt.net (62.172.103.29) 27.176 ms 26.930 ms 35.141 ms
10 transit1-pos1-0-0.telehouse.ukcore.bt.net (62.6.201.82) 36.758 ms 92.485 ms 44.818 ms
11 166-49-211-153.eu.bt.net (166.49.211.153) 34.078 ms 25.273 ms 30.513 ms
12 t2a1-ge7-0-0.uk-lon1.eu.bt.net (166.49.135.49) 24.247 ms 30.281 ms 62.638 ms
13 te0-3-0-6.ccr21.lon01.atlas.cogentco.com (130.117.14.49) 25.020 ms 30.362 ms 24.113 ms
14 te0-1-0-5.ccr21.lon13.atlas.cogentco.com (130.117.1.2) 125.143 ms 120.989 ms 200.777 ms
15 te0-1-0-4.ccr21.bos01.atlas.cogentco.com (154.54.1.93) 137.861 ms 127.215 ms 128.359 ms
16 te0-1-0-7.mpd22.ord01.atlas.cogentco.com (154.54.43.185) 136.835 ms 137.146 ms 123.663 ms
17 te4-8.ccr01.msp01.atlas.cogentco.com (154.54.84.106) 143.332 ms 138.890 ms 138.664 ms
18 38.104.196.86 (38.104.196.86) 168.528 ms 189.868 ms 144.544 ms
19 69.54.32.233 (69.54.32.233) 137.684 ms 142.572 ms 195.584 ms
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 *

ISPs DNS

Traceroute has started…

traceroute: Warning: central.crashplan.com has multiple addresses; using 173.225.132.52
traceroute to central.crashplan.com (173.225.132.52), 64 hops max, 72 byte packets
1 api (192.168.1.254) 3.964 ms 1.896 ms 1.541 ms
2 217.32.145.135 (217.32.145.135) 27.093 ms 21.470 ms 21.725 ms
3 217.32.145.158 (217.32.145.158) 21.950 ms 47.288 ms 25.521 ms
4 213.120.177.10 (213.120.177.10) 22.784 ms 26.693 ms *
5 217.41.168.177 (217.41.168.177) 52.535 ms * 23.148 ms
6 217.41.168.107 (217.41.168.107) 24.868 ms 22.607 ms 23.993 ms
7 109.159.249.112 (109.159.249.112) 22.923 ms 22.343 ms 22.030 ms
8 core1-te0-7-0-7.faraday.ukcore.bt.net (109.159.249.23) 28.723 ms 35.774 ms 30.054 ms
9 host213-121-193-22.ukcore.bt.net (213.121.193.22) 84.745 ms 27.633 ms 27.606 ms
10 core1-pos5-0-0.telehouse.ukcore.bt.net (194.74.65.122) 23.140 ms 28.476 ms 23.263 ms
11 166-49-211-153.eu.bt.net (166.49.211.153) 23.536 ms 32.299 ms 27.653 ms
12 t2a1-ge4-0-0.uk-lon1.eu.bt.net (166.49.135.17) 23.192 ms 36.063 ms 32.719 ms
13 te0-3-0-6.ccr21.lon01.atlas.cogentco.com (130.117.14.49) 32.528 ms 27.766 ms 36.428 ms
14 te0-1-0-5.ccr21.lon13.atlas.cogentco.com (130.117.1.2) 131.475 ms 124.579 ms 133.704 ms
15 te0-0-0-4.ccr21.bos01.atlas.cogentco.com (154.54.5.161) 128.090 ms 152.050 ms 120.436 ms
16 te0-1-0-7.mpd22.ord01.atlas.cogentco.com (154.54.43.185) 120.703 ms 120.671 ms 132.293 ms
17 te4-8.ccr01.msp01.atlas.cogentco.com (154.54.84.106) 138.981 ms 147.221 ms 146.175 ms
18 38.104.196.86 (38.104.196.86) 138.336 ms 147.432 ms 145.431 ms
19 69.54.32.233 (69.54.32.233) 170.769 ms 139.333 ms 139.053 ms
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 *

Anyone got any suggestions on how to correct the issue?



lordj4000
Jul 5, 2012, 01:23 AM
Changing your dns servers doesn't change the ip address the traceroute is connecting to. Remember, the dns name is for you, computers use ip addresses.

Pinging the server you're trying does not return which means that something, a firewall at the border of crashplan's network most likely, is dropping icmp traffic. That is why the traceroute isn't completing and won't complete. This is normal, any server with a firewall in front of it probably drops icmp by default. Usually you have to explicitly allow it.

If you're having trouble backing up i'd contact the company. Maybe look and see if you have any kind of outgoing firewall that might be blocking the ports the backup needs.

newmacuser23
Jul 5, 2012, 09:30 AM
Changing your dns servers doesn't change the ip address the traceroute is connecting to. Remember, the dns name is for you, computers use ip addresses.

Pinging the server you're trying does not return which means that something, a firewall at the border of crashplan's network most likely, is dropping icmp traffic. That is why the traceroute isn't completing and won't complete. This is normal, any server with a firewall in front of it probably drops icmp by default. Usually you have to explicitly allow it.

If you're having trouble backing up i'd contact the company. Maybe look and see if you have any kind of outgoing firewall that might be blocking the ports the backup needs.

While researching the issue I came across what you described (about certain types of traffic being blocked), the reason however why I am still trying to see if I can get the traceroute to work is because others have reported being able to do a successful traceroute when troubleshooting the same issue. I have tried running the traceroute with all my computers firewalls disabled and get the same results.

hwojtek
Jul 5, 2012, 10:18 AM
If one of the routers en route has ICMP traffic blocked, there will be no answer in the traceroute from this router on. However, the target IP may respond if pinged.