NTP Client synchronization with a Windows 2003/2008

[Jerry]

On Tue, 13 Oct 2009 17:13:16 +0200
Jacques Henry (caramba696 at googlemail.com) replied:

>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?

You might want to check out these two URL's for starters:

http://lists.ntp.isc.org/pipermail/questions/2007-January/012469.html
http://msdn.microsoft.com/en-us/library/ms884917.aspx

-- 
Jerry
gesbbb at yahoo.com

My folks didn't come over on the Mayflower,
but they were there to meet the boat.