From owner-freebsd-questions@FreeBSD.ORG Wed Oct 14 16:04:43 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D758B1065670 for ; Wed, 14 Oct 2009 16:04:43 +0000 (UTC) (envelope-from caramba696@googlemail.com) Received: from mail-yw0-f197.google.com (mail-yw0-f197.google.com [209.85.211.197]) by mx1.freebsd.org (Postfix) with ESMTP id 8C3288FC24 for ; Wed, 14 Oct 2009 16:04:43 +0000 (UTC) Received: by ywh35 with SMTP id 35so36393503ywh.7 for ; Wed, 14 Oct 2009 09:04:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=8VqQbsC2IAMb45jmAtdQZ899LeI6tmQK85WF3LHIb1Q=; b=UU4Ajeoid3ilIFw1uCP/Ej1/fHeENso3uh5dhsJuHyPe4RZTNWZXwPuqGv1CRLHTtm JZ5CssGNzvzA+jj5dO1uzo0ju4nnAftVDed8VdUoafzCfb37VDWyjkaAsGo1q0+XpX3e 5Im/VNz2Oh/nvrPM/flAguRp2h3zVEVRZNlf8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=DQF51lHMh+4ay5G1GMcuc3+BZ51YAH2nsd79EWyeZAYeAZ7TqaAE6dzw5OtT126g8n lvEn92MYidihOekfoJr02SBkAgZRGy479HnrJAlJ8KMVlkjnRQ98ctD0oNKKynchrDZk QLPeV1HlulDDo/bnlaHK52WED3gcj9pUUBn/I= MIME-Version: 1.0 Received: by 10.101.144.30 with SMTP id w30mr7446311ann.188.1255536282383; Wed, 14 Oct 2009 09:04:42 -0700 (PDT) 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> Date: Wed, 14 Oct 2009 18:04:41 +0200 Message-ID: <2345d18f0910140904v3e2e9f37hbaabc05cb561a19d@mail.gmail.com> From: Jacques Henry To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: NTP Client synchronization with a Windows 2003/2008 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2009 16:04:43 -0000 > > 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