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...
Further testing... it will not recognize/act on any name, only an ip address.
This is in non-dhcp mode... I added dns entries... no help
I'm guessing that it MIGHT work if you were in DHCP mode, but I cannot have my AP jumping around on different ip addresses and having to find it with a program each time I want to change a setting.
So, I will have to check periodically that the ip address I use is still good. I use the ip address from pool.ntp.org, a pool of ntp servers, definitely more reliable than a single ntp server from microsoft or netgear. (and i'm pretty sure a higher stratum level clock).
Thanks again for the suggestions... it was a small thing, but irritating.
Greg
This is in non-dhcp mode... I added dns entries... no help
I'm guessing that it MIGHT work if you were in DHCP mode, but I cannot have my AP jumping around on different ip addresses and having to find it with a program each time I want to change a setting.
So, I will have to check periodically that the ip address I use is still good. I use the ip address from pool.ntp.org, a pool of ntp servers, definitely more reliable than a single ntp server from microsoft or netgear. (and i'm pretty sure a higher stratum level clock).
Thanks again for the suggestions... it was a small thing, but irritating.
Greg