Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 47 Source: W32Time
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.
|English: Request a translation of the event description in plain English.|
- Description: No valid response has been received from manually configured peer - In my case, I was not able to synchronize the PDC server, which was an NTP server as well, and all other clients were synchronizing their times according to this server.
1. Set all servers in the domain to be synchronized by your PDC.
- nltest /dclist:domain
- for /f "tokens=1, *" %i in (servers.txt) do net time \\%i /setsntp:PDC-NTP-Server /y >> result.txt
The file servers.txt contains a list of your servers.
- net time /domain:domain name /set
2. Modify the registry to set the time server. Go to HKLM\System\CurrentControlSet\Services\lanmanserver\parameters and add a key TimeSource (reg_dword) with a value of 1.
3. This problem may occur when your computer sends synchronization requests by using symmetric active mode. By default, Windows Server 2003 domain controllers are configured as time servers and use symmetric active mode to send synchronization requests. Some NTP servers that do not run Windows respond only to requests that use client mode.
Click Start, click Run, type cmd, and then press Enter. At the command prompt, type the following commands in the order that they are given. After you type each command, press Enter:
• w32tm /config /manualpeerlist:NTP_server_IP_Address, 0x8 syncfromflags:MANUAL
• net stop w32time
• net start w32time
• w32tm /resync
See ME875424 for details.
After applying these steps, the problem should be solved.
See ME875424 for a solution to the time synchronization problem.
If the computer generating this message is configured to synchronize its time with an NTP server, it is possible that the server is not available. A common setting that may cause problem is having the NTP server specified as "time.microsoft.com". Get a "good" server from the list of Internet-based NTP servers see the US Navy Naval Observatory link below.
See ME830092 for a hotfix. This article applies to Windows Server 2003.
|Private comment: Subscribers only. See example of private comment|
|Links: USNO NTP Network Time Servers|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated