windows time

[angryblack]

I am having a problem with some of our windows 2000
clients not keeping prpoer time with the dc. Some of
them either fall back in time or are keeping the correct
time. The dc's are seup to get the time info from our
edge rougter which get's the time from the mil clock.
The one thing almost all of the workstations have in
common even those that are keeping time correct is they
do not have a time server setup if you do a NET
TIME /QUERYSNTP it says no time server. Can anyone tell
me how might this be caused and how to change it on a
mass level.

 

[Robert Cohen]

What we do is have a logon script (a batch file) that is run at logon. In
it I have:

net time /domain:bbh /set /y

the bbh is the domain name. It thus adjusts the workstation computers to
the server's clock at each logon.

 

[SaltPeter]

The PDC emulator is the time authority on a W2K domain. only this DC should
be synchronizing via set sntp with the router. UDP port 123 is employed for
time sync, your router might be blocking this port. Switch the time sync to
tcp if that's the case.

Note that clients should synchronize with their login DC, the DC in turn
syncs with the FSMO PDC emulator.

Registry Entries for the W32Time Service
http://support.microsoft.com/?kbid=223184

How to Configure an Authoritative Time Server in Windows 2000
http://support.microsoft.com:80/support/kb/articles/q216/7/34.asp

Windows Time Synchronization Service
http://www.winnetmag.com/Articles/Index.cfm?ArticleID=8383