Event ID - 132

Event Id	132
Source	Microsoft-Windows-Time-Service
Description	NtpClient was unable to set a domain peer to use as a time source because of duplicate error on '%3'. The same time source '%4' has been specified as manual peer in NtpServer. NtpClient will try again in %2 minutes and double the reattempt interval thereafter. The error was: %1
Event Information	According to Microsoft : Cause : This event is logged when NtpClient was unable to set a domain peer to use as a time source because of duplicate error. Resolution : Configure an appropriate time source peer The local Windows Time service is attempting to synchronize from a time source peer that is configured to synchronize from the local Windows Time service. You cannot have two computers running Windows Time service that are configured to synchronize from each other. To resolve this issue, configure the local Windows Time service to use a different time source peer or modify the configuration of the current time source peer to use a different time source peer. Perform the following procedure on the computer that is logging the event to be resolved. To perform this procedure, you must have membership in Administrators or you must have been delegated the appropriate authority. To configure a manual time source peer: 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. At the command prompt, type w32tm /config /manualpeerlist:server,0x8, /syncfromflags:manual /update, where server is the name of the time source that you want to configure, and then press ENTER. 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: 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. At the command prompt, type W32TM /resync, and then press ENTER. At the command prompt, type W32TM /query /status, and then press ENTER. This 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 an administrator-configured time server) in the same Active Directory domain as the local computer. To verify that the Windows Time service synchronized successfully with its time source, confirm that Event IDs 35 and 37 appear in Event Viewer. If there was a recovery from a previous failure to synchronize with the time source, you also see Event ID 138, which indicates that the Windows Time service is synchronized correctly.
Reference Links	Event ID 132 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