[ntp:questions] Solaris doesn't like Active Directory NTP?

ilmdba ilmdba at yahoo.com
Fri Nov 14 07:25:05 UTC 2003


hi i've got a whole slew of unix boxes, linux, solaris, irix, osx,
etc. that i need to point to windows active directory server for time.

my linux clients seem to have no problem binding to the AD servers,
but all my solaris clients don't seem to like it (if i understand this
# properly).  this includes solaris 7, 8 and 9 systems.

ntpq -p on any of the linux systems looks like:

miket deathstar100 /home/miket >ntpq -p
     remote           refid  st t when poll reach delay  offset jitter
======================================================================
+ilm-dc2.lucasdi 172.20.4.18  2 u   50  128  377  0.245  27.802  7.810
*ilm-dc3.lucasdi 172.20.4.18  2 u  125  128  377  0.244 -30.285  9.966
+ilm-dc1.lucasdi 172.20.4.17  2 u  125  128  377  0.248  36.322  6.792
 LOCAL(0)        LOCAL(0)    10 l   35   64  377  0.000   0.000  0.008


ntpq -p on the solaris boxes (all versions) looks similar to:

     remote           refid  st t when poll reach delay  offset  disp
=====================================================================
 LOCAL(0)        LOCAL(0)    10 l   29   64  377   0.00   0.000 10.03
#ilm-dc3.lucasdi 172.20.4.18  2 u  133  256  377   0.34  21.501  1.04
+ilm-dc2.lucasdi 172.20.4.18  2 u  238  256  377   0.35 -24.366  3.37
+ilm-dc1.lucasdi 172.20.4.17  2 u  146  256  377   0.40   4.461  0.72

from the ntpq man page, the # means:

           #    Selected  for   synchronization;   but   distance
                exceeds maximum.

which i've found no explainantion for, but some other posts indicate
that this means it will -not- synchronize time with the server?  is
this correct?

and if so, any ideas why xntpd doesn't like AD?



More information about the questions mailing list