Automatically restart ADSL modem when no / bad connectivity

[Electron1]

Any advice on how to do this?
I know that this can be done if you are able to reload a modem with DD-WRT, but this involves some advanced work - replacing the factory firmware and fiddling around to get it working properly, then you can apparently write your own script to do some basic checks - a combination of regualr pings and nslookup e.g. every 5 minutes, then after a few successive failures, initiate a reboot.

I don't want to replace factory firmware (Netgear DG834 modem).
Does anyone know of a windows based program that does this?
I guess that you would need to write some code that would do telnet to the router to initiate the reboot.

Alternatively are there modems that have this sort of functionality built in?

 

[Pada]

Just get a modem that doesn't need restarting. Some of those Netgear DG834 models were really terrible.

I've never had to reboot my ancient Telkom 5100 ADSL modem in the 2 years that I had it!

 

[Electron1]

Thanks Pada.

This modem and line have been stable for over 3 years. In the last week there have been 2 outages where there is no connectivity overnight / over the weekend till someone is back in the office and reboots the modem. This has had an effect on email (I am going to post a separate thread on recommendations for email relay services).

I don't have any details on what the cause for the connectivity issue, it could be the modem, the line quality, ISP or acombination of the above. Just was wondering if there are reboot solutions out there.

 

[Amphibious]

Hi Electron1,

I have had this similiar issue before at one of my clients.

It sounds like a modem issue giving in. If possible try setting up a spare modem to test before testing the line or ISP.

Thanks Pada.

This modem and line have been stable for over 3 years. In the last week there have been 2 outages where there is no connectivity overnight / over the weekend till someone is back in the office and reboots the modem. This has had an effect on email (I am going to post a separate thread on recommendations for email relay services).

I don't have any details on what the cause for the connectivity issue, it could be the modem, the line quality, ISP or acombination of the above. Just was wondering if there are reboot solutions out there.

 

[PsyWulf]

Cheap and dirty option is writing a batch file that can ping and log the result to a txt file,then check the txt file for "timeout",telnet to the router and initiate a restart,put that on a schedule and relax

 

[Electron1]

Hi Electron1,

I have had this similiar issue before at one of my clients.

It sounds like a modem issue giving in. If possible try setting up a spare modem to test before testing the line or ISP.

Thanks, if it happens again, I will give that a try. Also asked my client to call me before rebooting so I can do some troubleshooting.

Cheap and dirty option is writing a batch file that can ping and log the result to a txt file,then check the txt file for "timeout",telnet to the router and initiate a restart,put that on a schedule and relax

I'm sure I could do it in a batch file, probably better to do in WSH, just didn't want to reinvent the wheel if there is any existing solution out there.