Discussion:
Is anyone seeing a problem with the Windows Time-service in Vista?
(too old to reply)
Whip
2007-04-06 13:18:01 UTC
Permalink
I get this message: " NtpClient was unable to set a manual peer to use as
a time source because of DNS resolution error on 'time.windows.com,0x9'.
NtpClient will try again in 15 minutes and double the reattempt interval
thereafter. The error was: No such host is known. (0x80072AF9) "

These show up in the System Windows logs in the Event viewer. I set up a
filter for the Time-Service entries and see that there have been 242 in the
last 32 days.

The writeup on this also says that it will run once a week. I am seeing it
trying to run everyday. This process has worked 12 out of the last 32 days
since Vista was installed on March 5th. For now, I have stopped it from
starting using MSCONFIG, but wonder if I may have created another problem.
BillD
2007-04-06 13:52:48 UTC
Permalink
Post by Whip
I get this message: " NtpClient was unable to set a manual peer to use as
a time source because of DNS resolution error on 'time.windows.com,0x9'.
NtpClient will try again in 15 minutes and double the reattempt interval
thereafter. The error was: No such host is known. (0x80072AF9) "
These show up in the System Windows logs in the Event viewer.
yes, I have a lot of these errors in event viewer:
- 8 on 30 January
- 8 on 27 March
- 28 from 4 April to 6 April
Whip
2007-04-06 22:54:01 UTC
Permalink
Thanks for letting me know that I am not alone on this issue.
Post by BillD
Post by Whip
I get this message: " NtpClient was unable to set a manual peer to use as
a time source because of DNS resolution error on 'time.windows.com,0x9'.
NtpClient will try again in 15 minutes and double the reattempt interval
thereafter. The error was: No such host is known. (0x80072AF9) "
These show up in the System Windows logs in the Event viewer.
- 8 on 30 January
- 8 on 27 March
- 28 from 4 April to 6 April
Whip
2007-04-09 14:52:03 UTC
Permalink
OK, maybe I have this figured out now.
Right click on time in the taskbar.
Select Adjust Date/Time
Click on Internet Time tab
Select Change Settings
Reply Continue to User Account Control message
Change the Server from time.windows.com, I selected time.a-nist.gov
Update now
OK, OK

Will have to wait a few days to be sure, but this appears to fix the problem.

