Event ID - 13

Event Id13
SourceMicrosoft-Windows-Time-Service
DescriptionTime Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but the computer is joined to a Windows NT 4.0 domain. Windows NT 4.0 domain controllers do not have a time service and do not support domain hierarchy as a time source. NtpClient will attempt to use an alternate configured external time source if available. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.
Event InformationAccording to Microsoft :
Cause :
This event is logged when the machine is configured to use the domain hierarchy to determine its time source but the computer is joined to a Windows NT 4.0 domain.
Resolution :
Configure a manual peer, or join the computer to a Windows 2000, Windows Server 2003, or Windows Server 2008 domain (NT5DS)
The computer running the Windows Time service client is configured as a member of a Windows NT 4.0 domain. This computer should be joined to a domain running AD DS or it should configured to use a manual time source peer. Perform the following procedures on the computer that is logging the event to be resolved.
To perform these procedures, must have membership in Administrators or must have been delegated the appropriate authority.
To join a new domain:
  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 sysdm.cpl, and then press ENTER. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.The System Properties dialog box opens.
  3. On the Computer Name tab, click Change. The Computer Name/Domain Changes dialog box opens.
  4. Under Member of, ensure that Domain is selected. Type the name of the domain in the box.
  5. When you are prompted, type your domainname\username and password to join the computer to the domain, where domainname is the name of the domain where your user account exists.
  6. When the domain is found, the membership is confirmed. Click OK.
  7. Restart the computer when you are prompted.
To configure a manual time source peer:
  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 /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:
  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.
    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 LinksEvent ID 13 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.