[EMAIL PROTECTED] wrote: > i have a standalone win2k3 server , i wish to configure against a ntpd > on linux. > I have configured the following regestery key's according to MS > document :
Why? You don't need to mess with those registry settings directly in almost all cases. Set them back to their defaults, and use w32tm alone to configure the Windows Time Service. > I have allso done the following to ensure proper work against a non > windows NTP server : > w32tm /config /manualpeerlist:NTP_server_IP_Address,0x8 > /syncfromflags:MANUAL > net stop w32time > net start w32time > w32tm /resync You should use: w32tm /config <your config info> /update to update the running Windows time configuration w32tm /resync causes Windows Time Service to throw out its frequency correction history, and start fresh (similar to deleting ntp.drift on an ntpd system). This makes it take longer to "settle down" to the correct time... perhaps as much as hours depending on the intrinsic error of your motherboard's clock. > the clock on win2k3 server sync's after this , but i can't get it to be > done automatically. > when i reissue >w32tm /resync command the clock resync's. > How do i configure the sync to be preformed every 15 min's ? > Once configured, the windows time service should maintain +/- 16 ms or so offsets after it figures out how fast/slow your motherboard clock is running. If you don't yet have SP1 on that Windows 2003 server, I suggest installing it, as there are many Windows Time updates included. _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
