Danny Mayer wrote: > Martin Burnicki wrote: >> Evandro, >> >> Evandro Menezes wrote: >>> On Feb 27, 7:06 am, Ryan Malayter <[EMAIL PROTECTED]> wrote: >>>> This is not true. Windows time service uses UDP/123, just like every >>>> other NTP or SNTP implmentation. All of Microsoft's documentation that >>>> I have read (and I think I have read everything concerning w32time) >>>> agrees on that point. >>> That's true. But W32TIME also registers the time service to the >>> domain or AD hierarchy, allowing the workstations to synchronize with >>> it. >> That's what I meant in one of my earlier posts. >> >>> But when the workstations contact the DC, I think that NTP will >>> reply instead. >> If that setup really works then it's indeed a good workaround for using ntpd >> on the PDC. >> >> Unfortunately I've currently no W2k3 domain set up for testing ... >> > > I do. My main machine at home is a domain controller running Active > Directory. I needed this for some Kerberos work that I was doing. I also > run BIND 9.5.0 on it rather than Microsoft's DNS. > > I have search for information in it but I don't see anything specific > and it didn't seem to add any records to the DNS when I ran w32time on it. > > Danny
Check out this PDF document: http://download.microsoft.com/download/9/5/E/95EF66AF-9026-4BB0-A41D-A4F81802D92C/%5BMS-W32T%5D.pdf which seems to indicate that it uses RPC to get its list of time servers. Danny _______________________________________________ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
