I've noticed these errors in event viewer on the domain controller: Event Type: Warning Event Source: W32Time Event Category: None Event ID: 47 Computer: <var>ComputerName</var> Time Provider NtpClient: No valid response has been received from manually configured peer time.windows.com,0x1 after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS name. The error was: The peer is unreachable. Source:Microsoft-Windows-Time-Service Event ID: 36 Task Category: None Level: Warning Description: The time service has not synchronized the system time for 86400 seconds because none of the time service providers provided a usable time stamp. The time service will not update the local system time until it is able to synchronize with a time source. If the local system is configured to act as a time server for clients, it will stop advertising as a time source to clients. The time service will continue to retry and sync time with its time sources. Check system event log for other W32time events for more details. Run 'w32tm /resync' to force an instant time synchronization. My question is what are the ramifications of this or can it be ignored, because the problem seems to be intermittent.

I don't think you have anything to worry about, your time info will sync next time it connects up, you may want to list some secondary time servers, probably connectivity issues with your ISP Here is a list of the atomic clock time servers in boulder colorado: http://tf.nist.gov/tf-cgi/servers.cgi:P Advice offered, If you need more help it is advised to seek the council and advice of paid professionals. The answer is always 42, or reboot.

Chect this article. It will help you. Thanks

Event Type: Warning Event Source: W32Time Event Category: None Event ID: 47 Computer: <var>ComputerName</var> Time Provider NtpClient: No valid response has been received from manually configured peer time.windows.com,0x1 after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS name. The error was: The peer is unreachable. If you're running windows 2003, try the following; logon on the machine and open the "system" eventlog, leave it open, next fire an "admin" command prompt (cmd.exe) and, at the prompt, enter the following commands net time /setsntp:pool.ntp.org,0x1 net stop w32time net start w32time w32tm /resync /rediscover once entered the last command, which will force a time-resync, check the system eventlog, if things are working as expected you should see some messages related to the timeservice and reporting the sync progress Note: the "0x1" after the timeserver name is needed to let the timeservice understand that the NTP server is specified by name and not by IP address, in case you want to enter more servers by name, you will need to enclose them in double quotes and add the ",0x1" after each name, for example "0.pool.ntp.org,0x1 1.pool.ntp.org,0x1 2.pool.ntp.org,0x1 3.pool.ntp.org,0x1"

PDC is trying to synchornize with the Time server and was not able to connect for that period. The only issue is any of the server didnt sychronize with the PDC emulator for the time service. Services can affect which are AD intergrated. Better to have an external time server/secondary time server.If you found this post helpful, please "Vote as Helpful". If it answered your question, remember to "Mark as Answer". MCSE,MSCITP-EA

This was a big help Thanks