Thanks to Richard Urban's post of 3/20/2007.
Post by Whip
Thanks for letting me know that I am not alone on this issue.
Post by BillD
Post by Whip
I get this message: " NtpClient was unable to set a manual peer to use as
a time source because of DNS resolution error on 'time.windows.com,0x9'.
NtpClient will try again in 15 minutes and double the reattempt interval
thereafter. The error was: No such host is known. (0x80072AF9) "
These show up in the System Windows logs in the Event viewer.
- 8 on 30 January
- 8 on 27 March
- 28 from 4 April to 6 April
Mike
2007-04-12 01:18:01 UTC
Permalink
Whip, did this work after a few days? I tried it and so far so good. This
has been driving me crazy...hope this sustains. Thanks for the good work.
Post by Whip
OK, maybe I have this figured out now.
Right click on time in the taskbar.
Select Adjust Date/Time
Click on Internet Time tab
Select Change Settings
Reply Continue to User Account Control message
Change the Server from time.windows.com, I selected time.a-nist.gov
Update now
OK, OK
Will have to wait a few days to be sure, but this appears to fix the problem.
Thanks to Richard Urban's post of 3/20/2007.
Post by Whip
Thanks for letting me know that I am not alone on this issue.
Post by BillD
Post by Whip
I get this message: " NtpClient was unable to set a manual peer to use as
a time source because of DNS resolution error on 'time.windows.com,0x9'.
NtpClient will try again in 15 minutes and double the reattempt interval
thereafter. The error was: No such host is known. (0x80072AF9) "
These show up in the System Windows logs in the Event viewer.
- 8 on 30 January
- 8 on 27 March
- 28 from 4 April to 6 April
Whip
2007-04-12 02:44:01 UTC
Permalink
Two days is a pretty short test, but I will tell you what has happened so
far. On the 10th, it did not try to update when I was connected to the
internet. On the 11th, it tried to update when I was not connected and
failed, but as soon as I was connected, it updated without a hitch.
Post by Mike
Whip, did this work after a few days? I tried it and so far so good. This
has been driving me crazy...hope this sustains. Thanks for the good work.
Post by Whip
OK, maybe I have this figured out now.
Right click on time in the taskbar.
Select Adjust Date/Time
Click on Internet Time tab
Select Change Settings
Reply Continue to User Account Control message
Change the Server from time.windows.com, I selected time.a-nist.gov
Update now
OK, OK
Will have to wait a few days to be sure, but this appears to fix the problem.
Thanks to Richard Urban's post of 3/20/2007.
Post by Whip
Thanks for letting me know that I am not alone on this issue.
Post by BillD
Post by Whip
I get this message: " NtpClient was unable to set a manual peer to use as
a time source because of DNS resolution error on 'time.windows.com,0x9'.
NtpClient will try again in 15 minutes and double the reattempt interval
thereafter. The error was: No such host is known. (0x80072AF9) "
These show up in the System Windows logs in the Event viewer.
- 8 on 30 January
- 8 on 27 March
- 28 from 4 April to 6 April
Mike
2007-04-12 02:48:01 UTC
Permalink
Didnt work. I found a new problem in th log that I've tied to the failures.
"Event id 43015, I2c return failed, source R300. If anyone knows what his
is, this is the culprit.
Post by Whip
Two days is a pretty short test, but I will tell you what has happened so
far. On the 10th, it did not try to update when I was connected to the
internet. On the 11th, it tried to update when I was not connected and
failed, but as soon as I was connected, it updated without a hitch.
Post by Mike
Whip, did this work after a few days? I tried it and so far so good. This
has been driving me crazy...hope this sustains. Thanks for the good work.
Post by Whip
OK, maybe I have this figured out now.
Right click on time in the taskbar.
Select Adjust Date/Time
Click on Internet Time tab
Select Change Settings
Reply Continue to User Account Control message
Change the Server from time.windows.com, I selected time.a-nist.gov
Update now
OK, OK
Will have to wait a few days to be sure, but this appears to fix the problem.
Thanks to Richard Urban's post of 3/20/2007.
Post by Whip
Thanks for letting me know that I am not alone on this issue.
Post by BillD
Post by Whip
I get this message: " NtpClient was unable to set a manual peer to use as
a time source because of DNS resolution error on 'time.windows.com,0x9'.
NtpClient will try again in 15 minutes and double the reattempt interval
thereafter. The error was: No such host is known. (0x80072AF9) "
These show up in the System Windows logs in the Event viewer.
- 8 on 30 January
- 8 on 27 March
- 28 from 4 April to 6 April
TDM
2007-04-06 14:57:06 UTC
Permalink
Post by Whip
I get this message: " NtpClient was unable to set a manual peer to use as
a time source because of DNS resolution error on 'time.windows.com,0x9'.
NtpClient will try again in 15 minutes and double the reattempt interval
thereafter. The error was: No such host is known. (0x80072AF9) "
These show up in the System Windows logs in the Event viewer. I set up a
filter for the Time-Service entries and see that there have been 242 in the
last 32 days.
The writeup on this also says that it will run once a week. I am seeing it
trying to run everyday. This process has worked 12 out of the last 32 days
since Vista was installed on March 5th. For now, I have stopped it from
starting using MSCONFIG, but wonder if I may have created another problem.
Shell out to a command prompt and try "nslookup time.windows.com"
If you do not get an IP address back, then your event log is telling you
the truth, you cannot resolve the hostname via DNS. If you do get an
IP back, then something else is busticated.

I dont have Vista in front of me know, but in XP, you set the server
in this registry location :

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters

Look for NtpServer here and try setting it to the IP of time.microsoft.com
which
is currently 207.46.197.32,0x1. Not a good idea to hard code IP's so just do
this
as a test. If it works, try to figure out what is wrong with your DNS
resolution.

Also note that systems in an Active Directory domain will likely have this
value
overriden by a GPO.

