Time synchronization may not succeed when you try to synchronize with a non-Windows NTP server in Windows Server 2003 (875424)

SYMPTOMS

When you try to synchronize your Microsoft Windows Server 2003-based computer to a Network Time Protocol (NTP) server that is not running Microsoft Windows, the synchronization may not succeed. When this problem occurs, the following events may be recorded in the System log:Event Type: Information Event
Source: W32Time
Event Category: None
Event ID: 38
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description: The time provider NtpClient cannot reach or is currently receiving invalid time data from NTP_server_IP_Address. For more information, see Help and Support Center at http://support.microsoft.com. Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 47
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description: Time Provider NtpClient: No valid response has been received from manually configured peer NTP_server_IP_Address 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. For more information, see Help and Support Center at http://support.microsoft.com.Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description: 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://support.microsoft.com.