Hi, I've got a domain with one DC and other member servers. I found cases that the clock of those servers are not synchronize. Why ? (Doesn't the computers within a domain have the clock synchronize features by default?) If not, how can I make them synchronize periodically? I've been thinking of using "NET TIME" command, but I need to login each servers one by one. Is there any way to issue command on a remote machine ? (i know OS/2 have "NET ADMIN" command so that I can issue a command on a remote server.) Also, I've try rsh and rexec. But I got the error message "rsh: can't establish connection". But i do not want any server to run other service such as rsh service... Any one can help ? thanks

Not sure if there is anything that can help here but look at this site: http://www.boulder.nist.gov/timefreq/service/its.htm I do know it sets my clock at whatever interval I want. It may be some thing there that will help you.

Run the services application in the admin tools folder. (Make sure you are either an administrator or have admin privelages) Select the Windows Time W32Time and make the startup time automatic rather than manual or disabled. I used to run atomic clock and my laptop used to loose about 8 seconds a week before i set this to automatic, it has been acurate for the last 2 weeks since i did this, when checked with the atomic clock application. I expect that that the time is taken from the www everytime i log on and is corrected. HTH Billy

Hi I am aware of this issue as well since I am facing similiar issues myself. As far as my reading goes the w32time service is pain in the back side lol we can try to set the sntp in a domain with no external access but even after doing that it will give errors in the event viewer. I have also found it helps to use w32tm from command line use the help it is a very helpful tool (still trying to use it properly) I think this has something to do with registry values which i am still reading up on & what happens is the time service is always looking for a external source to syncronise time with set by default by M/S( I wonder what happens to domains without internet access) I have a domain & i set up my dc with all primary FSMO roles & the PDC emulator is the right one which should be running the time service but still it is asking for a external source well I will keep u all updated if I find something really worth resolving this issue & if you all find it or have a solution let us know. Thanks

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 Time Protocol (SNTP) time server as authoritative by using the following net time command, where server_list is the server list: net time /setsntp:server_list There are several SNTP time servers run by the U.S. Naval Observatory that are satisfactory for this function, for example: ntp2.usno.navy.mil at 192.5.41.209 tock.usno.navy.mil at 192.5.41.41 After you set the SNTP time server as authoritative, run the following command on a computer other than the domain controller to reset the local computer's time against the authoritative time server: net time /set More information about the net time command is available at a command prompt if you type the following command: net time /? SNTP defaults to using User Datagram Protocol (UDP) port 123. If this port is not open to the Internet, you cannot synchronize your server to Internet SNTP servers. NOTE: Administrators can also configure an internal time server as authoritative by using the net time command. If the administrator directs the command to the operations master, it may be necessary to reboot the server for the changes to take effect. For additional information, see the following Microsoft white paper: The Windows Time Service http://www.microsoft.com/windows2000/docs/wintimeserv.doc