TDM
k***@yahoo.com.invalid
2007-04-06 18:52:53 UTC
Permalink
Post by Whip
I get this message: " NtpClient was unable to set a manual peer to use as
a time source because of DNS resolution error on 'time.windows.com,0x9'.
I've seldom used time.windows.com. Can you imagine jamming all of new York thru the same subway entrance at the same time ?
Try any of the 5 nist servers. You'll have fewer problems, and be able to update more than once a week.
I do it hourly.
There are other time servers. But the nist ones do the job just fine.
--
more pix @ http://members.toast.net/cbminfo/index.html
Richard G. Harper
2007-04-06 20:14:40 UTC
Permalink
Dude, time.windows.com is an alias that points to a bank of servers. Just
like microsoft.com, google.com, and the like.
--
Richard G. Harper [MVP Shell/User] ***@gmail.com
* NEW! Catch my blog ... http://msmvps.com/blogs/rgharper/
* PLEASE post all messages and replies in the newsgroups
* The Website - http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


<***@yahoo.com.invalid> wrote in message news:***@4ax.com...

I've seldom used time.windows.com. Can you imagine jamming all of new York
thru the same subway entrance at the same time ?
Try any of the 5 nist servers. You'll have fewer problems, and be able to
update more than once a week.
I do it hourly.
There are other time servers. But the nist ones do the job just fine.
k***@yahoo.com.invalid
2007-04-07 01:53:16 UTC
Permalink
Post by Richard G. Harper
Dude, time.windows.com is an alias that points to a bank of servers. Just
like microsoft.com, google.com, and the like.
Well I've had nothing but trouble with time.windows.com. ie: set mine to update hourly, not weekly. I can no longer have Vista use time.windows.com. It fails every time.

I can change it back to check weekly and go back to time.windows.com. But why ?
--
more pix @ http://members.toast.net/cbminfo/index.html
Whip
2007-04-06 22:52:00 UTC
Permalink
Checked with NSLOOKUP and it returns a Name of SIWEB.MICROSOFT.AKADNS.NET
Address of 207.46.197.32 and Aliases of time.windows.com. Any suggestions on
how to troubleshoot the DNS resolution?
Post by TDM
Post by Whip
I get this message: " NtpClient was unable to set a manual peer to use as
a time source because of DNS resolution error on 'time.windows.com,0x9'.
NtpClient will try again in 15 minutes and double the reattempt interval
thereafter. The error was: No such host is known. (0x80072AF9) "
These show up in the System Windows logs in the Event viewer. I set up a
filter for the Time-Service entries and see that there have been 242 in the
last 32 days.
The writeup on this also says that it will run once a week. I am seeing it
trying to run everyday. This process has worked 12 out of the last 32 days
since Vista was installed on March 5th. For now, I have stopped it from
starting using MSCONFIG, but wonder if I may have created another problem.
Shell out to a command prompt and try "nslookup time.windows.com"
If you do not get an IP address back, then your event log is telling you
the truth, you cannot resolve the hostname via DNS. If you do get an
IP back, then something else is busticated.
I dont have Vista in front of me know, but in XP, you set the server
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
Look for NtpServer here and try setting it to the IP of time.microsoft.com
which
is currently 207.46.197.32,0x1. Not a good idea to hard code IP's so just do
this
as a test. If it works, try to figure out what is wrong with your DNS
resolution.
Also note that systems in an Active Directory domain will likely have this
value
overriden by a GPO.
TDM
Guy Thomas
2007-04-06 19:47:32 UTC
Permalink
Post by Whip
I get this message: " NtpClient was unable to set a manual peer to use as
a time source because of DNS resolution error on 'time.windows.com,0x9'.
NtpClient will try again in 15 minutes and double the reattempt interval
thereafter. The error was: No such host is known. (0x80072AF9) "
These show up in the System Windows logs in the Event viewer. I set up a
filter for the Time-Service entries and see that there have been 242 in the
last 32 days.
The writeup on this also says that it will run once a week. I am seeing it
trying to run everyday. This process has worked 12 out of the last 32 days
since Vista was installed on March 5th. For now, I have stopped it from
starting using MSCONFIG, but wonder if I may have created another problem.
Here is information on setting Net Time /setsntp

http://computerperformance.co.uk/ezine/ezine97.htm

Guy
Continue reading on narkive:
Loading...