From owner-freebsd-questions@FreeBSD.ORG Tue Oct 13 16:03:25 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 B71011065695 for ; Tue, 13 Oct 2009 16:03:25 +0000 (UTC) (envelope-from kraduk@googlemail.com) Received: from mail-gx0-f214.google.com (mail-gx0-f214.google.com [209.85.217.214]) by mx1.freebsd.org (Postfix) with ESMTP id 6EEF48FC18 for ; Tue, 13 Oct 2009 16:03:25 +0000 (UTC) Received: by gxk6 with SMTP id 6so9414837gxk.13 for ; Tue, 13 Oct 2009 09:03:24 -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:cc:content-type; bh=NWnH3hmhPfKJ521yZG9jRBArSRI+sJfP1TbvozlgxF0=; b=cE1xCRgqfd2RJBvPOa/LBF3V9WLNItuLxPGywXKdSbuDt3J0JQraMdgLAb3q6aaxEw mFzUqW+7cVMGOehmu6FzCt3p97oLt17tnxsp3TiIAMlU1qDUzn2X3+5HrhUoyO+eSynq Bj2GegTTOoxNlPvJqT+S+CVZDUrXP9HCb1t0Y= 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 :cc:content-type; b=ZvoW/a6cYBygjjSohE9Va5Hfkob+OerxPuSvPDtFSueH3Tz7/exLHiM+pbqNshREZ+ AYfXm4rOS8OiUEFJf/Tr6gKR791B8S1Zi/npL8d2gPSLgk0hxJpI3yNW046ktGe4EdDQ dXVdQfnnGjQnj4xyy77+FKoGxkW6eBGUUD8hQ= MIME-Version: 1.0 Received: by 10.239.190.20 with SMTP id v20mr467561hbh.208.1255449802606; Tue, 13 Oct 2009 09:03:22 -0700 (PDT) In-Reply-To: <2345d18f0910130854l363f157eob42e3253c7dad202@mail.gmail.com> References: <2345d18f0910130813j6a2bbde0sec59647f44d43585@mail.gmail.com> <2345d18f0910130854l363f157eob42e3253c7dad202@mail.gmail.com> Date: Tue, 13 Oct 2009 17:03:22 +0100 Message-ID: From: krad To: Jacques Henry Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-questions@freebsd.org 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: Tue, 13 Oct 2009 16:03:25 -0000 2009/10/13 Jacques Henry > Hello, > > I am using a System based on FreeBSD 6.3. > On this System an automatically generated ntpd.conf file is generated in > order to synchronize the System clock with a NTP Server. I want to use a > Windows 2003 or 2008 Server to act as the NTP Server. On the Windows System > the NTP Server (Windows Time Service) is *correctly* running. The thing is > that even if there are NTP traffic between the client and the Server (NTP > Client and Server IP packet), My FreeBSD is not synchronizing at all: > > freebsd-client>ntpq -p 127.0.0.1 > remote refid st t when poll reach delay offset > jitter > ======================================================= > NTP_server 192.168.10.6 2 u 103 1024 1 1.037 -587367 > 0.002 > > > As you can see the offset is huge and never decreases as in a normal way... > > My ntpd.conf file looks like: > ----------- > # File is automatically generated > # Do not edit > tinker panic 1 > tinker step 1 > > # ntp servers list > server 172.30.1.5 > > # files informations > driftfile /etc/ntp.drift > > # restriction informations > restrict default ignore # do not allow request by default > restrict 127.0.0.1 # allow localhost for debugging > restrict 172.30.1.5 nomodify > ------------ > > my ntp.drift file > ------------ > -101.101 > ------------ > > I know that maybe the Microsoft NTP/SNTP implementation is not > RFC-compliant, but is there a way to configure my NTP client in a more > "compatible" (less strict) way to adjust its time with a Windows Server? > > Thanks > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > ntpd wont resync if the time difference is to big, as it assumes something is wrong as you would have set the system clock roughly correct. To fix stop ntpd, then do an ntpdate against the server. This should set the time. Now run ntpd again also set the following variables to a server of your choosing to make sure ntpdate is run 1st on boot $ grep ntp /etc/rc.conf* /etc/rc.conf:ntpdate_flags="uk.pool.ntp.org" /etc/rc.conf:ntpdate_enable="YES" /etc/rc.conf:ntpd_enable="YES"