tom

Hi!

I checked the W32tm hives at both DC's.

The PDC -emulator (dc01.my.dom) has the following entries under the
Parameters subkey (the time source is a NTP server in our network):
Value Name Value Type Value Data
-------------------------------------------------
ServiceMain REG_SZ SvchostEntry_W32Time
ServiceDll REG_EXPAND_SZ C:\WINDOWS\system32\w32time.dll
NtpServer REG_SZ 10.10.21.200
Type REG_SZ NTP

The second DC has the following entries under the Parameters subkey:
Value Name Value Type Value Data
-------------------------------------------------
ServiceMain REG_SZ SvchostEntry_W32Time
ServiceDll REG_EXPAND_SZ C:\WINDOWS\system32\w32time.dll
NtpServer REG_SZ dc01.my.dom
Type REG_SZ NT5DS

What pisses me of the most, is that a excellent working service in w2k has
in w2k3 been modified to a nightmare... Sorry, but I feel a little
frustrated at the moment.

- Tomppa -

flying brian

Why don't you try sync your DC with an external time source then when you
have that working, try sync other DC's from that to test.

tom

That's one option that I already have considered. But I wouldn't like to do
that on every DC, totally there will be about 20 DC's on different
locations. That's always one step more to do when setting up a new DC. And
since the hierarchy should automatically configure the time sync, I really
don't know....

Of course, if I can't get the w2k3 time service to work as it should, then
I'll have to make the configuration manually and sync every DC with our old
NTP server.

- Tomppa -