Even ID:54 Windows时间服务不能找到域控制器

Event ID: 54
Source	w32time
Type	Warning
Description	The Windows Time Service was not able to find a Domain Controller. A time and date update was not possible.
Comments	Ionut Marin (Last update 8/18/2004): As per Microsoft: “These issues may occur if the Norton AntiVirus Auto-Protect service is running". See Q810402 for details on this problem. Q223184 lists the registry entries that control aspects of the W32Time service. Peter Van Gils (Last update 3/20/2004): Check DNS settings and network connectivity and then run “w32tm /resync /nowait”. Adrian Grigorof (Last update 4/27/2003): Windows 2000 computers are attempting to synchronize their time with a domain controller. If none is found this message is generated. The domain controller must run the w32time service. This service can be syncronized with an external source (ie.atomic clocks like the one maintained by Navy Observatory). A syncronized time is very important for Active Directory implemenations due to its distributed nature. As per Microsoft: "This issue can occur because of repeated network issues or if the Time service has been unable to find a domain controller to synchronize with for a long time. To reduce network traffic, the Time service will wait 960 minutes before it tries again, and no synchronization takes place during this interval, even if network connectivity is restored after being in a disconnected state for an amount of time that is less than the synchronization interval." I have seen this occuring on a newly configured domain controller that had its DNS settings pointing to external DNS servers. Since the server would try to find the Domain Controller quering a DNS server the query would  fail and this event recorded.
Links	Q223184 , Q312534 , Q810402 , Windows 2000 Time
Search	Microsoft Support  -   Microsoft Search  -   Google Groups  -   Google Microsoft  -   EventID.Net Queue  -   More links...
Various	Send comments   -    Notify me when updated