Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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


View products that this article applies to.

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.

↑ Back to the top


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.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

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 2, x86-based versions
File nameFile versionFile sizeDateTimePlatform
W32time.dll5.2.3790.4124227,32826-Jul-200712:44x86
Windows Server 2003 with Service Pack 2, x64-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
W32time.dll5.2.3790.4124407,55225-Jul-200722:08x64SP2Not applicable
Ww32time.dll5.2.3790.4124227,32825-Jul-200722:08x86SP2WOW
Windows Server 2003 with Service Pack 2, Itanium-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
W32time.dll5.2.3790.4124578,56025-Jul-200722:13IA-64SP2Not applicable
Ww32time.dll5.2.3790.4124227,32825-Jul-200722:13x86SP2WOW
Windows Server 2003 with Service Pack 1, x86-based versions
File nameFile versionFile sizeDateTimePlatform
W32time.dll5.2.3790.2982227,32826-Jul-200712:21x86
Windows Server 2003, x64-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
W32time.dll5.2.3790.2982407,55225-Jul-200722:03x64SP1Not applicable
Ww32time.dll5.2.3790.2982227,32825-Jul-200722:03x86SP1WOW
Windows Server 2003 with Service Pack 1, Itanium-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
W32time.dll5.2.3790.2982578,56025-Jul-200722:03IA-64SP1Not applicable
Ww32time.dll5.2.3790.2982227,32825-Jul-200722:03x86SP1WOW

↑ Back to the top


Workaround

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

↑ Back to the top


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


More information

Steps to reproduce this problem

  1. Set up a Windows Server 2003-based computer in a workgroup.
  2. Connect the computer directly to the Internet.
  3. Click Start, click Run, type regedit, and then click OK.
  4. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
  5. In the details pane, right-click the NtpServer registry entry, and then click Modify.
  6. In the Value data box, type ntp.tt.se,0x1, and then click OK.
  7. Right-click the Type registry entry, and then click Modify.
  8. In the Value data box, type NTP, and then click OK.
  9. Exit Registry Editor.
  10. 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
After you enable debug logging of the Windows Time service, information that resembles the following will appear in the debug log:
Time - TimeProvCommand([NtpClient], TPC_TimeJumped) called.
...
Time - | Poll Interval: 6 - 64s; Precision: -31 - -0.465661ns per tick
...
Time - Rejecting packet w/ bad precision
Time - 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

↑ Back to the top


Keywords: kbautohotfix, kbexpertiseinter, kbwinserv2003postsp2fix, kbbug, kbfix, kbHotfixServer, kbqfe, KB940742

↑ Back to the top

Article Info
Article ID : 940742
Revision : 2
Created on : 10/8/2011
Published on : 10/8/2011
Exists online : False
Views : 287