Danny Mayer wrote: > Martin Burnicki wrote: >> Though it's normally preferable to run ntpd rather than w32time, there is >> a limitation if you run ntpd on a domain controller: >> The domain members (workstations) will stop detecting the domain >> controller automatically as their primary time source, so you'll have to >> configure the domain controller explicitely as times source on every >> client. > > Really? Why would it do that? Is this documented somewhere?
We have tried it with a small test setup and found that w32time domain members did identify their PDC as time source when w32time was running on the PDC, but not when ntpd was running on the PDC. I have recently received a note from someone who seemed to be very familiar with Active Directory. That person told me whn w32time starts it makes an entry in the LDAP directory which tells the clients at logon that this server is also their time server. I assume if ntpd would do the same thing then domain clients would also detect and accept ntpd running on the PDC. Unfortunately I don't have the original note handy right now, so I'll have to investigate. Martin -- Martin Burnicki Meinberg Funkuhren Bad Pyrmont Germany _______________________________________________ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
