George, As I said in my message to you, Windows shows dispersion 10s, which is ten times the ntpd default of 1 s. You will need to either modify Windows code, ntpd code or tinker the maxdist to something above 10 s.
Windows shows a precision of 6, which will cause the ntpd server to bounce around. If you exect to use multiple servers in the interest of robustness, you will have to tinker the mindist to something well above 16 ms. You would be much better advised to use SNTP from a shell script. Dave george_joby wrote: > Hi > > I am trying to configure NTP server in Windows 2003 server and client > as Redhat Linux AS 4. But if I use W32time of Windows my client will > never synchronise with the server. But if I use the third part software > in Windows server 2003 (http://www.meinberg.de/english/sw/ntp.htm) my > Linux client will synchronise with the server. I heard that W32time is > based on SNTP but read that SNTP and NTP can be used interchangebly. > (http://www.microsoft.com/technet/solutionaccelerators/cits/interopmigration/unix/usecdirw/21wsdsu.mspx) > > > But I am not able to syncronize with the server at all. > > My configuration is just between two system in a local lan using cross > cable. Server is configured to use internal clock. > > My client want to try with w32time. Also I saw this ... > > http://ntp.isc.org/bin/view/Support/TroubleshootingNTP#Section_9.10. > > Can any body help me in this. Will w32time work with linux ? > _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
