Clock settings

[Ely]

The clock settings on all my Win2000 clients are off by 20
minutes. I've tried changing the settings on the Domain
Controller to the correct time. Shorty after no one can
logg onto the domain because it says the system time is
not the same as the domain controller. Does anyone know
how to resolve this problem?

Thanks ,

ELy

 

[Gerry Voras]

With an Active Directory domain controller using Kerberos, the clients and
the DC have to be within 5 minutes of each other; else, your clients won't
be able to log in.

The 1st thing to do is set all the PC's (sever and clients) to whith 5
minutes of each other. Once Kerberos is working again, with all the clients
running and connected to the network (you shouldn't need to have them logged
in, but from your experience it may be neccesary to do so, and from a domian
admin's account at that) reset the domain controller(s)'s clock(s) by
syncronizing with an atomic clock. There are lots of NTP clients out
there -- I personally use SolidSync. Check www.tucows.com for a wide
selection.

Ideally, within a few minutes, the domain controller(s) should reset all the
clients' clocks.If not, check your AD policy to ensure that clock access is
available from admin and system accounts (but probably not from user
accounts).

If you aren't using Active Directory, include in your login script the
command NET TIME /Set /y .