NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
WNDAP350 - time stuck in January 2000, NTP ignored
Yep, now have two of them... of course support says: reset completely, reboot, etc. Seems that the time increments, and the days do, but no matter what, I'm in january and worse, the year 2000. Oh...
Great, hope the support people get the info!
The straight ip address worked.
I noticed that I had not filled in any DNS entries... so I added some dns servers and put the pool.ntp.org back in, will see if that works too...
Seems pretty dumb, but maybe that is a problem, since I have it on a static address, with dhcp disabled, then it probably cannot resolve a named server.
That's maybe why the default time-b.netgear.com NEVER WORKED out of the box and the support people were clueless.
Thanks for the information and spurring my mind (connecting the ip address working with lack of DNS resolution).
Regards, Greg
The straight ip address worked.
I noticed that I had not filled in any DNS entries... so I added some dns servers and put the pool.ntp.org back in, will see if that works too...
Seems pretty dumb, but maybe that is a problem, since I have it on a static address, with dhcp disabled, then it probably cannot resolve a named server.
That's maybe why the default time-b.netgear.com NEVER WORKED out of the box and the support people were clueless.
Thanks for the information and spurring my mind (connecting the ip address working with lack of DNS resolution).
Regards, Greg