dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1280
share rss forum feed

Robbord

join:2004-03-04

[DSL] Strange problem - can't access server/website

I can't access peach.nocdirect.com/cpanel. When I do a tracert, it just dies:

Tracing route to peach.nocdirect.com [69.73.168.158]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms ATOMIC [192.168.1.1]
2 7 ms 7 ms 7 ms adsl-99-107-167-254.dsl.lsan03.sbcglobal.net [99
.107.167.254]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.

If I do it from an online traceroute on a different network, it works.

hop ip address fully qualified domain name
1 70.84.211.97 61.d3.5446.static.theplanet.com
2 70.87.254.1 po101.dsr01.dllstx5.networklayer.com
3 70.85.127.105 po51.dsr01.dllstx3.networklayer.com
4 173.192.18.224 ae16.bbr01.eq01.dal03.networklayer.com
5 173.192.18.209 ae7.bbr02.eq01.dal03.networklayer.com
6 173.192.18.135 ae1.bbr01.tl01.atl01.networklayer.com
7 198.32.132.69
8 74.119.144.158
9 209.140.17.62
10 69.73.168.158 peach.nocdirect.com

I get the same problem when I use the IP address instead of the domain name.

My host, JaguarPC, moved me on to a new server. I've been trying to access it by the domain name or IP address but it just doesn't work. I'm perplexed. I've never encountered this problem before. I'm very curious as to the reason and solution. Thanks for your help!


dslx_nick
Premium,VIP
join:2011-12-24
Chatsworth, CA
kudos:29

1 recommendation

Hey Robbord,

That looks like a backbone routing issue; you're able to reach the gateway, but traffic's not passing beyond that. I assume you're able to access other websites just fine, right? Send me an IM with your account info, if you would.

Robbord

join:2004-03-04
said by dslx_nick :
I assume you're able to access other websites just fine, right?
Yes... I can connect to other websites just fine. I have no other known networking problems. I live in Anaheim, CA. I have a friend who lives near San Diego. (I think Cardiff by the Sea or Solana Beach) He has AT&T DSL and has the same problem.

Backbone routing problem eh? Sounds interesting! Thanks for your help Nick! Let me know what you find out...

Robbord

join:2004-03-04

3 edits
reply to Robbord
More debugging info...
---------------

My information (Rob - DSL Extreme Customer):

Tracing route to peach.nocdirect.com [69.73.168.158]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms ATOMIC [192.168.1.1]
2 7 ms 7 ms 7 ms adsl-99-103-155-254.dsl.lsan03.sbcglobal.net [99
.103.155.254]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.

Tracing route to peach.nocdirect.com [69.73.169.50]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms ATOMIC [192.168.1.1]
2 7 ms 7 ms 7 ms adsl-99-103-155-254.dsl.lsan03.sbcglobal.net [99
.103.155.254]
3 11 ms 11 ms 7 ms 12.83.98.249
4 32 ms 7 ms 8 ms la2ca03jt.ip.att.net [12.122.84.201]
5 8 ms 8 ms 8 ms 192.205.35.6
6 8 ms 8 ms 8 ms te0-4-0-3.ccr22.lax01.atlas.cogentco.com [154.54
.88.194]
7 8 ms 45 ms 46 ms te0-2-0-3.mpd22.iah01.atlas.cogentco.com [154.54
.45.9]
8 51 ms 70 ms 57 ms te0-2-0-2.ccr22.atl01.atlas.cogentco.com [154.54
.42.214]
9 58 ms 57 ms 58 ms te0-0-0-0.ccr21.atl01.atlas.cogentco.com [154.54
.45.29]
10 58 ms 58 ms 58 ms 38.122.18.211
11 57 ms 57 ms 57 ms 206.220.172.26
12 68 ms 58 ms 57 ms 184.170.248.170
13 57 ms 57 ms 57 ms 209.140.17.58
14 76 ms 72 ms 58 ms peach.nocdirect.com [69.73.169.50]

Trace complete.

--------------------

Friend Ron (AT&T customer)

