Discussion Locked

Network Time Synch

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Is there a way, out of the box, to configure Win2k server to synch time on network workstations on login? Similar to the way that Novell clients are synched when they log into a Netware server.

9 replies

by natebroomfield

Windows 2000 uses the w32time service to do this. You can find info in the following article on Microsoft's site. Q216734

by jimmy

I am using w32time at the server to synch with the Naval SNTP server, but I did not mention (sorry for the oversight) that I am working with win9x clients, not a fully win2k environment. Only a Win2k server. Thanks for the input though.

by joseph moore

There are a lot of ways to set up synching up the PC clocks on workstations, and they all seem to have the same security concern: by default, a normal user cannot change their own system time. This makes automating time syncs difficult.
So, here is one method I set up a sister company with.
I built a global group called TimeSync, and gave this group the permission to Change the System Time.
Next, I added every user into the global group.

Then, in every logon script used by the users, Iput the following line in:
NET TIME \\servername /set /y

servername is the name of the Server that is being used as the master clock.
Now, this sister company is NOT using the w32time service on the Server. Instead, they are using a downloaded time sync program that they scheduled to run once a week.
I guess it really doesn't matter how the main server gets its own clock synchronized. If you want an "out of the box" solution, then set up your Win2k server with the TechNet article info (configuring a SNTP server), then make the global group, add the users to it, and add the Net Time line to their logon scripts.
That will work.

Just remember that this gives the users the ability to change their system clocks. IF you run some type of logon/logoff tracking software, then users "could" get into trouble. A wonderful security concern to keep in mind!

Hope this helps.

by jimmy

worked like a champ... I had forgot to use the /y and the users were getting asked for confirmation every boot. Thanks

by ebob

Yes, of course. Sounds like you've already got at least one 'server' (W2K) running a synch with an external source. Presumably, it can run the time server service.

Then you need to install a "service" on the other boxes to synch with the W2K box.INHO, avoid the "applications" that run only when a user logs in. I believe they are not as effective. The "service" approach runs when the PC starts up.

Where to get a synch client? Try:
http://www.eecis.udel.edu/~ntp/

which includes all sorts of great info.

by curlergirl

If you're running all Win9x clients, then you don't have any security problems. Since your server is already syncing with an SNTP server, all you need to do is add the following line to your login scripts:

net time \\[servername] /SET /y

Thiswill work for any Win9x workstations, and any WinNT workstations where the users have the permissions to change their local workstation's time settings. Hope this helps!

This discussion is closed to new replies.