Windows Server 2003'te ve Windows XP'de W32Time sık sık günlüğe Olay Kimliği 50 kaydediyor ve saat eşitlemesi düzgün yapılmıyor

Event ID: 50
Source: W32time
Type: Warning
The time service detected a time difference of greater than 5000 milliseconds for 900 seconds. The time difference might be caused by synchronization with low-accuracy time sources or by suboptimal network conditions. The time service is no longer synchronized and cannot provide the time to other clients or update the system clock. When a valid time stamp is received from a time service provider, the time service will correct itself.
In the default domain hierarchy, when a Microsoft Windows Server 2003-based child domain controller tries to synchronize the time, you may receive the following event messages:

Event ID: 38
Source: W32time
Type: Information
The time provider NtpClient cannot reach or is currently receiving invalid time data from yourpdc.forestroot.com (ntp.d|65.53.232.135:123->65.53.250.22:123).

Event ID: 47
Source: W32time
Type: Warning
Time Provider NtpClient: No valid response has been received from manually configured peer yourpdc.forestroot.com after eight 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.

Event ID: 29
Source: W32time
Type: Error
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.

İlgili KB: http://support.microsoft.com/?scid=kb%3Ben-us%3B830092&x=7&y=13

Leave a Reply

Your email address will not be published. Required fields are marked *

− 1 = 5