NtpClient was unable to find a domain

[HansL]

Hello guys,

I have this error on several machines for some time now :
Does anybody know the solution?

* System Event
* Source: W32Time
* Event ID : 49

The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will continue trying to locate a DC every 960 minutes. This message will not be logged again until after a domain controller is found.

Thanks alot
Hans

 

[gpalmer711]

This is not an important error. Windows XP has the facility to sync your time with a time server to make sure you always have the correct time. This error occurs if it cannot connect to the server that is set.

Go to Start > Settings > Control Panel > Date and Time > Internet Time Tab.

I personally get this error if the server is set to "Time.windows.com so I set it to "time.nist.gov". Once you have changed the server, click on Update now to make sure you can connect to the server.

Alternativly you can disable this feature in the same Tab.

Greg Palmer

----------------------------------------
Any feed back is appreciated.

 

[HansL]

Thank you Greg !

 

[bcastner]

I disagree with Greg on this. The message you can ignore as he describes is:
[tt]
Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 36
Date: 11/18/2003
Time: 3:21:03 PM
User: N/A
Computer: bcastner
Description:
The time service has not been able to synchronize the system time for 49152 seconds because none of the time providers has been able to provide a usable time stamp. The system clock is unsynchronized.

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

[/tt]

Your message is a similar issue, but in a Domain setting you cannot simply select a NTP time server but have to synchronize with the primary DC. You could find yourself unable to authenticate with the domain if the time synchronization strays too far.

Solution:

http://support.microsoft.com/defaul...port/kb/articles/Q258/0/59.ASP&NoWebContent=1

I agree with Greg that I might ignore an occasional error message of this type, but not several. Follow the instructions in the KB article.