You are currently offline, waiting for your internet to reconnect

Time synchronization may not succeed when you try to synchronize with a non-Windows NTP server in Windows Server 2003

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

SYMPTOMS
When you try to synchronize your Microsoft Windows Server 2003-based computer to a Network Time Protocol (NTP) server that is not running Microsoft Windows, the synchronization may not succeed. When this problem occurs, the following events may be recorded in the System log:

Event Type: InformationEvent
Source: W32Time
Event Category: None
Event ID: 38
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:The time provider NtpClient cannot reach or is currently receiving invalid time data from NTP_server_IP_Address. For more information, see Help and Support Center at http://support.microsoft.com.

Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 47
Date: Date
Time: Time
User: N/A
Computer: ComputerName
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. For more information, see Help and Support Center at http://support.microsoft.com.

Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: Date
Time: Time
User: N/A
Computer: ComputerName
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. For more information, see Help and Support Center at http://support.microsoft.com.

CAUSE
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.
RESOLUTION
To resolve this problem, configure Windows Time to use client mode when it synchronizes with the time server. To do this, follow these steps:
  1. Click Start, click Run, type cmd, and then press ENTER.
  2. 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
MORE INFORMATION
The mode that Windows Time uses to send requests is set by the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer
If the value of the Enabled entry in this subkey is 1, Windows Time uses symmetric active mode. Otherwise, Windows Time uses client mode.

The 0x8 setting that is referenced in the command in the "Resolution" section sets Windows Time to use client mode.

The valid settings for the mode used with the /manualpeerlist switch include the following:
  • 0x01 - use special poll interval SpecialInterval
  • 0x02 - UseAsFallbackOnly
  • 0x04 - send request as SymmetricActive mode
  • 0x08 - send request as Client mode
Properties

Article ID: 875424 - Last Review: 10/30/2006 21:29:59 - Revision: 3.2

  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • kbtshoot kbprb KB875424
Feedback
>tml>ipt>");