Most @Home Customers Still Connected -- For Now

Mansing writes: "There may be hope after all, according to this update from the Washington Post" In short, a reprieve for many @Home customers, with negotiations ongoing between @Home and the major cable companies with which its service is offered -- watch for updates here. (AT&T broadband customers, though, will be moving to another service -- AT&T dropped out of the negotiations to keep @Home for their customers, and say that switching current customers to a new network will take about 2 weeks.)

Comments

AT&T

[Ailuro]

As a AT&T @Home subscriber, I thought it was pretty funny last night when they showed a commercial for AT&T broadband bashing DSL for having no guarantees of connectivity. Ha! I hope that'll show up on adcritic.com soon, I wanna send that to my friends.

Thank goodness for Work T-1 :)

Re-connect how-to

[Mark Bainter]

I posted this in reply to the how-to in the other thread, but seems I might be better served to post it here or many people might not see it.

FWICT, the best way to get your service re-established goes like this:

-kill your dhcp client. Wipe your leases.
-re-init your cable modem:
(Unplug it, wait 20-30 seconds and plug it in)
-Wait for it to sync up. If it doesn't, keep trying.
-Once it resyncs, run:
tcpdump -i eth0 -lf dst port 68
This should list the dhcp replies going out
on your subnet. If you don't see them,
something is still not right. Try re-initing
your cable modem again.
-Start your dhcpclient

This should get you setup. Remember, if you're like me and were on a static number and blocking dhcp traffic you'll need to alter your firewall rule(s).

Re:AT&T's replacement is worse than bad.

[digitalunity]

1) Their support are not answering the phone
Be kind, they're very busy right now. Wait a little.

2) My IP address that has been static since I signed up over a year ago has suddenly changed and it appears that static addressing in any form has gone up in smoke. This screws anyone relying on a static IP.
Wait a while. Things will settle down. My IP address has changed many times since saturday morning. If you need a static IP to run something against the AUP, maybe you need a new ISP anyways.
3) They have been playing fast and loose with the service agreement (that I signed), but instituting an AUP (that I didn't sign)that directly contradicts it.
I haven't seen anything like this. Do you have any references?
4) Their DNS service has been very erratic

It was. It's working now. I couldn't get any of the DHCP assigned DNS IP's to work. Now they do. I think they updated the DHCP well before actually turning on the DNS servers. Oh well. Get over it. If you want DSL; you can go ahead and do it. I however, as well as everyone else I know, has found the short service interupption more than acceptable.
This is not the sort of crap I want to be paying for and I am actively shopping for a replacement (I.E. DSL). I expect any other user who wants to do more than play with the latest microsoft browser will be doing the same and dumping AT&T as soon as possible
What the fsck are you talking about? You think maybe throwing in some mention of Microsoft will get you modded up or make you look cool? What do you need to do thats so goddamned important that you need a static IP? And what in the freak does a browser have to do with your ISP? That's not rhetorical.

So, yes they made some big changes. No, that's not fully exculpatory for the service interuptions. However, they've declared that it will be taken care of.

Come to think of it... there was a new AUP a while back that you had to opt-out of in writing. It's been in effect for quite a while. Maybe you should check your mail. :)

Moderators: If you have to look up any of the terms I've used, don't moderate me. You're probably confused. Read the Moderator Guidlines before doing anything drastic.

Comcast Jumpstart - Comcast's @Home Replacement?

[instinctdesign]

I posted this in the last @Home discussion, but that was after about 450 posts so it basically got lost, so here it is again.

I actually just had a chat with a Comcast rep at a local technology show and it looks like that if your running Comcast@Home you might be in for a significantly better ride than the other providers have partnered with.

Comcast has been working on their own broadband cable network for a bit of time now, partly anticipating the demise of @Home as well as the issues rising out of the severe limitations that @Home put on commercial deals that Comcast wanted to pursue. Originally planned to launch in April 2002, the Comcast network, currently codenamed 'JumpStart', has been pushed forward to a potential launch January 1st 2002, assuming everything goes well. Due to the accelerated timetable there may be glitches in the initial rollout, but frankly intermittently buggy cable (assuming it will be fixed in the near future) is better than dialup in my opinion.

You will however lose your @Home email account as well as any stored messages or address book so back them up as soon as possible. Comcast will provide email services once their network is up and running. What the final name of the program I can't attest to, jumpstart.net .org and .com all seem to be taken, so its hard to say what your email address could end up being.

Obviously this is all from one source, though a Comcast representative, its best to avoid taking all this to heart until there is a final formal announcement as to their plans. I do know that Comcast@Home is up and running as of mid-day today. For how long... who is to say.

Re:AT&T's replacement is worse than bad.

[abe ferlman]

What do you need to do thats so goddamned important that you need a static IP? And what in the freak does a browser have to do with your ISP? That's not rhetorical.

I can't speak for the poster above, but the reason I got always-on internet service was so that I could shell into my home computer and access my files from wherever I like, not to mention forwarding X applications over the Internet when useful/necessary. Static ip is necessary for that.

Lighten up on the attitude a little, k buddy?