Windows Server 2003 R2 and Windows XP SP3 (All 32-bit)Registry Settings for Windows TimePDC - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\ Type = NTPMember clients and non-PDC domain controllers - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\ Type = NT5DSGetting events below:-Event Type: WarningEvent Source: W32TimeEvent Category: NoneEvent ID: 24Date: 2/19/2010Time: 12:20:54 PMUser: N/AComputer: XXX-XX-XX-XXXXDescription:Time Provider NtpClient: No valid response has been received from domain controller XXX-XX-XX-XXXX.xx.xx.xxxxx after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Event Type: ErrorEvent Source: W32TimeEvent Category: NoneEvent ID: 29Date: 2/19/2010Time: 12:20:54 PMUser: N/AComputer: XXX-XX-XX-XXXXDescription:The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 15 minutes. NtpClient has no source of accurate time. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Event Type: InformationEvent Source: W32TimeEvent Category: NoneEvent ID: 38Date: 2/19/2010Time: 12:23:42 PMUser: N/AComputer: XXX-XX-XX-XXXXDescription:The time provider NtpClient cannot reach or is currently receiving invalid time data from XXX-XX-XX-XXXX.xx.xx.xxxxx (ntp.d|x.x.x.x:123->x.x.x.x:123).For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. · I have tried w32tm /unregister & w32tm /register · DNS is working fine · Can ping the time server (PDC) from the clients · Only seems to have happened since applying the security templates defined in the Microsoft document Windows Server 2003 SP2 R2 Common Criteria Configuration Guide 3.0 which is a requirement in this environment - http://www.microsoft.com/downloads/details.aspx?FamilyId=4F7B6A93-0307-480F-A5AF-A20268CBD7CC&displaylang=en Does anyone know how to resolve this?

Hi,Try this on the domain controller (PDC) http://technet.microsoft.com/en-us/library/cc786897(WS.10).aspxEg: w32tm /config /manualpeerlist:"0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org" /syncfromflags:manual /reliable:yes /updateTry this on Windows XP client http://technet.microsoft.com/en-us/library/cc758905(WS.10).aspxEg: w32tm /config /syncfromflags:domhier /update net stop w32time && net start w32timeCompare the Domain Controller (PDC) Registry again this http://support.microsoft.com/default.aspx/kb/816042Hope you find the info useful

Hi - thanks for your response. I am unable to complete your first suggestion as the environment is air-gapped and thus has no access to an Internet NTP source. I have tried the suggestion for the client and this did not work. Still get the same error message when trying to resync the time and the time remains offset from the PDC. I'm not 100% sure on the PDC should be configured in an environment where there is no access to an NTP server and no internal hardware clock - any ideas? Jonathan

Hi, Have you tried the following steps in the article below: How to configure an authoritative time server in Windows Serverhttp://support.microsoft.com/default.aspx/kb/816042 "To configure the PDC master without using an external time source, change the announce flag on the PDC master. The PDC master is the server that holds the forest root PDC master role for the domain. This configuration forces the PDC master to announce itself as a reliable time source and uses the built-in complementary metal oxide semiconductor (CMOS) clock. To configure the PDC master by using an internal hardware clock, follow these steps: 1. Click Start, click Run, type regedit, and then click OK. 2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags3. In the right pane, right-click AnnounceFlags, and then click Modify. 4. In Edit DWORD Value, type A in the Value data box, and then click OK. 5. Quit Registry Editor. 6. At the command prompt, type the following command to restart the Windows Time service, and then press ENTER: net stop w32time && net start w32time"Thanks.This posting is provided "AS IS" with no warranties, and confers no rights.

I had tried that unsuccessfully but I have now resolved this myself! I ran the command w32tm /config /syncfromflags:domhier /reliable:yes /update on the PDC and then stopped and started the w32time service. Now when I run the w32tm /resync command on clients pointing towards the PDC they update successfully. Thanks for your help with this anyway guys. Jonathan

Glad to hear you have resolved the problem. If you have more questions in the future, you’re welcomed to this forum. Thanks.This posting is provided "AS IS" with no warranties, and confers no rights.