Strange @home modem behavior...

[dronox]

Allright, I doubt anyone will be able to answer this one...

I've got the Grey/Green ish @home cable modem- I think it's by Motorola.

The past two times I tried to get it running in linux it craps all over itself for 7-12 hours...

The "Test" light flashes on and off for about 6 minutes, then it stops and the "Cable" one flashes for a minute- then back to the "Test".

It's the hugest pain in the ***, because it wont get me any connection to the net- in windows- for 7-12 hours.
I think it's related to DHCP because when I go in winipcfg, and try to "renew", it can't "contact" the dhcp server...

If anyone knows why this happens, PLEEEASE share the warmth. Heh.
Thanks.

[oh, and ps- I did try un-plugging about 459883 times, same with the "reset" button.]

[JALU]

I have at home, and they told me that I have to start the modem before I start/plug it into my computer and let it run for something like 5 minutes before I can use it. I don't and it works fine, but it might be something like that. It's worth a try I guess.

[Hatecrime69]

I think i have the same problem as you do (os independent obiously) a while ago it useto crap out almost hourly for me, lately it has been pretty good though. What I do (witch usually works, sometimes it takes awhile) is unplug the modem and plug it back in (it doesn't matter when you do it, when it connects you can surf the net again without restarting)

[freaker]

sounds like an @HOME problem to me. I have been running @HOME for quite some time now, and the only time it craps is when Comcast screwed something up or an outtage -
IMHO


freaker :cool:

[dronox]

Yup-
As I stated at the end- I've tried that.. It does nothing.. it's so weird.

And @home tech support is a joke, heh.
I called and they kept going through the same routine as they do for everything...

Well- thanks anyway people.

Originally posted by Hatecrime69:
I think i have the same problem as you do (os independent obiously) a while ago it useto crap out almost hourly for me, lately it has been pretty good though. What I do (witch usually works, sometimes it takes awhile) is unplug the modem and plug it back in (it doesn't matter when you do it, when it connects you can surf the net again without restarting)

[bighara]

Our @home account will blank out every so often for the whole evening. It's apparently an issue on their end. Esp if you're in one of their 'beta' areas.

[ariel001]

I had this problem with @Home after a power outage... I kept calling their tech support and they'd walk me through the same BS every time (unplug the modem, re-"push", whatever) and it wasn't helping. I finally realized that it was the cable modem itself that was malfunctioning, but getting someone to come out and replace it was a real chore. I actually ordered ADSL from the phone company and brought all the stuff home, but then was able to convince their LOCAL support manager to come out to my house and fix it.. he was at my house all freakin' day trying various things (switching ethernet cards, running with the hub, without the hub, etc). Finally he came to the conclusion that it was the modem. As soon as he replaced it it started working again and has ever since then. These modems seem to be really sensitive to power surges (my digital cable box has the same problem, btw). The tech support people for @Home are morons though.. and don't even mention that you have any non-Windows OS, a firewall, multiple computers (a feature they charge you extra for but won't provide support for!) , etc.