Date: Tue, 13 Oct 2009 17:03:22 +0100 From: krad <kraduk@googlemail.com> To: Jacques Henry <caramba696@googlemail.com> Cc: freebsd-questions@freebsd.org Subject: Re: NTP Client synchronization with a Windows 2003/2008 Message-ID: <d36406630910130903g1fe317f7s89f9f06180ff6c90@mail.gmail.com> In-Reply-To: <2345d18f0910130854l363f157eob42e3253c7dad202@mail.gmail.com> References: <2345d18f0910130813j6a2bbde0sec59647f44d43585@mail.gmail.com> <2345d18f0910130854l363f157eob42e3253c7dad202@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/10/13 Jacques Henry <caramba696@googlemail.com> > 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d36406630910130903g1fe317f7s89f9f06180ff6c90>