tag:blogger.com,1999:blog-28293948.post1193273320801707993..comments2008-07-08T15:14:18.603-05:00RPMnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-28293948.post-27287393774968086082008-07-08T15:14:18.603-05:002008-07-08T15:14:18.603-05:00By setting Windows Time Service to create client-mode NTP associations (basically put ",0x8" after the ntp server name in your configuration), Windows will adjust the polling interval automatically from 64 to 1024 seconds based on the needs of the clock filter. This is the same behavior as the reference ntpd.<BR/><BR/>Polling more frequently does not necessarily give you "better" time - longer poll intervals make the clock more stable. The reasons are complex, but there is a short synopsis <A HREF="http://www.cis.udel.edu/~mills/ntp/html/ntpd.html#poll" REL="nofollow">here</A>.<BR/><BR/>Finally, using a short poll interval (<60s) against other people's servers is considered rude, and some NTP implementations will simply start dropping your requests or end you a Kiss-of-Death packet if you poll too frequently.RPMhttp://www.blogger.com/profile/12675510409950425811noreply@blogger.comtag:blogger.com,1999:blog-28293948.post-68454852437317746912008-07-08T13:46:35.984-05:002008-07-08T13:46:35.984-05:00So, you enforce a polling interval on your DCs (and PDC emulator)? I also have a few clients that need to have very accurate time. I'm going to test having them sync directly to a level 3 internet ntp.matthttp://www.blogger.com/profile/16346388073511323423noreply@blogger.com