@home Sucks!!!!

[Postit]

You know.. I had a similar problem, although mine was that I couldn't even ping the gateway. It turns out, that my MAC Address list on my account was up around 25-30, and once they cleared them off, it works better than it did before. I went through the same things you ppl did. My comptuer was setup right, everything worked fine 2 hours before etc etc..just a thought. I have a different cable modem provider tho.

-Post it

 

[Grey]

My @Home has been going to crap lately as well. First they told me it was a Router problem. Now they say that the specific things are because the DHCP server is conking out for the NJ @Home area causing IPs to be unassigned. I asked them why some things still worked and he said the connection must still be active from before the DHCP died. Sigh. It has been working fine since monday morning..Although their own DHCP setup program cant find the net DOH.

 

[bozack]

You know that is the nuttiest thing about @home

if they are going to assign DHCP Ip's then they should use the MAC address for authentication, but instead they have this ass backwards system of using the computer name and the workgroup. Heck even the workgroup didn't matter, I had mine just set as workgroup instead of the default @home workgroup and my connection was fine before the election.

@home sucks and I wish I never went with them

 

[minihoser]

i glad someone brought this up. I live in sacramento where service rolled out 3 months ago..ever since them peak times pings go to higher than 600+..no chance for UT during the hours of 5pm-2am..downloads during the day are 2-3Mbps..during peak time there are 128kbps..2 times a 56k modem..this is how all of sacramento is due to overselling their service..i have had 6 ticket numbers email and service up and down everyday..service techs out twice and it took 6 weeks for them to admit to a problem..the worst part is they are still selling service in sac asw if there is no problem..everytime i call they ask for my serial number and tell me to cycle my modem if i do it one more time i will explode..i asked them about their quote "blazing fast service that up to 100 time faster than a 28.8k modem"..so all of sac has to deal with this until they get more routers up and running..they said they had the same problem in new jersey and it took a while to fix

thanks alot
not@home

 

[Alphacowboy]

Ah... well that is a big ol' difference, we use MAC addresses for it all, works very well

 

[LordSandMan]

Ok, just wondering has anyone had a good experience with @home. Anyone??????

 

[Stephen24]

Well, I have ADSL from Sympatico (bell) and it has never went down, EVER.

 

[pm]

LordSandan: Yes, as I mentioned above, I've definitely had an overall good experience with AT&T@Home. The installation was very competently done, the performance is amazing (2.5Mb/s down and 810kb/s up with very low latencies), downtime is more often than I would like (about 6 hours a month) but it is not terrible, and overall for $40/month it's a huge improvement on my old $40/month 19.6kb/s phone connection. The email service is awful, but I don't use it. Technical support has been spotty the three times that I've needed to call. One the tech was terrible, the other two times they were pretty competent. Overall, I'm very pleased with AT&T@Home.

It's worth noting that I'm >5 miles from a CO, that the phone company (USWest) is particularly incompetent here in Fort Collins, CO, that the IDSL service that I could get would be 144kb/s symmetric (well under 1/10 of the speed that I currently get) and would cost $50/month.

Most of my coworkers have had worse experiences with USWest's DSL than I have with AT&T@Home and a many of them switched to AT&T in the last few months.

 

[SSP]

Am I the only one here whose happy with @home service? My connection went down last month (actually, the whole area went down), other then that... it's working fine.

Oh yeah, if the mail server goes down... I just change the servers.

 

[beat mania]

I must have the most incompetent install guy for my @home network. I'm even surprised that my connection works ... I live in Sacramento, CA btw.
I told the guy that my machine used to connect to pacbell dsl, and after he installed the modem, he told me that I had to reconfigure all the settings for my internet software. I told him I don't need to. He keeps telling me that I have to. Until I showed him my software working without reconfiguring, and then he admitted that he though dsl was DIAL UP like modem ... and then he tried to connect me to the @home web page for registration, except that it wouldn't connect. And then he started BSing me, telling me that since I had pacbell before, they put in some cr@p in my computer so that I can't access the @home web page. Turns out that he got the wrong address.

Is @home in Sac really that bad? I work during the day, and when I come home, I usually just go on newgroup and irc. I notice that the mail server is down alot, the news server down sometime, but that's about it.

 

[minihoser]

beatmania
how long have you had sac@home..my access during the day is great during the hours of 6pm and 2am my pings for games are 600+..making any online game unplayable..my speed also go from 2-3Mbps to only 2 or 3 times faster than dialup..when i run a tracert to any site..my 3rd hop which is 24.7.183.xx labeled snfa is a huge bottle neck for sacramento..to my best knowledge sacramento is over sold and it will only get worse before it gets better
:frown:

 

[formulav8]

I'm glad i have RR instead of @home

 

[beat mania]

hoser: I've had it since end of August. Frankly, I just use the connection to download stuff. I don't play online games. And sorry, I have no idea how tracert works to give you a better answer. But I don't notice my download speed to be that bad, at 2x dial up.

 

[ViRGE]

I'm with pm. While @home isn't perfect, it's the best thing I've ever had, and most likely the best thing I'll get for some time.

 

[minihoser]

7:35 pm sacramento@home.com..peak time stats

Test running..........
** Speed 296(down)/88(up) kbps **
(At least 5 times faster than a 56k modem)
Finish.

Tracing route to www.yahoo.akadns.net [204.71.202.160]
over a maximum of 30 hops:

