couldn't get connected.....

[Dan Lund]

I've ran into this issue in the past in spurts, but I've always
started troubleshooting from the cable modem back... and it's always
been the cable modem not sync'ing with the head-end on Cox's network.
If you notice the 'cable' light blinking, it's attempting to sync with
the head-end.  If it's doing that, you can cycle the computer and god
knows what else behind it and it isn't going to amount to anything.
Sometimes a cable modem power cycle helps it, which might be what you
ran into.
Another thing I noticed is that Cox doesn't seem to set their DHCP
expiry right, which means that someone else will be assigned your IP
after it expires in the DHCP allocation, but the
machine/router/access-point (whatevers getting an IP from Cox) still
tries using the old IP because it's been told that the expiry time is
some ridiculously far away date.  A cycle of the interface usually
fixes that... or a power cycle which is an overkill but it would do
the same thing.

So in a nutshell, the 3 steps are a sledgehammer fix... more of a
remedial "get me up and working so I can find out what's going on"
fix.

--Dan

On 10/21/07, Jorge Delacruz <alterthegrid at yahoo.com> wrote:
> I spent a lot of time last year dealing with this
> issue and Cox.  Then someone told me to follow this
> sequence:
> 1.  Shutdown the computer.
> 2.  Power-cycle the modem.
> 3.  Start up the computer.
>
> Worked every time.  I spent hours on the phone with
> Cox and got nowhere other than "our equipment is fine
> - it must be your equipment."  Whatever.
>
> JD
>
>
> --- Michael Havens <bmike101 at cox.net> wrote:
>
> > Two days ago I turnewd my computer off and a couple
> > of hours later back on.
> > The modem was working but no connectivity so I
> > called COX today. I got the
> > standard 'We don't support your operating system but
> > the modem is working.'
> > Then, after noticing a message durring startup that
> > said 'No DHCP offer', I
> > consulted with a Linux Geek (whose phone number I
> > posses) and he said that it
> > is probably my ethernet card. So a new one was
> > picked up at FRY'S Electronics
> > and it was installed. I started up the computer and
> > it bitched about an IRQ.
> > I think I need a driver for it (it is a 10/100/1000
> > D-Link card picked up for
> > 24 bucks). Upset, I reinstalled thye old card and
> > everything came up. Why did
> > this happen?
> > ---------------------------------------------------
> > PLUG-discuss mailing list -
> > PLUG-discuss at lists.plug.phoenix.az.us
> > To subscribe, unsubscribe, or to change your mail
> > settings:
> >
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> >
>
>
> Jorge Delacruz
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss at lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>


-- 
Thanks,
Dan Lund

"The major difference between a thing that might go wrong and a thing
that cannot possibly go wrong is that when a thing that cannot
possibly go wrong goes wrong it usually turns out to be impossible to
get at or repair."