Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 13 Oct 2009 17:13:16 +0200
From:      Jacques Henry <>
Subject:   NTP Client synchronization with a Windows 2003/2008
Message-ID:  <>

Next in thread | Raw E-Mail | Index | Archive | Help

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
     remote           refid      st t when poll reach   delay   offset
 NTP_server     2 u  103 1024    1    1.037  -587367

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

# files informations
driftfile       /etc/ntp.drift

# restriction informations
restrict default ignore  # do not allow request by default
restrict       # allow localhost for debugging
restrict     nomodify

my ntp.drift file

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?


Want to link to this message? Use this URL: <>