Login to Account Create an Account
Problem: Synchronizing Time on 2k3 PDC with External Source
Posted 07 April 2011 - 07:52 AM
Anyway, the network administrators before me set the default domain policy to configure the "Configure the Windows NTP Client" and the "Enable WIndows NTP client" to be enabled. Obviously since our domain controllers were in the domain that this policy was being issued to, they are getting these settings as well. I went ahead and made an OU and put the domain controllers in there and enforced the "Default domain controllers policy" GPO so that should override any settings the default domain policy issues. Of course, the default domain controllers policy has all three of the time settings discussed here set as "not configured". I went ahead and did a gpupdate /force on the domain controller with the PDC fsmo role and then logged off and logged back on. The problem was that I was getting the same error. Is this something that I will have to restart the domain controller for all the settings of the enforced "default domain controllers policy" to take effect? I really don't want to restart this domain controller seeing as it is running DHCP and DNS.
Posted 17 October 2014 - 04:57 PM
You have to be very sure you followed the instructions for using an external time source correctly. I've used these instructions on many a 2K3 server without issue, so to recap:
1. Change Windows to use the NTP protocol for time synchronization:
2. Configure the AnnounceFlags value:
3. Enable the NTP server value:
4. Specify the NTP server to use:
5. Select the NTP polling interval:
6. Configure the time correction settings:
After this, stopping and restarting the NTP service should get you working. If it does not, check the value configured in step 4 - this being misconfigured is the only time I've seen errors in the Windows Time service like the ones you've posted, so it's possible this is incorrect in your registry. I would also suggest using a time server OTHER than time.nist.gov, as it is a VERY busy time server and you are likely to miss one or two time syncs to it before you get a good one. I would suggest using another time server, preferrably a stratum-2 NTP server closer to you. You can find these listed here:
Works great on my SBS 2003 server. Thanks!
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users