Afficher un message
Vieux 20/03/2006, 21h18   #1
bill@0spam.net
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Odd traceroute behavior involving 4 ISPs

I am having a problem reaching what should be an easily reachable
server going through 4 ISPs. I have no problems pinging or
tracerouting to other hosts on the Internet. The target server is
reachable from just about anywhere except the DSL connection I'm going
through. The route goes through four ISPs: Xspedius, AT&T, Qwest, and
Speakeasy. Each one either states the routing problem is not on their
network or their noc is non-responsive. This has got to be a routing
or subnet mask problem with one of them.

I'm trying to reach 66.93.249.81 (a Speakeasy IP). The trace gets to
the speakeasy network and then dies. The last two hosts in the trace
below (13 and 14) are un-pingable as well:

03/20/06 14:31:35 Fast traceroute mia-c2.0spam.net
Trace mia-c2.0spam.net (66.93.249.81) ...
1 192.168.2.1 1ms 1ms 1ms TTL: 0 (No rDNS)
2 165.236.196.1 9ms 11ms 8ms TTL: 0 (No rDNS)
3 No Response * * *
4 199.227.6.81 16ms 11ms 19ms TTL: 0 (No rDNS)
5 216.85.80.5 33ms 24ms 82ms TTL: 0 (No rDNS)
6 12.119.94.17 44ms 41ms 39ms TTL: 0
(xspedius.fldfl.ip.att.net probable bogus rDNS: No DNS)
7 12.123.33.62 77ms 45ms 50ms TTL: 0 (No rDNS)
8 12.122.12.121 46ms 35ms 52ms TTL: 0
(tbr1-cl1474.attga.ip.att.net probable bogus rDNS: No DNS)
9 12.123.20.201 39ms 54ms 56ms TTL: 0
(br1-a340s8.attga.ip.att.net probable bogus rDNS: No DNS)
10 192.205.33.90 41ms 48ms 48ms TTL: 0 (No rDNS)
11 205.171.21.105 50ms 40ms 34ms TTL: 0
(atl-core-01.inet.qwest.net fraudulent rDNS)
12 205.171.221.18 44ms 51ms 56ms TTL: 0
(atx-edge-01.inet.qwest.net fraudulent rDNS)
13 208.45.200.102 39ms 40ms 51ms TTL: 0 (No rDNS)
14 69.17.82.122 44ms 48ms 43ms TTL: 0
(220.fe-2-3.er1.atl1.speakeasy.net probable bogus rDNS: No DNS)
15 No Response * * *
16 No Response * * *

Similar (yet not exact) routes from public looking glass servers have
no problem. The target server is VERY reachable.

Any suggestions as to where the routing problem is, and once
identified, who to contact so that something will actually get fixed.
I've worked the issue from the Speakeasy and the Xspedius ends, but no
one wants to own this problem. Extremely frustrating.

Thanks in advance. You can email me directly: bill @ 0spam.net

  Réponse avec citation
 
Page generated in 0,05584 seconds with 9 queries