Back to W32Time. According to http://support.microsoft.com/kb/939322:
The KB article goes on to suggest that you might want to use a 3rd party client instead of W32Time. (Something like http://www.timesynctool.com/ for example - don't forget to disable the Windows Time Service, though, if you use a 3rd party tool).The W32Time service is not a full-featured NTP solution that meets time-sensitive application needs. The W32Time service is primarily designed to do the following:
•Make the Kerberos version 5 authentication protocol work.
•Provide loose sync time for client computers.
The W32Time service cannot reliably maintain sync time to the range of 1 to 2 seconds. Such tolerances are outside the design specification of the W32Time service.”
This Technet blog might also be helpful, especially the comments:
http://blogs.technet.com/b/askds/archiv ... ments.aspx