| Event Id | 29 |
| Source | w32time |
| 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 %1 minutes. NtpClient has no source of accurate time. |
| Event Information | According to Microsoft : Cause : The Windows Time Service cannot synchronize time with its time sources. Windows Time Service will attempt synchronization at a later time. The W32time 29 message is usually caused by connectivity issues between a client and its source. In some cases, the source computer is unavailable; it may be restarting, disconnected from the network, or unreachable because of firewall or router configurations. If the W32time 29 condition persists, you should immediately troubleshoot the issue to ensure that successful synchronization can resume. User Action: To ensure that the system can connect to the source, do one or more of the following: 1.Verify that the local computer is capable of contacting the desired source. In most cases, a simple connectivity test such as “ping” is adequate. 2.Confirm that Windows Time Service (or other NTP Time Service) is running and available on the source system. 3.If you are using a manually configured peer, such as time.windows.com, verify that the name is typed correctly and that the system is available. 4.Confirm that there are no network devices that block traffic on port 123 between the local computer and the time source. W32time 29 is not a critical message when logged occasionally. It indicates that the system is unable to synchronize, which can present a problem if the condition persists. Always monitor the system after this message appears to ensure that synchronization resumes successfully. |
| Reference Links | Event ID 29 From Source w32time |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.