Kent West said on Tue, Feb 25, 2003 at 03:21:21PM -0600: > This is what my Windows admin says: > > >... here's what MS has to say about the time service running on ntp0: > >'The Windows Time Synchronization service (W32Time) is a fully compliant > >implementation of the Simple Network Time Protocol (SNTP) as detailed in > >IETF RFC 1769.' You Windows Admin appears to be correct. > And the result of your suggested test: > > >westk[@westek]:/home/westk> sudo ntpdate -q ntp0.acu.edu > >server 150.252.128.107, stratum 2, offset -67.056698, delay 0.03380 > >25 Feb 15:14:35 ntpdate[11374]: no server suitable for synchronization > >found > > This got me curious, so I went to my WinXP box and tried to synch > against ntp0.acu.edu; it failed also. Apparently you're right about our > ntp server being a client only, or something equally messed up. Time to > go confront my Windows admin. It looks like your Windows NTP server is up and running, but is 67 seconds fast, resulting in it being unsuitable for syncronization. (The offset -67.05 is the key result). Your Windows admin probably needs to fix ntp0's clock before offering time service to the rest of campus. M
Attachment:
pgpG6KdAxSu22.pgp
Description: PGP signature