When SpecialPollInterval is used as a polling interval, the Windows Time service does not correct the time if the service gets into Spike state

Article ID: 2638243 - View products that this article applies to.
Expand all | Collapse all

Symptoms

An NTP client computer that is running Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8 or Windows Server 2012, may not correct the time if the following conditions are true:
  • The NTP client syncs its time with the manually specified NTP server.
  • The NTP client uses SpecialPollInterval as a polling interval.
  • The time offset between the NTP client and the NTP server is greater than the LargePhaseOffset as configured in the NTP client.
In this situation, the NTP client cannot correct its time even after waiting for SpikeWatchPeriod to pass.
Back to the top | Give Feedback

Cause

This problem occurs because the NTP client gets into SPIKE state every time the client polls the time sample to the NTP server. The Time service manages its internal status, and if the client gets into SPIKE state, the client does not sync its time.
Back to the top | Give Feedback

Resolution

To work around this issue so that the NTP client is enabled to sync with the NTP server after a SPIKE state, configure Windows Time to use the MinPollInterval/MaxPollInterval as the polling interval.

To have us configure Windows Time to use the MinPollInterval/MaxPollInterval as the polling interval for you, go to the "Fix it for me" section. If you prefer to configure Windows Time to use the MinPollInterval/MaxPollInterval as the polling interval yourself, go to the "Let me fix it myself" section.

Fix it for me

Collapse this imageExpand this image
To configure Windows Time to use the MinPollInterval/MaxPollInterval as the polling interval, click the Fix it button or link. Then click Run in the File Download dialog box, and follow the steps in the Fix it wizard.

For Windows 8
Collapse this imageExpand this image
Collapse this imageExpand this image
Fix this problem
(http://go.microsoft.com/?linkid=9824396 )

Microsoft Fix it 25001
Collapse this imageExpand this image

Collapse this imageExpand this image

For Windows 7, Windows Vista, Windows Server 2008 
Collapse this imageExpand this image
Collapse this imageExpand this image
Fix this problem
(http://go.microsoft.com/?linkid=9811182 )

Microsoft Fix it 50877
Collapse this imageExpand this image
Collapse this imageExpand this image

Notes
Collapse this imageExpand this image
  • This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.
  • If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.
  • We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the "Fix it for me
    (http://blogs.technet.com/fixit4me/)
    " blog or send us an email
    (mailto:fixit4me@microsoft.com?Subject=KB)
    message.
Collapse this imageExpand this image
Collapse this imageExpand this image

Let me fix it myself

Collapse this imageExpand this image
To configure Windows Time to use the MinPollInterval/MaxPollInterval as the polling interval, follow these steps: 

  1. Click Start, click Run, type cmd, and then press ENTER.

    Note In Windows 8 or Windows Server 2012, press the Windows logo Key+R to open the Run box, type cmd in the Run box, and then press ENTER.
  2. At the command prompt, type the following command. After you type the command, press ENTER.

    w32tm /config /update /manualpeerlist:NTP_server_IP_Address,0x8 /syncfromflags:MANUAL

Note When you use the 0x1 flag with the /manualpeerlist switch, you specify use of SpecialPollInterval. To work around this problem, do not use the 0x1 flag.
Collapse this imageExpand this image
Back to the top | Give Feedback

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

More information

The polling interval that Windows Time uses is set by the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters

If the value of the NtpServer entry in this subkey contains 0x1, Windows Time uses SpecialPollInterval as the polling interval. Otherwise, Windows Time uses MinPollInterval/MaxPollInterval. For additional Information about the Windows Time Service and registry values, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/cc773263(WS.10).aspx
(http://technet.microsoft.com/en-us/library/cc773263(WS.10).aspx)
Back to the top | Give Feedback

Properties

Article ID: 2638243 - Last Review: January 24, 2013 - Revision: 11.0
Applies to
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Foundation
  • Windows Server 2008 Standard
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Foundation
  • Windows Server 2008 R2 Standard
  • Windows Vista Business
  • Windows Vista Enterprise
  • Windows Vista Ultimate
  • Windows 7 Enterprise
  • Windows 7 Professional
  • Windows 7 Ultimate
  • Windows 8 Enterprise
  • Windows Server 2012 Datacenter
  • Windows Server 2012 Essentials
  • Windows Server 2012 Foundation
  • Windows Server 2012 Standard
Keywords: 
KB2638243
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top