Windows Forum

Ask something
Discussion Locked

w32time event

0 helpful
4 replies

by deven

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I get this event almost every hour on my webserver, which is a stand alone windows 2000 server.

Event Type: Warning
Event Source: w32time
Event Category: None
Event ID: 11
Date: 3/11/2003
Time: 2:11:24 AM
User: N/A
Computer: WEBSERVER
Description:
The NTP server didn't respond

I can't assign a seperate time server (like PDC) as this machine is stand alone machine.

How can I use any other time server or in other words on a stand alone windows 2000 server how can I configure time server?

when I use "net time" I get "could not locate a time-server"

Thanks in advance

4 replies

by churdoo

If you don't have one available on your network, you can use a publicly available NTP server. Do a search on public free time servers and find one that's geographically close to you

next enter the command
net time /setsntp:someNtpServer

Thiswill cause your webserver to query that timeserver, and will sync its time accordingly from that server
--c

by mustafa.ibrahim

Deven, try the following:

http://support.microsoft.com/?kbid=216734

How to Configure an Authoritative Time Server in Windows 2000
The information in this article applies to:
Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Professional
Microsoft Windows 2000 Datacenter Server

This article was previously published under Q216734
For a Microsoft Windows XP version of this article, see 314054.

SUMMARY
This article describes how to configure an authoritative time server in Windows.
MORE INFORMATION
Windows includes the W32Time Time service tool that is required by the Kerberos authentication protocol. The purpose of the Time service is to ensure that all computers that are running Windows 2000 or later in an organization use a common time. The Time service uses a hierarchical relationship that controls authority and does not permit loops to ensure appropriate common time usage.

Windows-based computers use the following hierarchy by default:
All client desktop computers nominate the authenticating domain controller as their in-bound time partner.
All member servers follow the same process as client desktop computers.
Domain controllers may nominate the primary domain controller (PDC) operations master as their in-bound time partner but may use a parent domain controller based on stratum numbering.
All PDC operations masters follow the hierarchy of domains in the selection of their in-bound time partner.
Following this hierarchy, the PDC operations master at the root of the forest becomes authoritative for the organization, and you should configure the PDC operations master to gather the time from an external source. This is logged in the System event log on the computer as event ID 62. Administrators can configure the Time service on the PDC operations master at the root of the forest to recognize an external Simple Network

This discussion is closed to new replies.