<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Configuring the Time Service: NtpServer and SpecialPollInterval</title><link>http://blogs.msdn.com/w32time/archive/2008/02/26/configuring-the-time-service-ntpserver-and-specialpollinterval.aspx</link><description>One of the most talked about configuration options for W32Time has to be the list of time sources that W32Time connects to for synchronization. It is important to note that W32Time will only actively synchronize with one time source at a time, even though</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Configuring the Time Service: NtpServer and SpecialPollInterval</title><link>http://blogs.msdn.com/w32time/archive/2008/02/26/configuring-the-time-service-ntpserver-and-specialpollinterval.aspx#8324429</link><pubDate>Wed, 19 Mar 2008 05:07:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8324429</guid><dc:creator>Frank</dc:creator><description>&lt;p&gt;Hi, just wanted to say this is an excellent article. &amp;nbsp;This finally have cleared up one of my confusions about setting up NTP, namely: Why does MS tell me I have to add ,0x1 to the end of a DNS name? &amp;nbsp;&lt;a rel="nofollow" target="_new" href="http://support.microsoft.com/kb/816042"&gt;http://support.microsoft.com/kb/816042&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Reading that KB article again, it's really perfectly clear the way they state it. &amp;nbsp;For some reason though I always mis-interpreted the meaning until now. &amp;nbsp;I thought the ,0x1 was somehow telling Windows that it's a DNS name, rather than an IP address. &amp;nbsp;(Obviously that would be dumb.)&lt;/p&gt;
&lt;p&gt;Finally makes sense now though. &amp;nbsp;Thanks!&lt;/p&gt;</description></item><item><title>re: Configuring the Time Service: NtpServer and SpecialPollInterval</title><link>http://blogs.msdn.com/w32time/archive/2008/02/26/configuring-the-time-service-ntpserver-and-specialpollinterval.aspx#8324438</link><pubDate>Wed, 19 Mar 2008 05:15:07 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8324438</guid><dc:creator>Ryan Sizemore</dc:creator><description>&lt;p&gt;Glad to hear you like it. If you can think of any other topics that have you puzzled regarding w32time, let me know and I'll try to add some clarification.&lt;/p&gt;
</description></item><item><title>re: Configuring the Time Service: NtpServer and SpecialPollInterval</title><link>http://blogs.msdn.com/w32time/archive/2008/02/26/configuring-the-time-service-ntpserver-and-specialpollinterval.aspx#8328212</link><pubDate>Fri, 21 Mar 2008 04:11:48 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8328212</guid><dc:creator>Frank</dc:creator><description>&lt;p&gt;Actually, now that you mention it, why does the article recommend using 0x1? &amp;nbsp;Is there something wrong with letting NTP decide the interval on its own?&lt;/p&gt;</description></item><item><title>re: Configuring the Time Service: NtpServer and SpecialPollInterval</title><link>http://blogs.msdn.com/w32time/archive/2008/02/26/configuring-the-time-service-ntpserver-and-specialpollinterval.aspx#8328562</link><pubDate>Fri, 21 Mar 2008 08:39:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8328562</guid><dc:creator>Ryan Sizemore</dc:creator><description>&lt;p&gt;Nope, nothing wrong with that at all. Most domain admins prefer to have the PDC (or root time source) sync at a regular interval, so this post mirrors those requests.&lt;/p&gt;
</description></item><item><title>re: Configuring the Time Service: NtpServer and SpecialPollInterval</title><link>http://blogs.msdn.com/w32time/archive/2008/02/26/configuring-the-time-service-ntpserver-and-specialpollinterval.aspx#8575932</link><pubDate>Thu, 05 Jun 2008 21:14:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8575932</guid><dc:creator>brorymes</dc:creator><description>&lt;p&gt;Just checking (possible typo?):&lt;/p&gt;
&lt;p&gt;In both examples, time.windows.com is followed by 0x01, although you indicate that both the 0x01 and 0x08 flags apply (i.e. SpecialInterval + Client). &lt;/p&gt;
&lt;p&gt;Shouldn't time.windows.com be followed by 0x09 in both examples, since (0x01 OR 0x08) = 0x09?&lt;/p&gt;
</description></item><item><title>re: Configuring the Time Service: NtpServer and SpecialPollInterval</title><link>http://blogs.msdn.com/w32time/archive/2008/02/26/configuring-the-time-service-ntpserver-and-specialpollinterval.aspx#8991332</link><pubDate>Wed, 08 Oct 2008 16:43:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8991332</guid><dc:creator>Gary</dc:creator><description>&lt;P&gt;Ryan, &lt;/P&gt;
&lt;P&gt;Just had a time problem that caused me to do some research on W32Time. We have two time sources defined but the active one had a problem which caused a change of time by 365 days. The question was can W32Time be configured to sample two times sources and compare them, if I'm reading correctly then this is not possible.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description></item><item><title>re: Configuring the Time Service: NtpServer and SpecialPollInterval</title><link>http://blogs.msdn.com/w32time/archive/2008/02/26/configuring-the-time-service-ntpserver-and-specialpollinterval.aspx#8991599</link><pubDate>Wed, 08 Oct 2008 19:14:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8991599</guid><dc:creator>Ryan Sizemore</dc:creator><description>&lt;p&gt;Gary:&lt;/p&gt;
&lt;p&gt;It would be best to ask these questions on the forums, but nonetheless...&lt;/p&gt;
&lt;p&gt;If a feature like that existed, how would we know which one was the correct one? The correct way to solve this is to impose a set of limits on the phase correction. See the article above about Max*PhaseCorrection. This will limit the size of the time jump that w32time can make, thus preventing your 365 day jumps.&lt;/p&gt;
&lt;p&gt;In Windows Server 2008, we imposed a new set of default limits of 48 hours to prevent this type of problem. You should consider setting those same limits in your environment.&lt;/p&gt;
&lt;p&gt;Ryan&lt;/p&gt;
</description></item><item><title>re: Configuring the Time Service: NtpServer and SpecialPollInterval</title><link>http://blogs.msdn.com/w32time/archive/2008/02/26/configuring-the-time-service-ntpserver-and-specialpollinterval.aspx#9212063</link><pubDate>Sun, 14 Dec 2008 01:34:12 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9212063</guid><dc:creator>Gus</dc:creator><description>&lt;p&gt;Do I need special software for my MS web server 2003 to synchronize my routers time. I am trying to use the ntp services on my cisco devices to get the time from my web server using only W32time services. What a drag!!!&lt;/p&gt;</description></item><item><title>re: Configuring the Time Service: NtpServer and SpecialPollInterval</title><link>http://blogs.msdn.com/w32time/archive/2008/02/26/configuring-the-time-service-ntpserver-and-specialpollinterval.aspx#9212294</link><pubDate>Sun, 14 Dec 2008 03:32:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9212294</guid><dc:creator>Ryan Sizemore</dc:creator><description>&lt;p&gt;No, you don't need special software. You need to enable the NtpServer, which will allow your cisco device to sync with the web server. Take a look at the article titled &amp;quot;Configuring a Standalone NtpServer&amp;quot;. It should cover everything you need.&lt;/p&gt;
&lt;p&gt;Ryan&lt;/p&gt;
</description></item><item><title>re: Configuring the Time Service: NtpServer and SpecialPollInterval</title><link>http://blogs.msdn.com/w32time/archive/2008/02/26/configuring-the-time-service-ntpserver-and-specialpollinterval.aspx#9909071</link><pubDate>Mon, 19 Oct 2009 13:52:51 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9909071</guid><dc:creator>Donno Cole</dc:creator><description>&lt;p&gt;I find that when using an IP address for the time server, the 0x01 switch is not being applied properly. &amp;nbsp;The IP address fails to resolve and no time packets are received from the server. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Is there a trick to get it to work with an IP address?&lt;/p&gt;
&lt;p&gt;Thank you!&lt;/p&gt;</description></item><item><title>re: Configuring the Time Service: NtpServer and SpecialPollInterval</title><link>http://blogs.msdn.com/w32time/archive/2008/02/26/configuring-the-time-service-ntpserver-and-specialpollinterval.aspx#9909129</link><pubDate>Mon, 19 Oct 2009 15:34:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9909129</guid><dc:creator>Ryan Sizemore</dc:creator><description>&lt;p&gt;Hi Donno,&lt;/p&gt;
&lt;p&gt;Using an IP address should be no different than using a DNS name. For example, &amp;quot;123.234.12.23,0x01&amp;quot; should be all that you need.&lt;/p&gt;
</description></item></channel></rss>