up vote 0 down vote favorite
share [g+] share [fb]

I find the message hilarious and at first I thought it was some joke from an over-active programmer of the MS team, or a hoax. However, the message appears again and again, a couple of times a day:

NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on ''. NtpClient will try again in 3473457 minutes and double the reattempt interval thereafter. The error was: The requested name is valid, but no data of the requested type was found. (0x80072AFC)

Source: Time Service
Event ID: 134
Level: Warning

I suspect that my time servers are not configured correctly. Is that true and how can I fix it? But why such an odd message?

link|improve this question
87% accept rate
feedback

1 Answer

up vote 1 down vote

Yes your Time Server is mis-configured. Either it has no upstream server to synchronize with or you block the port in your firewall (Port 123 UDP).

Why such a big number? The solution is already presented in the error message: "and double the reattempt interval thereafter." So it started with a few seconds and then doubled and doubled and doubled...

That's all described in the documentation about Microsoft Time Service.

link|improve this answer
Someone likely set ResolvePeerBackoffMaxTimes to a very high value. – David Schwartz Nov 21 '11 at 20:48
The "then doubled and doubled and..."-thought occurred to me too, except that: the frequency of this message is more than daily, the number is not a double of an integer, the last message should have been 1736728.5 minutes ago, which is 3.3 years, which is long before I installed my system...... it just doesn't make sense. – Abel Nov 22 '11 at 8:16
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.