> traceroute can't get to that IP address, so I'm pretty sure the corporate
> firewall is doing its job.
traceroute failure just means that someone is not passing icmp
traffic. the only thing you know is icmp traffic won't pass.
here's a dirty trick you can do with plan 9 traceroute:
; ip/traceroute /net/tcp!minooka.coraid.com
trying /net/tcp!12.51.113.6!32767
round trip times in µs
low avg high
--------------------------
192.168.0.64 175 243 376
192.168.1.254 320 386 509
65.14.248.28 19621 20117 20711
74.253.143.53 21151 22002 22685
205.152.99.98 21649 22016 22468
65.83.238.74 21693 22098 22641
65.83.238.194 22661 23113 23896
12.122.140.198 23143 23939 24520 cr2.attga.ip.att.net
12.122.140.45 169904 201516 222315 gar19.attga.ip.att.net
12.87.45.86 26855 27417 28069
12.51.113.6 26376 26949 27493
by the way, plan 9 dns query tends to do poorly
with rfc2672-style reverse ips. it tends to quit on
the cname.
- erik
