Netgear DG834G auto-reconnecting

I have an ADSL connection that appears to be getting disconnected from time
to time. Its not a problem with the router crashing, but when I log on to
the router and go to 'Router Status' it just says disconnected. If I click
connect, it goes back online. Does anyone know if I can set the router to
reconnect automatically when it gets disconnected?

Thanks
Tom

On Sat, 8 May 2004 13:14:56 +0100, "Tom" <(E-Mail Removed)>
wrote:

>I have an ADSL connection that appears to be getting disconnected from time
>to time. Its not a problem with the router crashing, but when I log on to
>the router and go to 'Router Status' it just says disconnected. If I click
>connect, it goes back online. Does anyone know if I can set the router to
>reconnect automatically when it gets disconnected?

To my knowledge this router does that anyway. On the one occasion I
found my ADSL connection had been disconnected the router was trying
once every 5 secs to reconnect. However on that occasion I was
actually forced to reboot the router to restore the connection.

That said, it has only been once in several months that I have
experienced this. The rest of the time it remains connected.

"Tom" <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> I have an ADSL connection that appears to be getting disconnected from time
> to time. Its not a problem with the router crashing, but when I log on to
> the router and go to 'Router Status' it just says disconnected. If I click
> connect, it goes back online. Does anyone know if I can set the router to
> reconnect automatically when it gets disconnected?
>
> Thanks
> Tom


Snap!

I have the same router and the same 'problem' - more of a nuisance,
really, as like you I don't have to reboot to regain connection, just
log in to the the router and reconnect to the net. Still, it can be
confusing for SWMBO.... All settings relevant to automatically
connecting are set, BTW; as another poster has noted, this appears to
be a reasonably common problem with this brand of routers.

The only fix I've been able to find on the net so far is to upgrade
the firmware to the latest revision, although some users have reported
problems with applying the upgrade (i.e. boxes locking up). I'll be
giving that a go tonight and will repost if successful.

HTH,

Shano

On 10 May 2004 09:03:19 -0700, (E-Mail Removed) (Shano) wrote:

>Snap!
>
>I have the same router and the same 'problem' - more of a nuisance,
>really, as like you I don't have to reboot to regain connection, just
>log in to the the router and reconnect to the net. Still, it can be
>confusing for SWMBO.... All settings relevant to automatically
>connecting are set, BTW; as another poster has noted, this appears to
>be a reasonably common problem with this brand of routers.
>
>The only fix I've been able to find on the net so far is to upgrade
>the firmware to the latest revision, although some users have reported
>problems with applying the upgrade (i.e. boxes locking up). I'll be
>giving that a go tonight and will repost if successful.
>
>HTH,
>
>Shano

Bizarrely, after posting in this thread yesterday I got home last
night to find this exact problem. Just clicking on "connect" made it
reconnect. Strange.

So that's now twice since I got it that I've had this problem, approx
once a month.

Incidentally, I upgraded the firmware without incident, but recommend
you use a cat5 connection to do the upgrade.

Hi Tom,

Not sure whether my DG834G is auto-reconnecting or not, but coincidently I
noticed this in my security log the other day;

Mon, 2004-05-10 13:59:38 - LCP down.
Mon, 2004-05-10 13:59:40 - Initialize LCP.
Mon, 2004-05-10 13:59:40 - LCP is allowed to come up.
Mon, 2004-05-10 14:00:13 - CHAP authentication success

I'm not entirely sure what LCP is but according to my router uptime stats
the WAN figure does indicate that it was only been up since these entries,
so I assume this means that it did indeed auto-reconnect (I certainly didn't
do anything to reconnect it and no-one noticed anything here).

Many thanks, David

"Tom" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I have an ADSL connection that appears to be getting disconnected from
time
> to time. Its not a problem with the router crashing, but when I log on to
> the router and go to 'Router Status' it just says disconnected. If I
click
> connect, it goes back online. Does anyone know if I can set the router to
> reconnect automatically when it gets disconnected?
>
> Thanks
> Tom
>
>

In article <(E-Mail Removed)>,
(E-Mail Removed) says...
> On 10 May 2004 09:03:19 -0700, (E-Mail Removed) (Shano) wrote:
>
> >Snap!
> >
> >I have the same router and the same 'problem' - more of a nuisance,
> >really, as like you I don't have to reboot to regain connection, just
> >log in to the the router and reconnect to the net. Still, it can be
> >confusing for SWMBO.... All settings relevant to automatically
> >connecting are set, BTW; as another poster has noted, this appears to
> >be a reasonably common problem with this brand of routers.
> >
> >The only fix I've been able to find on the net so far is to upgrade
> >the firmware to the latest revision, although some users have reported
> >problems with applying the upgrade (i.e. boxes locking up). I'll be
> >giving that a go tonight and will repost if successful.
> >
> >HTH,
> >
> >Shano
>
> Bizarrely, after posting in this thread yesterday I got home last
> night to find this exact problem. Just clicking on "connect" made it
> reconnect. Strange.
>
> So that's now twice since I got it that I've had this problem, approx
> once a month.
>
> Incidentally, I upgraded the firmware without incident, but recommend
> you use a cat5 connection to do the upgrade.
>

Cheers for the advice - unfortunately I attempted the upgrade before
reading it...

I'd go a bit further and say "use a cat5 connection and remove all other
connections"; although at
http://kbserver.netgear.com/support_...asp?dnldID=673 it states to
use the ethernet port, I also had a wireless connection and the phone
line connected, and the upgrade failed. Luckily I'd already downloaded
the recovery utility just in case :-o

A quick disconnect to the bare minimum to run the utility and everything
appears to be fine, and the connection has been solid for 24 hours now
(and about 20 of those have been idle) so it appears to have worked,
although I've upgraded to 1.04.01 which has been reported to have a few
bugs on the boards at adslguide.org.uk. Still, at this stage I'd be
happy to get your reported month of uninterrupted uptime!

Cheers again,

Shano

On Tue, 11 May 2004 22:06:38 +0100, Shano <(E-Mail Removed)>
wrote:

>In article <(E-Mail Removed)>,
>(E-Mail Removed) says...
>>
>> Incidentally, I upgraded the firmware without incident, but recommend
>> you use a cat5 connection to do the upgrade.
>
>Cheers for the advice - unfortunately I attempted the upgrade before
>reading it...
>
>I'd go a bit further and say "use a cat5 connection and remove all other
>connections"; although at
>http://kbserver.netgear.com/support_...asp?dnldID=673 it states to
>use the ethernet port, I also had a wireless connection and the phone
>line connected, and the upgrade failed. Luckily I'd already downloaded
>the recovery utility just in case :-o

I think when I performed the upgrade I had not yet installed the
wireless kit for the workstation so it was not an issue. But as a
general rule I never have both enabled at the same time anyway.

>A quick disconnect to the bare minimum to run the utility and everything
>appears to be fine, and the connection has been solid for 24 hours now
>(and about 20 of those have been idle) so it appears to have worked,
>although I've upgraded to 1.04.01 which has been reported to have a few
>bugs on the boards at adslguide.org.uk. Still, at this stage I'd be
>happy to get your reported month of uninterrupted uptime!

The lesson here is to be careful what you say! I got home last night
and the connection was down - twice in 2 days therefore. Not only
that but it would not reconnect at all. In the end I had to reboot
the router and it then connected successfully. I could get bored with
this....

As for firmware, I am using v1.04 which was only up on the website for
a short while, having been quickly replaced by 1.04.01 that you have.
As I am not suffering from any of the reported bugs in the version I
have I decided not to make the upgrade and risk frying the router.