reub2000
Premium
join:2001-12-28
Evanston, IL
| reply to reub2000
Re: How come I can't access this site?
Here is my traceroute:
traceroute to www.npmoc.navy.mil (199.10.200.33), 30 hops max, 40 byte packets
1 172.31.255.251 (172.31.255.251) 29.484 ms 23.590 ms 26.049 ms
2 192.168.24.49 (192.168.24.49) 13.567 ms 15.179 ms 12.282 ms
3 ge-8-0-169.ipcolo2.Chicago1.Level3.net (63.210.100.197) 12.567 ms 13.081 ms 14.757 ms
4 ae-24-56.car4.Chicago1.Level3.net (4.68.101.168) 12.072 ms 11.908 ms 12.275 ms
5 * sprint-level3-oc48.Chicago1.Level3.net (209.0.225.22) 11.250 ms 20.669 ms
6 sl-bb20-chi-4-0.sprintlink.net (144.232.8.218) 14.766 ms 16.246 ms 13.515 ms
7 sl-bb23-chi-9-0.sprintlink.net (144.232.26.54) 13.293 ms 13.561 ms 15.745 ms
8 sl-bb24-chi-15-0.sprintlink.net (144.232.26.101) 15.281 ms 13.308 ms 18.936 ms
9 sl-bb20-che-2-0.sprintlink.net (144.232.20.161) 32.267 ms 32.563 ms 31.971 ms
10 sl-bb21-che-15-0.sprintlink.net (144.232.15.142) 31.506 ms 31.022 ms 31.778 ms
11 sl-bb22-stk-6-0.sprintlink.net (144.232.20.141) 78.088 ms 75.834 ms 76.095 ms
12 sl-bb20-prl-9-1.sprintlink.net (144.232.8.45) 123.193 ms 121.596 ms 121.171 ms
13 sl-gw2-prl-0-0.sprintlink.net (144.232.30.22) 122.176 ms 121.980 ms 121.743 ms
14 sl-timewarner-12-0.sprintlink.net (160.81.200.214) 136.137 ms 169.016 ms 135.412 ms
15 216-136-8-79.static.twtelecom.net (216.136.8.79) 134.972 ms 134.092 ms 135.710 ms
16 66-162-246-34.static.twtelecom.net (66.162.246.34) 136.969 ms 136.029 ms 137.984 ms
17 140.45.122.57 (140.45.122.57) 135.119 ms 134.934 ms 135.734 ms
18 140.45.122.18 (140.45.122.18) 135.224 ms 135.431 ms 135.292 ms
19 140.45.1.49 (140.45.1.49) 137.348 ms 136.675 ms 136.883 ms
20 * * *
21 * * *
22 * * *
23 * * *
24 * *
quote:
Also, make sure some form of content filtering isn't the problem - try the main site, »www.npmoc.navy.mil/ It's also working here.
I don't have any content filtering.
--
My pbase gallery |
|
Bill_MI
Bill In Michigan
Premium,MVM
join:2001-01-03
Royal Oak, MI
 ·Comcast
1 edit | Since you're getting very close to the site, it can't be routing on our end of this. There must be something close to the site filtering your IP - this is not uncommon for *.MIL sites (they think your address may be overseas).
To compare apples and apples, here's my regular (UDP) traceroute starting at YOUR hop 17 (MY hop 19):
19 140.45.122.57 (140.45.122.57) 151.749 ms 153.984 ms 152.721 ms
20 140.45.122.18 (140.45.122.18) 151.503 ms 151.922 ms 151.518 ms
21 140.45.1.49 (140.45.1.49) 153.712 ms 152.440 ms 154.219 ms
22 198.26.171.82 (198.26.171.82) 158.384 ms 154.885 ms 156.410 ms
23 * * *
24 * * *
25 * * *
Now, running tcptraceroute I can get the entire path. It's a nifty tool for just this:
19 140.45.122.57 151.412 ms 150.697 ms 151.923 ms
20 140.45.122.18 150.934 ms 152.371 ms 151.691 ms
21 140.45.1.49 154.620 ms 153.826 ms 153.644 ms
22 198.26.171.82 158.408 ms 155.824 ms 156.128 ms
23 net8host130.cpf.navy.mil (199.124.8.130) 157.581 ms 154.588 ms 156.857 ms
24 www.npmoc.navy.mil (199.10.200.33) [open] 157.576 ms 159.292 ms 162.261 ms |
|
