Routing Prob: dslam broken?

Forums » US Telco Support » AT&T » AT&T Midwest » Routing Prob: dslam broken?


Uniqs: 370	Share Topic:	RSS topic:	toggle: flat / full normal / watch	Posting:	Post a:	Post a:

Links: ·Status Page ·FAQ ·SBC Techs ·Anti-virus and spyware

McAfee free to AT&T Yahoo users »
« why does it take so long?

tc60045

@sbcglobal.net

Routing Prob: dslam broken?

I need to connect to a server at 64.75.105.1

Traceroute to this server from Northern Illiinois is unsuccessful:

tcmbp:$ traceroute 64.75.105.1
traceroute to 64.75.105.1 (64.75.105.1), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 1.243 ms 0.985 ms 2.315 ms
2 adsl-75-57-79-254.dsl.emhril.sbcglobal.net (75.57.79.254) 9.801 ms 10.092 ms 11.388 ms
3 dist2-vlan60.emhril.ameritech.net (68.22.72.131) 9.341 ms 10.328 ms 10.847 ms
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
etc.

Can you please take a look at routing to this server and see if there is indeed a broken connection?

Thanks!

permalink · 2008-12-19 11:24:13 · Print ·

psx_defector

join:2001-06-09
Allen, TX

Re: Routing Prob: dslam broken?

If the DSLAM was broken, you wouldn't be posting.

The route is bad:

»network-tools.com/default.asp?pr···75.105.1

»ws.arin.net/whois/?queryinput=N%···ER-BLK-2

Looks like someone didn't setup the subnet right. I was able to hit some other IPs in the block. I would suggest you have Damon Grace, the contact in the ARIN info, get with Time Warner/Road Runner, their ISP, to get the route fixed. This is not an AT&T issue.

permalink · 2008-12-19 11:47:25 · Print ·

TheDuck join:2003-06-22 Eastlake, OH	And if you wait a while for the routes to filter through the DNS servers it will probably clear up.
	permalink · 2008-12-19 14:58:27 ·

Frohike Premium join:2000-07-23 Waxahachie, TX 1 edit	Turn off your modem for 2 minutes. Turn it back on - hopefully you wont get another IP in the same subnet. You have an IP that is not correctly configured in the distribution router. If you pull another IP in the 75.57.x.x range - Power off again. I'll send the IP up to the NOC - not sure how long before they actually get to it. Edited to correct the IP.
	permalink · 2008-12-19 20:31:38 ·

psx_defector join:2001-06-09 Allen, TX	Re: Routing Prob: dslam broken? Dude, even Level3 is seeing the same problem. Nothing can be done from his end. And for disclosure, it's not working as well over 5 different BRAS routers here in Dallas and ATT MIS.
	permalink · 2008-12-19 21:02:17 ·

Frohike Premium join:2000-07-23 Waxahachie, TX	I see what your saying. I thought you tracert to his IP and it was bad. And didn't read last sentence stating it was an AT&T issue.
	permalink · 2008-12-19 21:51:17 ·

scooby Premium join:2001-05-01 Schaumburg, IL	64.75.105.1 is not even being announced thus your traceroute just hangs. IP space needs to be announced so that routers know how to send your traffic to it. I would check with the person who gave you the ip. from route-server.he.net: route-server.he.net> show ip bgp 64.75.105.1 % Network not in table
	permalink · 2008-12-19 22:10:00 ·

your comment..

Forums » US Telco Support » AT&T » AT&T Midwest	McAfee free to AT&T Yahoo users » « why does it take so long?


Friday, 04-Dec 04:37:20	Terms of Use \| Privacy Policy \| Hosting by www.nac.net - DSL,Hosting & Co-lo \| feedback \| contact over 10 years online! © 1999-2009 dslreports.com. page compression OFF