Event ID - 51

Event Id51
SourceMicrosoft-Windows-Time-Service
DescriptionTime Provider NtpClient: The time sample received from peer %1 differs from the local time by %2 seconds. The observed transmission delay from the server was %3 milliseconds.
Event InformationAccording to Microsoft :
Cause :
This event is logged when the time sample received from peer differs from the local time by seconds.
Resolution :
Resolve time source inconsistencies
The Windows Time service received inconsistent time data, which resulted in a large time change. This event can indicate an unreliable time source, network connectivity issues, latency with the time source clock, or a hardware malfunction.
Possible solutions include:
  • Checking to see if the system has any time source software other than Microsoft time source software. If so, remove that software, and then see if the issue is resolved.
  • Verifying network connectivity to the time source.
  • Checking the time source for malfunctions.
Verify :
To perform this procedure, you must have membership in Administrators or you must have been delegated the appropriate authority.
To verify that the Windows Time service is synchronizing correctly:
  1. Open a command prompt as an administrator. To open a command prompt as an administrator, click Start. In Start Search, type Command Prompt. At the top of the Start menu, right-click Command Prompt, and then click Run as administrator. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  2. At the command prompt, type W32TM /resync, and then press ENTER.
  3. At the command prompt, type W32TM /query /status, and then press ENTER. The command displays the status of the Windows Time service synchronization. The Last Successful Sync Time line of the output displays the date and time that you ran the W32TM /resync command in the previous step. Also, check the computer name that is shown as the Source. This should be the name of a domain controller (or administrator-configured time server).
To confirm that the Windows Time service was synchronized successfully with its time source when you ran the W32TM /resync command, verify that Event ID 35 appears in the Event Viewer.
Reference LinksEvent ID 51 from Source Microsoft-Windows-Time-Service

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.
 Refresh