Microsoft KB Archive/940742

= The Windows Time service in Windows Server 2003 does not synchronize time with a time server if the precision value of the NTP response is less than -30 =

Article ID: 940742

Article Last Modified on 10/11/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows Server 2003, Standard x64 Edition
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, Datacenter x64 Edition
 * Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
 * Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems

-



SYMPTOMS
In Windows Server 2003, the Windows Time service does not synchronize time with a time server if the precision value of the Network Time Protocol (NTP) response is less than -30. Instead, the Windows Time service discards the response. For example, this problem occurs when the precision value of the NTP response is -31.

When this problem occurs, the Windows Server 2003-based computer may be unable to use the time server that has the best precision.



CAUSE
This problem occurs because the Windows Time service in Windows Server 2003 supports only precision values from -30 through -3. If the Windows Time service receives an NTP response whose precision value is outside this range, the service discards the response.



Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
To apply this hotfix, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003

Restart requirement
You must restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003 with Service Pack 1, Itanium-based versions


WORKAROUND
To work around this problem, use a time server whose precision value is in the range from -30 through -3.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



Steps to reproduce this problem
 Set up a Windows Server 2003-based computer in a workgroup. Connect the computer directly to the Internet. Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry subkey:

 In the details pane, right-click the NtpServer registry entry, and then click Modify.</li> In the Value data box, type ntp.tt.se,0x1, and then click OK.</li> Right-click the Type registry entry, and then click Modify.</li> In the Value data box, type NTP, and then click OK.</li> Exit Registry Editor.</li> Restart the Windows Time service. To do this, you can run the following command at a command prompt:

net stop W32Time && net start W32Time

Note If a synchronization operation does not start when you run this command, run the following command at a command prompt:

w32tm /resync

</li></ol>

After you enable debug logging of the Windows Time service, information that resembles the following will appear in the debug log:

- TimeProvCommand([NtpClient], TPC_TimeJumped) called.

...

- | Poll Interval: 6 - 64s; Precision: -31 - -0.465661ns per tick

...

- Rejecting packet w/ bad precision

- Ignoring garbage packet.

For more information about how to enable debug logging of the Windows Time service, click the following article number to view the article in the Microsoft Knowledge Base:

816043 How to turn on debug logging in the Windows Time Service

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684Description of the standard terminology that is used to describe Microsoft software updates

Additional query words: w32time

Keywords: kbbug kbfix kbqfe kbpubtypekc kbexpertiseinter kbhotfixserver kbwinserv2003postsp2fix KB940742

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.