Unsolved

This post is more than 5 years old

2 Intern

 • 

2.2K Posts

32443

October 13th, 2008 18:00

NetGear Router wgr614 V.5 - Time is wrong

The title basically sums it up. The clock in my Netgear wgr614 router (version 5) is wrong.

 

It got reset back to January 1, 2003. While the functionality of the router works, when it sends email alerts, it sends them saying it was sent in 2003.

 

I could find no settings to set the clock, and Netgear's web site was no help. A Netgear Forum suggested reflashing the firmware, but that was no help....

 

Any help to get the time right? 

6 Operator

 • 

14.4K Posts

October 13th, 2008 20:00

on page 5-7 of your manual do you have the correct time zone set?  did you tick the box for daylight savings time?

 ftp://downloads.netgear.com/files/wgr614v5_ref_manual.pdf

Did you try doing a reset of your router? This generally involves holding in a button on the back. Note this will reset your router to factory settings so you will need to reenter all your settings. page b6-7 of manual

 

Just my .02

6 Operator

 • 

14.4K Posts

October 13th, 2008 23:00

Ahh DD_wrt.. ran that on my old WRT54g. Running a WRT600n now..

2 Intern

 • 

2.2K Posts

October 13th, 2008 23:00

The time zone is set correctly (and I'm guessing that would have no effect on the year....) and I did reset the unit. I did that after reinstalling the firmware didn't work.

 

No luck at all... It is not a router killing problem, but still is an oddity.

 

And, while technically not a router killer, I was just at Fry's Electronics and they have refurdished NetGear RangeMax 824's for $30...

 

Comments? 

6 Operator

 • 

14.4K Posts

October 13th, 2008 23:00

Cheap price. not much to lose I suppose. Im more partial to Linksys myself.

2 Intern

 • 

2.2K Posts

October 13th, 2008 23:00

Actually, I have an old Linksys WRT54G (forget the revision, but its old enough to put custom firmware on) sitting in a closet....:smileyhappy:

2 Intern

 • 

2.2K Posts

October 18th, 2008 04:00

UPDATE:

 

The time is now okay, so I am guessing it was an issue with the time server NetGear chooses it to use. 

No Events found!

Top