As an addition to thread585-1388102 and its predecessor.
Following the recent (last week or so) tardiness of the Netgear ntp servers, whereby the router would spend a day or two with the default date-time following reset, I dug further.
I have an Ubuntu machine on the LAN already running ntpd for its own time sync, so it was easy to set it also as a ntp server. Pointing the DG834G to the local machine for its time sync solved the e-mail date problem.
There has also been a recent thread in the netgear.com forum, regarding the poor performance of time-*.netgear.com, where someone mentioned using time.nist.gov at 192.43.244.18 instead of the default Netgear server. I tried setting this IP in the router and it, too, solves the e-mail date problem.
So, quite what's going wrong with time-*.netgear.com I don't know, but it seems that we've been looking in the wrong direction for the last few years!
Perhaps someone else could give it a try, just in case I've missed something? Ta!
--
Nick.
Following the recent (last week or so) tardiness of the Netgear ntp servers, whereby the router would spend a day or two with the default date-time following reset, I dug further.
I have an Ubuntu machine on the LAN already running ntpd for its own time sync, so it was easy to set it also as a ntp server. Pointing the DG834G to the local machine for its time sync solved the e-mail date problem.
There has also been a recent thread in the netgear.com forum, regarding the poor performance of time-*.netgear.com, where someone mentioned using time.nist.gov at 192.43.244.18 instead of the default Netgear server. I tried setting this IP in the router and it, too, solves the e-mail date problem.
So, quite what's going wrong with time-*.netgear.com I don't know, but it seems that we've been looking in the wrong direction for the last few years!
Perhaps someone else could give it a try, just in case I've missed something? Ta!
--
Nick.