Date: Wed, 14 Oct 2009 18:04:41 +0200 From: Jacques Henry <caramba696@googlemail.com> To: freebsd-questions@freebsd.org Subject: Re: NTP Client synchronization with a Windows 2003/2008 Message-ID: <2345d18f0910140904v3e2e9f37hbaabc05cb561a19d@mail.gmail.com> In-Reply-To: <200910140902.27825.j.mckeown@ru.ac.za> References: <2345d18f0910130813j6a2bbde0sec59647f44d43585@mail.gmail.com> <2345d18f0910130921g17b8d9fdy8fdb99bd5a0e8cf4@mail.gmail.com> <4AD4AE89.6010802@radel.com> <200910140902.27825.j.mckeown@ru.ac.za>
next in thread | previous in thread | raw e-mail | index | archive | help
> > The 19 minutes between when I sent my suggestions and you responded is > > hardly enough time to see if ntpd was slewing the time. Slewing 587 > > seconds takes days. > The thing is that ntpd is not slewing the time at all, even after several hours!! > > Are you sure that -x in there, telling ntpd to not step unless the > > offset is over 600 sec, doesn't override what you're trying to do with > > the -q? How about you try simple: > > > > ntpdate the_windows_server > > > > and see what that does? After that look in /var/log/messages. > I don't have that command on my system... > > Alternatively, from the commandline try > > ntpd -g -q -c /etc/ntp.conf > > The -g flag allows ntpd to set the clock once regardless of the offset and > the -q causes it to quit after setting the time. > > I tried this command without success... I can see the NTP packets (client and server) but the clock is never set.... with the debugging option enabled (-D 3), at the end I get: ... ... poll_update: at 15 172.30.1.5 flags 0201 poll 6 burst 1 last 1 next 17 read_network_packet: fd=22 length 48 from ac1e0105 172.30.1.5 receive: at 15 172.30.1.250<-172.30.1.5 flags 19 restrict 080 receive: at 15 172.30.1.250<-172.30.1.5 mode 4 code 1 auth 0 packet: flash header 0040 addto_syslog: no reply; clock not set
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2345d18f0910140904v3e2e9f37hbaabc05cb561a19d>