On 2013-07-02 20:15, Joel Finlinson wrote:
On Tue, Jul 2, 2013 at 5:30 PM, Corey Edwards <[email protected]> wrote:
Somebody is packet filtering somewhere. I would suggest running both a
traceroute and a TCP traceroute and compare the results (post here if like).
$ traceroute 144.17.90.8
$ tcptraceroute -p 80 144.17.90.8
>
C:\temp>tracert snow.edu
Tracing route to snow.edu [144.17.90.8]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 * 31 ms 36 ms 67.41.239.67
3 31 ms 30 ms 31 ms 67-41-234-17.slkc.qwest.net [67.41.234.17]
4 48 ms 49 ms 49 ms snj-edge-04.inet.qwest.net [67.14.34.82]
5 48 ms 49 ms 50 ms 65.113.32.206
6 72 ms 71 ms 71 ms be6.sc01.sntdcabl.integra.net[209.63.100.125]
7 70 ms 71 ms 66 ms be4.sc01.slkcutxd.integra.net [209.63.82.165
]
8 67 ms 68 ms 67 ms tg9-1.ar10.slkcutxd.integra.net[209.63.114.254]
9 67 ms 68 ms 68 ms 67.136.49.82
10 71 ms 71 ms 72 ms sno-pe-b-155.uen.net [140.197.252.231]
11 144.17.5.10 reports: Destination host unreachable.
Trace complete.
If you don't have a (usable) Linux box from which to run
tcptraceroute, there are two options for Windows:
1) run the old, horribly unmaintained, unreliable tracetcp
2) install nmap and run `nmap -p 80 --traceroute www.snow.edu` (preferred)
As for the traceroute-from-Linux failing miserably, I wonder what your
routing table looks like -- `ip -4 route show` perhaps?
Jima
/*
PLUG: http://plug.org, #utah on irc.freenode.net
Unsubscribe: http://plug.org/mailman/options/plug
Don't fear the penguin.
*/
