Discussion Locked

Synching time on multiple workstations

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
My boss recently asked me to research the ability to standardize the time on all of our win2000 workstations (300+)from our win2000 server. He told me to lookup timesrv.exe and w32time.exe to implement as well as other possibilities. Technet wasnt so forthcoming, I found some info about and how, but nothing substantial. What does everybody else use to control uniform time on all pcs? Any input would greatly be appreciated. Thx

12 replies

by joseph moore

I have a NT4 domain (NT4 PDC and BDCs) with Win2K clients, so I cannot use all of the functionality of the NET TIME command. So, here is how I handle it.
I run a NTP program on my PDC that I downloaded off the Internet (just do a search for "time sync" on download.com to get dozens of programs). This program synchs the clock on my PDC with an atomic clock via Network Time Protocol. I think it runs every 5 minutes.
So, my PDC is accurate. I then run the following line in every logon script:NET TIME \\MYPDC /SET /Y

This command synchs up the clock on the local workstations with my PDC (I put the real machinename of my server in place of MYPDC).

The last piece of the puzzle is to modify user rights. YOu see, in the default setup,normal Domain Users CANNOT change their system clocks; only Domain Admins can do that. So, I added the Domain Users group to the "Change the System Time" advanced user right. This allows the script to work.

In a pure Win2K environment (AD on yourservers), you can do it this way, but I think that Group Policy can also do this.

hope this helps

by jkaras

Sorry everyone about not closing this thread earlier. My job responsibilites have changed keeping me very busy and away from the site. All your suggestions helped me, thx, points for all.

by infoguy

Windows 2000 is supposed to synchronize itself with the server, if the service is turned on. Keeping the time on the server is the only problem. I use ws_ping propack from ipswitch to keep the server time correct. Pretty simple, just create a scheduled task to run the timeserver update occasionally.

Infoguy

by timwalsh

If you are running a Win2K domain, and the Windows Time Service is running on the DC, All Win2K (and WinXP) clients (that are joined to the domain) that have the Windows Time Service running will have their date and time synchronized with the DC.
The next trick is to have the DC synchronize its time with a reliable source (otherwise all the times will be synchronized, but the time could be wrong). You need to be able to access an NTP (Network Time Protocol) server. To get a list of servers offering NTP services, try this URL:

http://www.eecis.udel.edu/~mills/ntp/clock1a.html

As you peruse the list, you will notice that many servers are available for access only through prior arrangement. Therefore you need to search for servers that have true open access.

Next, you need to configure your server to use a specific NTP server for time synchronization.

Use the NET TIME command from a Command Prompt to specify the NTP server you wish to use:

NET TIME /SETSNTP:

by ctmoore1998

Just put the following command in your login script:
NET TIME \\SERVER_NAME /set /y
where server_name is the name of the server or workstation that you want to be the time server (usually your PDC )you can also use the Time Server option in 2000 DHCP just configure with the IP address of the PDC.

This discussion is closed to new replies.