Share via

Event ID 47 — Manual Time Source Acquisition

  • Article

Applies To: Windows Server 2008

An Active Directory forest has a predetermined time synchronization hierarchy. The Windows Time service (W32time) synchronizes time between computers within the hierarchy, with the most accurate reference clocks at the top. If more than one time source is configured on a computer, Windows Time uses Network Time Protocol (NTP) algorithms to select the best time source from the configured sources, based on the computer’s ability to synchronize with that time source. The Windows Time service acquires a time source peer from the domain heirarchy. By default, computers running the Windows Time service attempt to synchronize time only with a domain controller or a manually configured time source. Currently, the Windows Time service is synchronizing with a manually configured time source peer (as opposed to a time source peer from the domain hierarchy).

Event Details

Product: Windows Operating System
ID: 47
Source: Microsoft-Windows-Time-Service
Version: 6.0
Symbolic Name: MSG_MANUAL_PEER_TIMEOUT
Message: Time Provider NtpClient: No valid response has been received from manually configured peer %1 after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS name. The error was: %2

Resolve

Address peer discovery issues

The Windows Time service lost contact with its configured time source peer. Event ID 47 may indicate temporary communication issues on the network. If the event is recorded repeatedly, ensure that the local computer can communicate with the time source peer over the network and that the time source peer is online. 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 determine the name of the currently configured 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 /query /status, and then press ENTER. The command displays the status of the Windows Time service synchronization. Check the computer name that is shown as the Source in the command output. This should be the name of a domain controller (or administrator-configured time server).

Ensure that a firewall does not block User Datagram Protocol (UDP) port 123 on the local computer or on the time source peer and that there is no firewall between the two systems. For information about configuring the Windows Firewall, see The New Windows Firewall in Windows Vista and Windows Server 2008 (https://go.microsoft.com/fwlink/?LinkId=85301).

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 synchornization. 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 synchronized successfully with a time source peer, verify that Event ID 37 appears in Event Viewer. If there was a recovery from a previous failure to synchronize with the time source, you also see Event ID 137, which indicates that the Windows Time service is synchronized correctly.

For more information about the Windows Time service, see Windows Time Service Technical Reference (https://go.microsoft.com/fwlink/?LinkID=25393).

Manual Time Source Acquisition

Active Directory