Overriding Domain Controller's time setting on a client PC

[Alexander V. Alexeev]

Hi!

Here's my situation. We have a Win 2000 domain at work, with Win 2000 Server
being the DC and clients all on Win 2000 Pro / XP.

The problem is that the DC's system clock is ten minutes behind! I assume it
is not set to sync from an external source. Bothering the admin to change it
is out of the question for now. As a provisional solution is it possible to
override the DC's clock and set my work PC so that it sync's with a time
source on the Internet? Or does a domain member PC always reset back to DC's
time?

Thanks!
Alex A

 

[Lanwench [MVP - Exchange]]

Hi!

Here's my situation. We have a Win 2000 domain at work, with Win 2000
Server being the DC and clients all on Win 2000 Pro / XP.

The problem is that the DC's system clock is ten minutes behind! I
assume it is not set to sync from an external source. Bothering the
admin to change it is out of the question for now. As a provisional
solution is it possible to override the DC's clock and set my work PC
so that it sync's with a time source on the Internet? Or does a
domain member PC always reset back to DC's time?

All DCs and workstations will sync to the first DC set up (PDC emulator) by
default, and you need to leave it that way. If your workstation time doesn't
match the DC's, you will have problems.

If you type

net time <enter>

in a command prompt on your workstation, what do you get?

Why can't you talk to the admin about correcting the time on the DC and
making sure it's syncing with a reliable external time server? This should
be a simple enough task.