System time changes

I actually set my time to poll itself. By entering my servers address in the time set command, the primary server actually polls its own clock and stops drifting, then I set the other servers to poll the primarl.

NOTE: you must set the exact time right before telling it to poll itself of course.

I'll suggest you get the Microsoft Time Service paper. Tells you everything you need to know about setting up Windows Time Service on a Network. Downloadable MS Word Document. here's a link http://www.microsoft.com/windows2000/techinfo/howitworks/security/wintimeserv.asp

copy the link right to left so you don't put any spaces in it. remove any spaces you find or the link won't work. If the link doesn't work do a internet search for "Windows Time Service". Plenty of hits from Microsoft's Support site.

Well you should already have your workstations polling the time server. If your primary server is holding correct time, so will your workstations.

Now I am sure that in a Windows server environment, this is FAR more complicated than it needs to be and will probably require a few patches. I would also recommend taking the Microsoft advice noted above.

This is just a simple solution I have used many times, in a Netwaer environment of course. I just assumed the solution would be similar because I learned the Novell fix from a Linux server issue I had one day.

If only MS could keep up.

1) Go to one of the affected clients and open a command prompt.
2) Type NET TIME
You should see the current time at your DC.
3) Type NET TIME /SET
4) Enjoy.

You can set synchronization with an external time source by entering:
1) Type: NET TIME /SETSNTP:
for example: NET TIME /SETSNTP:tick.uh.edu
2) Type: NET TIME /QUERYSNTP to verify the setting.
3) Enjoy.

sheesh. what O/S are the 20 computers running? and did you actually read the Windows Time Service manual?

note: by default ALL windows 2000 or later client destop computers nomnate their authenticating DC as their inbound time partner.
By default all member servers follow the same relationship as above
By default PDC masters follow the hierarchy of domains so that the PDC at the roor of the beomes authoritative for the organization. This PDC is configured to receive time from an external time source such as NIDS.

Windows 9x computers DO NOT support NTP and will NOT automatically sync their time with an authoritative domain time service. So if your 20 or so computers that are on your network and are off 10 minutes are W9X computers, you'll have to write a script to update their time to network time.