| Event Id | 54 |
| Source | w32time |
| Description | The Windows Time Service was not able to find a Domain Controller. A time and date update was not possible. |
| Event Information | According To Microsoft: CAUSE: 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. MORE INFORMATION: Accumulated time errors may cause certain network operations to fail. To update the Time service and let it know that network connectivity has been restored and that it should resynchronize, use any of the following commands at a command prompt: net stop w32time w32tm -s net start w32time NOTE: Because the Forest Root DC is the timesource for the whole forest, it has to be configured manually to synchronize time with an external time source. Also, if time synchronization with an Internet source isnt critical, you can also configure the DC with the PDC master role to be the authoritative time server. |
| Reference Links | Resolution Clients Cannot Join a Domain with Norton Internet Security 2002 Forest root domain controllers may display system events 54 and 64 More Information From One Of The Group |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.