|
pool.ntp.org is a pool of reliable public time servers. Point your server to that, or point it to your router if policy says no external (finger)pointing. By the way, what is the reason given for prohibiting external time source?
Sincerely, _____ (, / | /) /) /) /---| (/_ ______ ___// _ // _ ) / |_/(__(_) // (_(_)(/_(_(_/(__(/_ (_/ /) (/ Microsoft MVP - Directory Services www.akomolafe.com - we know IT -5.75, -3.23 Do you now realize that Today is the Tomorrow you were worried about Yesterday? -anon From: Steven Johnston Sent: Fri 9/15/2006 8:32 AM To: ActiveDir@mail.activedir.org Subject: [ActiveDir] Windows Time Service Hi Guys, I have a small site with 2 DCs, the pdc emulator originally did not sync with any external source, I made the changes so it would seek an external source but now due to ‘policy’ it needs to sync to its internal clock. When I change the registry entry for ‘Type’ from ‘NTP’ to ‘Nt5DS’ I notice a lot of log entries in the system logs, these are w32time event ids 62 (this machine is a pdc of the domain at the root of the forest, configure to sync from external time source using the net command) and eventually 64 (because of repeated network problems the time service has not been able to find a domain controller to synchronize with for a long time. To reduce network traffic the time service will wait 960 minutes before trying again … etc….) Is there a way I can stop these annoying messages or should I just ignore them? I found out that by leaving the ‘Type’ as NTP and making ‘NtpServer’ the DC’s name these message no longer appear, are there any issues with setting it up this way? Regards, |
