Why are you assuming resetting the router won't work?

On Wed, 18 Mar 2009 06:54:56 -0400, "riggor9999"
riggor9999 at (no spam) nospam_yahoo.com> wrote:

Why are you assuming resetting the router won't work?

And by resetting you mean resetting to factory defaults. You do not mean
power down and back up.

On Wed, 18 Mar 2009 09:25:47 -0400, Dennis <nobody at (no spam) nowhere.invalid
wrote:

On Wed, 18 Mar 2009 06:54:56 -0400, "riggor9999"
riggor9999 at (no spam) nospam_yahoo.com> wrote:

Why are you assuming resetting the router won't work?
And by resetting you mean resetting to factory defaults. You do not mean
power down and back up.

Correct. One of the key things achieved by a return to factory
defaults is that the modem will then be in a known state, as opposed
to the unknown state it's in now. We know from experience that a
router set to factory defaults will work properly with Comcast,
assuming no other faults exist.

One thing I would have checked, given the symptoms described, and
maybe it's been checked and I missed it, is to make sure the router is
configured to use DHCP on its WAN port. Resetting to factory defaults
will return this setting to DHCP. If it's currently set to PPOE, for
example, the problem will be as described by the OP; i.e., the WAN IP
will remain 0.0.0.0.

On Wed, 18 Mar 2009 06:54:56 -0400, "riggor9999"
riggor9999 at (no spam) nospam_yahoo.com> wrote:

Why are you assuming resetting the router won't work?

And by resetting you mean resetting to factory defaults. You do not mean
power down and back up.

"Dennis" <nobody at (no spam) nowhere.invalid> wrote in message
news:cgt1s455fmd1epoh4mf2epm8fd6v6fusdd at (no spam) 4ax.com...
On Wed, 18 Mar 2009 06:54:56 -0400, "riggor9999"
riggor9999 at (no spam) nospam_yahoo.com> wrote:

Why are you assuming resetting the router won't work?
And by resetting you mean resetting to factory defaults. You do not mean
power down and back up.


Yes - earlier in the thread we all clearly stated "reset to factory
defaults"

I may have even mentioned "paperclip"

On Wed, 18 Mar 2009 09:25:47 -0400, Dennis <nobody at (no spam) nowhere.invalid
wrote:

On Wed, 18 Mar 2009 06:54:56 -0400, "riggor9999"
riggor9999 at (no spam) nospam_yahoo.com> wrote:

Why are you assuming resetting the router won't work?
And by resetting you mean resetting to factory defaults. You do not mean
power down and back up.

Correct. One of the key things achieved by a return to factory
defaults is that the modem will then be in a known state, as opposed
to the unknown state it's in now. We know from experience that a
router set to factory defaults will work properly with Comcast,
assuming no other faults exist.

One thing I would have checked, given the symptoms described, and
maybe it's been checked and I missed it, is to make sure the router is
configured to use DHCP on its WAN port. Resetting to factory defaults
will return this setting to DHCP. If it's currently set to PPOE, for
example, the problem will be as described by the OP; i.e., the WAN IP
will remain 0.0.0.0.

Bill M. wrote:
On Wed, 18 Mar 2009 09:25:47 -0400, Dennis <nobody at (no spam) nowhere.invalid
wrote:

On Wed, 18 Mar 2009 06:54:56 -0400, "riggor9999"
riggor9999 at (no spam) nospam_yahoo.com> wrote:

Why are you assuming resetting the router won't work?
And by resetting you mean resetting to factory defaults. You do not mean
power down and back up.

Correct. One of the key things achieved by a return to factory
defaults is that the modem will then be in a known state, as opposed
to the unknown state it's in now. We know from experience that a
router set to factory defaults will work properly with Comcast,
assuming no other faults exist.

One thing I would have checked, given the symptoms described, and
maybe it's been checked and I missed it, is to make sure the router is
configured to use DHCP on its WAN port. Resetting to factory defaults
will return this setting to DHCP. If it's currently set to PPOE, for
example, the problem will be as described by the OP; i.e., the WAN IP
will remain 0.0.0.0.


Problem solved.
The cable modem has a battery in it; first time I ever saw that.

Once we took out the battery, we wee able to fully power down and reset
the damn thing.

"Justin" <justin at (no spam) nobecauseihatespam.com> wrote in message
news:gps26f$o09$2 at (no spam) news.motzarella.org...
Bill M. wrote:
On Wed, 18 Mar 2009 09:25:47 -0400, Dennis <nobody at (no spam) nowhere.invalid
wrote:

On Wed, 18 Mar 2009 06:54:56 -0400, "riggor9999"
riggor9999 at (no spam) nospam_yahoo.com> wrote:

Why are you assuming resetting the router won't work?
And by resetting you mean resetting to factory defaults. You do not mean
power down and back up.
Correct. One of the key things achieved by a return to factory
defaults is that the modem will then be in a known state, as opposed
to the unknown state it's in now. We know from experience that a
router set to factory defaults will work properly with Comcast,
assuming no other faults exist.

One thing I would have checked, given the symptoms described, and
maybe it's been checked and I missed it, is to make sure the router is
configured to use DHCP on its WAN port. Resetting to factory defaults
will return this setting to DHCP. If it's currently set to PPOE, for
example, the problem will be as described by the OP; i.e., the WAN IP
will remain 0.0.0.0.

Problem solved.
The cable modem has a battery in it; first time I ever saw that.

Once we took out the battery, we wee able to fully power down and reset
the damn thing.

Cable modem or router?

I thought the cable modem hooked directly to the PC worked, and the problem
was when the cable modem was connected to router connected to PC.

What made you look / think of a battery?

Problem solved.
The cable modem has a battery in it; first time I ever saw that.

Justin wrote:

I thought the cable modem hooked directly to the PC worked, and the
problem was when the cable modem was connected to router connected to
PC.

Correct.
Laptop to cable modem = OK.
Router connected to Cable modem = toast

So what does the cable modem battery have to do with the router failing ?

Justin wrote:

I thought the cable modem hooked directly to the PC worked, and the
problem was when the cable modem was connected to router connected to
PC.

Correct.
Laptop to cable modem = OK.
Router connected to Cable modem = toast

So what does the cable modem battery have to do with the router failing ?

I thought the cable modem hooked directly to the PC worked, and the
problem was when the cable modem was connected to router connected to PC.

Correct.
Laptop to cable modem = OK.
Router connected to Cable modem = toast

SNIP

So the question is why did it have problems to begin with? There is no such
thing as random or one time problems. All it means is that you have not
figured out the sequence of events to recreate the problem.

If it was working ...

SNIP

So the question is why did it have problems to begin with? There is no such
thing as random or one time problems. All it means is that you have not
figured out the sequence of events to recreate the problem.

If it was working ... cable modem with battery, connected to router,
connected to pc ... and as you stated - all of a suddden, one day, the
router stopped working (appeared that it did not get it's IP address
renewed) ... what changed? Especially since when you disconnected the
router and went directly from cable modem to PC it worked.

We understand resetting the cable modem via paper clip or complete powerloss
(ac and dc) fixed the issue ... it really does not explain why it stopped
working with the router, but it continued to work directly connected to the
PC.

In theory - going from router to direct PC should have never worked without
the cable modem reset.