If you have this problem with only one client then my guess would be that
the problem is the client itself.
You could also try other software time service solutions. I hear that this
one is pretty good...
http://www.greyware.com/software/domaintime/index.asp
--
Mike
Microsoft MVP - Windows Security
"Senthil" <(E-Mail Removed)> wrote in message
news:134772CF-EF21-401F-90A4-(E-Mail Removed)...
> we have a domain hierarchy time synchronization model with the
> clients(W2K3)
> synchronizing time from its domain controller(W2K) and the domain
> controller
> synchronizing time with it DC etc., The issue we are having is that one of
> the two client machines, synchronizing from the same DC goes ahead by a
> minute. This is not acceptable in our environment. Has anyone seen this
> behaviour before ? Is synchronisation within millisecond accuracy posible
> in
> a windows windows environment ? We are considering a manually configured
> synchronization architecture instead of a domain hierarchy based
> synchronization model ? Any thoughts on this (other than the kerebros
> authentication problem that might occur across domains)?
>
> Any suggestions of a hardware based solution (atomic clock/ GPS etc.,)?
>
> -Senthil
Similar Threads
Linear Mode
