Slashdot Mirror

← Back to Stories (view on slashdot.org)

Some People @Home, Some Not @Home

Posted by ryuzaki0 on from the hey-brother-can-you-spare-a-dialup dept.

11thangel writes: "Dotcomscoop is reporting that Excite@home has released a statement saying that they have discontinued service to AT&T, as it's certain negotiations will be fruitless. All others are still at the bargaining table. Earlier statements indicated that an example would be made out of one provider, AT&T being the obvious target. Everyone else keep your fingers crossed." There's a Reuters story about AT&T being unplugged. Various submissions have noted that some people who still have connectivity have lost their DNS servers. Just add "64.28.67.150 slashdot.org" to your hosts file and you should be good to go. :)

20 of 513 comments (clear)

  1. I'm back online by XBL · · Score: 5, Informative

    I'm here in Iowa (under AT&T @Home), and my DNS has been down all day. It came back up an hour ago.

    My mail server reports that my account doesn't exist :-(

    Overall, I am impressed how AT&T has moved all its customers off Excite and onto their own network... I dunno how they did it.

    1. Re:I'm back online by aka-ed · · Score: 5, Informative
      Overall, I am impressed how AT&T has moved all its customers off Excite and onto their own network... I dunno how they did it.

      Not all their customers...yet. Here's the latest on the migration plan.

      --
      I survived the Dick Cheney Presidency 7 to 9 AM 7-21-07
    2. Re:I'm back online by BrookHarty · · Score: 5, Funny

      I hate when people say goto the web when your service isnt working. Same logic at work, you call in, my network access isnt working, they say please goto the intranet website and fill out a support request form.

  2. Poor guys by NightRain · · Score: 5, Funny

    I clicked on the link in the main article, and what are the words I see? "Overwhelming traffic to DotcomScoop.com has created technical problems leading to data loss. Recent news stories published on the site are lost for the time being. We will continue to provide updates as news warrants."

    And this is before the /. effect hits them. I feel their pain :)

  3. Real Slashdotters by soulsteal · · Score: 5, Funny
    A bonafide /.'er would add two lines to their HOSTS file:
    • 64.28.67.150 slashdot.org
    • 209.242.124.241 www.goatse.cx

    Just to be fair to the trolls...

  4. Excite@[home] by Anonymous Coward · · Score: 5, Funny

    Coincidently (?) their building sign only has "Excite@" illuminated (the "home" portion is dark)... or maybe it's irony... sarcasm ? ^_^

  5. Somewhat working by brocktune · · Score: 5, Interesting

    I changed DNS to the old Mediaone servers and I'm working again. My DHCP-generated IP address changed. Mail and news are not up yet.

    Details on how to change are here. I assume other folks can replace the "ga" in the URL with their state or city name. There was an email sent out last week with more details.

  6. dns isn't a crisis by Restil · · Score: 5, Informative

    Guys.. you can use ANY dns server on the internet pretty much. Might be that tinsy bit extra resolving latency, but the crisis is minimal.

    -Restil

    --
    Play with my webcams and lights here
    1. Re:dns isn't a crisis by Pathwalker · · Score: 5, Informative

      Pick a large university near you, and do a whois on them to see what their nameservers are.
      They'll probably be a good choice.

  7. @Home stay online HOWTO by Anonymous Coward · · Score: 5, Informative

    If you are one of the many disconnected today, here's something you can try to get back online:

    If your modem still has sync (cable modem is showing online, or solid cable light - depending on what modem you have) but have you no connectivity, set your IP and host information in statically, but specify non-@Home DNS numbers.

    This got me back online, so it might be worth your while to try it youself.

  8. Comcast@HOME by omega9 · · Score: 5, Informative

    I've got access through Comcast@Home here in Richmond, VA. We're still up but I keep the green lights in the corner of my eye.

    Mail, News, and DNS servers are all still active on their original IPs. We have not received any official email from Comcast concerning the status of their network. They're either solid with their own network and backbone, or they're just waiting to die. Either way, I wish we would get informed.

    --
    I'm against picketing, but I don't know how to show it.
  9. more dns #'s by loraksus · · Score: 5, Interesting

    4.2.2.2
    4.2.2.3
    provided to you by verizon and painfully easy to remember.

    I'm still shocked about how this is happening in the USA. I mean, if it happened in some eastern bloc country, or some nation in Africa that is very corrupt / piss poor, I could understand, but here?
    No offense to people in those countries, btw, it seems that the telecommunications infrastructure in most countries is beter than that of the usa.
    I honestly don't understand why the service costs so much in the usa - In BC, Canada, 1.5mb down / 768 up, 2 static ip's for $40 a month CANADIAN! Here, I pay $55ish for a whole 768dn / 100k up, a dynamic ip and shitty ping. WTF. The Canadian dollar is worth less, so it stands to reason that the equipment costs more for the Canadian providers (because they take in canadian $, not us $) . . .

    bah, at least my dsl provider looks like they will be in service for the next month or so....

    --
    1q2w3e4r5t6y7u8i9o0pqawsedrftgthyjukilo;p'azsxdcfv gbhnjmk,l.;/
    1. Re:more dns #'s by Spy+Hunter · · Score: 5, Funny
      Let's do a little reverse-DNSing, shall we?

      4.2.2.1: vnsc-pri.sys.gtei.net
      4.2.2.2: vnsc-bak.sys.gtei.net
      4.2.2.3: vsnc-lc.sys.gtei.net
      4.2.2.4: i-will-not-steal-service.gtei.net

      I guess that's the curse of having a memorable IP address...
      --
      main(c,r){for(r=32;r;) printf(++c>31?c=!r--,"\n":c<r?" ":~c&r?" `":" #");}
    2. Re:more dns #'s by seanadams.com · · Score: 5, Interesting

      4.2.2.4: i-will-not-steal-service.gtei.net

      Kinda stupid, actually. "Hey, we've left our DNS servers accessible to the public with no access control, but please don't use them unless you're paying us"

      Most people configure their DNS servers to allow anyone to do a recursive lookup, because usually there's no point in using someone else's DNS as opposed to running your own or using your ISPs.

      If they wanted to prevent the public from using their DNS servers, they would have one set of servers only accessible to their own customers, and another set accessible to the world, but which only served domains they were hosting. It's very easy to do, so it's silly of them to insinuate that we're "stealing" by using name servers which have been deliberately left open.

  10. AT&T@Home getting re-connected HOWTO by Anonymous Coward · · Score: 5, Informative

    I'm not sure it will help a lot of people, but this is what I just did to get reconnected. (Gotta feed the /. habit.) I'm in Fort Collins, CO if that's relevant to anyone. I haven't got a phone call from AT&T yet. But that may well be on account of the phone number they have listed for me is disconnected right now.

    I did try sending out DHCP requests before doing this, but never got any replies. I wouldn't call this course of action exceptionally friendly behaviour. But the web sites AT&T listed in some email this past week are either unreachable or have nothing helpful.

    • Listen for IP traffic coming over the modem. I did tcpdump -n -i eth0 and figured that the not-10.x.x.x router doing all the ARP requests was the neighborhood router.
    • Make note of several of the IP addresses that the router continues to ask for and stop tcpdump. Also note the suspected router address.
    • Set your IP address to one of the addresses from the previous step (see ifconfig(8) for help on that.) Add a default route through the router you found in the last step. route add -net default x.x.x.x )
    • Hope someone follows up with a suggestion on getting DHCP working again or that you get a phone call from AT&T.
    Gotchas:
    • You may well be hijacking someone else's legitimate IP address. And quite possibly violating your AUP in the process.
    • Your cable modem does need to think it has a good connection to the network. Look for a set of lights glowing steadily. Or if it has a web interface, look at that. My RCA cable modem has a status page at http://192.168.100.1/

    Good Luck!

    1. Re:AT&T@Home getting re-connected HOWTO by linzeal · · Score: 5, Funny

      Oh man you idiot giving out your ip address like that I just hax0red you so . . .

      --
      An Education is the Font of All Liberty
  11. AT&T @Home reconnecting (CORRECTED) by PureFiction · · Score: 5, Informative
    First: Oregon and Washington are the only states that AT&T is able to connect on their new network at this time. See http://biz.yahoo.com/rf/011201/n01282093_5.html

    If you are in one of those two states, you will notice that your cable modem is still synch'ed up, and that any site you try and reach will take you to this AT&T page:

    http://transition-aid.attbi.com/attbi_welcome_page .html

    This is because you are using the OLD @home nameservers, which AT&T has replaced to resolve ALL DNS lookups to their migration help site.

    The fix is as simple as it reads in the Manually Configuring Unsupported Operating Systems page

    1. Fire up a dhcp client. In my case, all I needed to issue was the command:
    • $ dhcpcd eth1
    2. Check your DNS servers (/etc/resolv.conf) and remove any of the old @home servers. The new IPs I got were:

    • 204.127.198.4
      63.240.76.4
    3. If you have any machines inside a NAT network, you need to update their DNS server lists as well (unless your gateway is set as the DNS)

    4. Change your outgoing SMTP server to mail.attbi.com instead of the *.home.com host.

    And that should do it! I was actually surprised how easy it was to get back online after they made the changes. I was dreading bringing out the old 56k modem again.

    Lets home the remaining states get their access back soon as well...

  12. Bad, stupid move by Excite@home... by kcbrown · · Score: 5, Insightful
    By turning off all their subscribers, Excite@home has effectively made an enemy of AT&T. Now that they've done this, I see one of two outcomes:
    1. Excite@home will turn the services back on and take the offer they were given (if that's even possible!)

      or

    2. AT&T will finish transitioning their customers to their own internal network and tell Excite@home to go fsck themselves.

    So if Excite doesn't turn their network back on VERY soon, like in the next day or so, they're toast: AT&T has the cash and resources to manage their cablemodem subscribers themselves. Once Excite@home no longer has anyone hooked up to their network, their value will drop through the floor.

    In short, even though the offer they were given probably wasn't very good (it was probably really bad, actually), now that they've shut down their customers they're dead. And if I were AT&T, I'd see to it that the floor was wiped with Excite@home in retaliation for screwing over my customers.

    The only variable I know of here that can affect the outcome is the rate at which cablemodem subscribers bail out and go with some other service, for those that can. Since it takes at least a couple of weeks for most DSL connections to be provisioned and configured, the only immediate competition that AT&T will lose customers to is dialup, which isn't terribly comparable. So I think AT&T is pretty safe when it comes to keeping their customers for the next couple of weeks. As long as they can transition the vast majority of their customers in that amount of time, they're safe, and that means that Excite@home has managed to fsck themselves good with this idiotic move.

    --
    Use 'slashdot stuff' in the subject line in any email you send me if you want to get past the spam filter.
    1. Re:Bad, stupid move by Excite@home... by trenton · · Score: 5, Interesting
      Excite@Home actually didn't make the decision to turn off the modems. The bondholders that financed Excite@Home did. AT&T's offer was so low, they stood to loose tons of money if the deal went through. So, they filed a law suit and had a judge COMPEL Excite@Home to turn off the service. Their reason for this was that keeping the modems on was costing 6 million per week, thus causing the company to lose even more money.

      It still remains to be seen if the bondholders will come out ahead. They claim that the assets of Excite@Home alone are worth much more than AT&T's buyout offer of $307 million. I guess they're waiting for a better offer.

      But, to be sure, pissing off 850,000 people is sure going to lower the value of Excite@Home.

      --
      Too big to fail? Does that make me to small to succeed?
  13. Photos by seanadams.com · · Score: 5, Funny
    Coincidently (?) their building sign only has "Excite@" illuminated (the "home" portion is dark)... or maybe it's irony... sarcasm ? ^_^



    OK, I'll bite. I just drove up there.

    Here are some hilarious images of this classic f**cked company.