Home | Site Map | Cisco How To |  Net How To | Wireless | Search | Forums | Services | Setup Guide | Careers | About Us | Contact Us|

Event ID 38, 47 and 29 - Source: W32Time

The time provider NtpClient cannot reach or is currently receiving invalid time data from NTP_server_IP_Address.

Time Provider NtpClient: No valid response has been received from manually configured peer NTP_server_IP_Address after 8 attempts to contact it.

The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible.

Symptoms: When checking the Event Viewer, you may have the following Event ID:

Source: W32Time
Event ID: 38
Description: The time provider NtpClient cannot reach or is currently receiving invalid time data from NTP_server_IP_Address.

Event Source: W32Time
Event ID: 47
Description: Time Provider NtpClient: No valid response has been received from manually configured peer NTP_server_IP_Address 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.

Event Source: W32Time
Event ID: 29
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 15 minutes. NtpClient has no source of accurate time.

Cause: By default, Windows Server 2003 domain controllers are configured as time servers and use symmetric active mode to send synchronization requests. However, some NTP servers requests to use client mode only.

Resolution: 1. To resolve this problem, configure Windows Time to use client mode with 0x08 (send request as Client mode) when it synchronizes with the time server. To do this, follow these steps:

2. How to configure Windows Time Server to use an external time source on a Windows 2003

Related Topics

Bob Lin Photography services

Real Estate Photography services