>Hmmm. Pretty weird. Can't ping them from the server and the last hop in a
>tracert is:
>
>216.87.89.190 gi41.applecore.den.viawest.net
>
>When I do a tracert from home it hits that address also but keeps on
>going. Wouldn't it take the same route from that point from either place?
>It's like 3 hops from the destination.
It *should* take the same route. It sounds like one of two things is
happening:
[1] 216.87.89.190 is accepting your ICMP packets, and responding to the
TTL expiring, but then dropping any further packets into the bit
bucket. I'd guess this is unlikely
[2] The first hop after 216.87.89.190 is simply dropping the packets, not
even responding to the TTL expiring. I'm guessing this is it: If you're
dropping packets for some reason, it would be dumb to reply to the TTL
expiring.
The problem now is figuring out why that router is blocking packets from
your server. The router after 216.87.89.190 appears to be run by
neighborhoodlink.com. However, the router after it is reporting itself as
10.10.10.2, which is a private IP address, and I'm sure it's a major
violation for a router on the Internet to use a private IP address like
that (internally, it could be 10.10.10.2 -- but there is no way to ping
that router from the Internet, for example). So it sounds like they don't
have much of a clue over there.
-Scott
---
Declude: Anti-virus, Anti-spam and Anti-hijacking solutions for
IMail. http://www.declude.com
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
An Archive of this list is available at:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