Tracing route to peach.nocdirect.com [69.73.168.158]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.254
2 11 ms 13 ms 10 ms bras7-l0.sndgca.sbcglobal.net [151.164.184.154]

3 9 ms 10 ms 9 ms dist1-vlan50.sndg02.pbi.net [63.200.206.130]
4 10 ms 25 ms 11 ms 12.83.70.161
5 ded3-g4-3-0.sfldmi.ameritech.net [151.164.40.106] reports: Destination hos
t unreachable.

Trace complete.

Tracing route to peach.nocdirect.com [69.73.169.50]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms 192.168.1.254
2 10 ms 12 ms 30 ms bras7-l0.sndgca.sbcglobal.net [151.164.184.154]

3 11 ms 9 ms 10 ms dist1-vlan50.sndg02.pbi.net [63.200.206.130]
4 13 ms 11 ms 11 ms 12.83.70.153
5 25 ms 13 ms 13 ms la2ca02jt.ip.att.net [12.123.30.189]
6 14 ms 16 ms 14 ms xe-0-1-1.mpr1.lax12.us.above.net [64.125.12.1]
7 18 ms 14 ms 14 ms xe-2-2-0.cr2.lax112.us.above.net [64.125.31.194]

8 51 ms 58 ms 60 ms xe-3-2-0.cr2.iah1.us.above.net [64.125.30.49]
9 82 ms 61 ms 62 ms xe-1-1-0.mpr3.atl6.us.above.net [64.125.31.49]
10 134 ms 61 ms 62 ms xe-1-0-0.mpr1.atl1.above.net [64.125.22.145]
11 61 ms 61 ms 62 ms 208.185.20.126.IPYX-063451-ZYO.above.net [208.18
5.20.126]
12 63 ms 61 ms 62 ms 184.170.245.254
13 66 ms 62 ms 61 ms 209.140.17.62
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.


sashwa
Premium,Mod
join:2001-01-29
Alcatraz
kudos:18

1 recommendation

It is not a good idea to post private information on this board as it is a public board.

I pm'd your IP addresses and your friend's to Nick.


dslx_nick
Premium,VIP
join:2011-12-24
Chatsworth, CA
kudos:29

1 recommendation

WELL.

Took a fair bit of digging and getting bounce from department to department... but finally got to the bottom of what's going on.

AT&T's got that IP in a 'black hole'. Basically, AT&T suspects someone from that IP of some less-than-kosher activity, and as a result will not route traffic to or from that IP. It's not that AT&T CAN'T route traffic to/from that IP, but WON'T.

At this point, JaguarPC needs to send an email to netsec@att.net to plead their case and get removed from the black hole (kind of like requesting to be removed from a spam blacklist, but this is entirely on AT&T's network, not a public blacklist).

Robbord

join:2004-03-04
Thanks for all your help Nick! Looks like JaguarPC pleaded their case to AT&T and AT&T bought it. I can finally get to my server!

Tracing route to peach.nocdirect.com [69.73.168.158]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms ATOMIC [192.168.1.1]
2 7 ms 7 ms 7 ms adsl-99-103-155-254.dsl.lsan03.sbcglobal.net [99.103.155.254]
3 9 ms 11 ms 11 ms 12.83.98.249
4 8 ms 8 ms 8 ms la2ca02jt.ip.att.net [12.123.30.17]
5 8 ms 7 ms 7 ms xe-9-2-0.lax30.ip4.tinet.net [77.67.79.173]
6 58 ms 58 ms 58 ms xe-9-2-0.atl11.ip4.tinet.net [141.136.109.205]
7 58 ms 58 ms 58 ms total-server-solutions-gw.ip4.tinet.net [173.241.130.54]
8 58 ms 59 ms 59 ms 206.220.172.26
9 58 ms 58 ms 58 ms 184.170.248.170
10 58 ms 58 ms 58 ms 209.140.17.58
11 59 ms 59 ms 59 ms peach.nocdirect.com [69.73.168.158]

Trace complete.

Finally... Thanks again!


dslx_nick
Premium,VIP
join:2011-12-24
Chatsworth, CA
kudos:29
Great, glad to hear it