The Windows 2000 and Windows Server 2003 Time service does not work through a proxy with Access Control enabled

View products that this article applies to.

This article was previously published under Q305135

Expand all | Collapse all

SYMPTOMS

Assume that the Windows Time service (W32Time) on a Microsoft Windows Server 2003-based or Microsoft Windows 2000-based computer is set to run behind a proxy server, such as Microsoft Internet Security and Acceleration (ISA) Server 2004, Microsoft ISA Server 2000, Microsoft Proxy Server 2.0, or Microsoft Proxy Server 1.0. In this scenario, the Time service may not be able to connect to the external Network Time Protocol (NTP) Time service.

Back to the top

CAUSE

This issue occurs because the Windows Time service runs under the local system account on the internal server, and the Access Control feature is enabled on the proxy server.

Back to the top

RESOLUTION

To work around this issue, use any of the following methods:

Disable the Access Control feature for the Winsock proxy. The Enable Access Control check box is located on the Permissions tab in the properties of the Winsock Proxy service in Microsoft Internet Information Services (IIS) Manager. To disable the Access Control feature, click to clear the check box.
Set the computer to access the proxy server for its NTP server, and configure the proxy to point to the external Time service.
On Windows 2000 Server Editions, use a batch file with the following commands on the internal computer:
net stop w32time
w32tm -once
net start w32time
Use the Scheduler tool to run the batch file daily.

Note The batch file method is unavailable on Windows Server 2003

Back to the top