1 9 ms 8 ms 10 ms 10.75.122.1
2 8 ms 10 ms 15 ms r1-fe2-0-100bt.scrmnt1.ca.home.net [24.8.150.1
3 398 ms 406 ms 420 ms c1-se10-0.snfcca1.home.net [24.7.74.153]
4 386 ms 401 ms 400 ms 24.7.70.6
5 403 ms 397 ms 409 ms 206.132.110.193
6 420 ms 413 ms 413 ms pos6-0-2488M.cr1.SNV.gblx.net [208.50.169.62]
7 424 ms 408 ms 409 ms ge0-0-1000M.hr8.SNV.gblx.net [206.132.254.37]
8 410 ms 409 ms 375 ms bas1r-ge3-0-hr8.snv.yahoo.com [208.178.103.62]
9 392 ms 388 ms 383 ms www.yahoo.akadns.net [204.71.202.160]

Trace complete.

it gets worse!!! this is every night between 6pm and 2 am


not@home.com

 

[Grey]

Dont get me wrong I love @home! I couldnt live without it. I was a beta @Home for NJ and have had it since going on 4 years now. I had to use a modem when it goes down now and then.

I dont know how you analog modem people stand it

I looked into DSL, besides their 3.5 mile radius thing, it takes months and i do mean MONTHS for them to either install it or fix a problem.

 

[ERJ]

I'll chime in......

Mostly I can't complain about charter@home's service. We have had the service now for 1 year and have been out 4 times (modem offline). However.....

Of those 4 times we have been out the quickest we have gotten back online is 5 days, and the longest being 8 days. Now that's service

I swear that each time we go out I feel like going down to charter HQ and busting some heads. The whole tech support system is set up to screw the customer. The only support number for @home that I am given is the national tech support number. The guys I call there can't do a damn thing to help me and also don't care to. It is always the same "We will enter a help ticket for your local tech support. They should contact you in 24-48 hours". Ain't that wonderful.

Alright, I'm done.

ERJ

 

[JonJon]

does anyone know where i can get a tracer program? thanx guys

 

[LXi]

NM

 

[pm]

JonJon, it's in the standard installs for Win2k, Win98/ME and Linux. In Win98/ME and Win2k, it's:

tracert.exe <destination>

ie.

tracert yahoo.com

In a typical Windows installation it's in the c:\windows directory.


Lxi: No offense intended, but what does that have to do with @Home?

 

[BCYL]

I had a very similar experience a couple of days ago too... @Home was down for me one night... The lights on the cable modem was blinking, saying it cannot scan or connect to a data channel... I thought it was just some temp problem on @Home side so I just waited... well the service came back on the next evening (so the service was down for around 20 hrs), but only for a couple of hrs only... Then everything went back, with the cable modem not detecting a data channel...

So I finally got tired of waiting, and phoned @Home... They told me they have absolutely no problems with their end, and everything was fine... Then they went on to blame that probably the problem lies in the lines at my house, and they would send a tech over to check on Monday (I phoned on Friday)... So I thought there's really nothing i can do, so hang up and waited...

Then the next day, @Home service came back on without a problem! And I have had no problems with it since then... If it was problems with the lines at my house, why does it magically fix itself?

That's my rant about @Home...

 

[Rodzilla]

there is NO such thing as RG-56 maybe ya meant RG-6 ?

 

[LXi]

NM

 

[Jaraxal]

I just wanted to throw in my .02 cents. I have had Comcast@Home now for about 1 1/2 years and I have no complaints. In that time, my service may have gone down 2 times, and at the longest it was down maybe a few hours.

I do get some intermittent problems surfing the web now and again. I usually find that I can ping my gateway, and other sites, but the DNS servers (primary and/or secondary) will be down. In a minute or two they usually come back up.

I have a Linksys 4 Port DSL/Cable router/switch. The first thing I do is ping the router. If that works, then I ping the Cable gateway. If that works, I ping my DNS servers, and the problem usually lies there. If I can't get beyond my router, I usually reset the router. If I can't ping my cable gateway, I usually disconnect the cable from my modem, turn the modem off and reconnect everything while holding in the reset button.

Needless to say this usually works well. Of course, I never let a tech touch my computer during the initial installation and I am using my own 3Com NIC.

 

[bozack]

hey LXI what the hell are you talking about?
I havent made a hardware generalization in months if not the past year so you must have me confused with someone else, I may have said the 815 is easier to configure and get optimized than the via 133 but never said it had better performance.

just read your othe post in here and I would definately say you have me confused with someone else, I have said before the bx is good, but I have worked with the 815 and it is better, and I have yet to work with the via, that one I just go with what I hear-get your people straight before making random replies.

Well here is an update to my situation, I called back again and spent another two hours on the phone with the techies, and I finally conceeded and blew away the tcp/ip stack and winsock and started fresh

guess what?

it didn't work....go figure, what I had been saying the whole time

so they had me run some tracerts and to yahoo.com and gwu.edu I could complete the connection, however everywhere else was pretty much a no go, the tracert would get out to the hardware addy of the modem, through one or two of their points and then just die.

Which led them to the point that it was a problem with the routing on their end, and had nothing to do with me, as I had been saying all along...oh well they said it should be cleared up tonight.

The one good thing I can say is that the tech I spoke with last night was first class, he was really helpful, nice, worked with me and not spoke at me, and he really knew what he was doing. Heck he even called me back when he said he would and in my book that is quality.

He also reassured me to the point that they do allow networks and they don't violate policy unless your running an ftp server or something, and he basically said that other tech had his head up his ass. oh well that was comforting to know