Win32Time Error Message

Virginia · 17-04-2007

I see the following error message, frequently, when I go into computer
management/system tools/system:

Win32Time

Event ID 29
The time provider NtpClient is configured to acquire time from one or more
time sources, however none of the sources are currently accessible. No
attempt to contact a source will be made for 15 minutes. NtpClient has no
source of accurate time.

or,

Win32Time

Event ID 17

Time Provider NtpClient: An error occurred during DNS lookup of the manually
configured peer 'time.windows.com,0x1'. NtpClient will try the DNS lookup
again in 15 minutes. The error was: A socket operation was attempted to an
unreachable host. (0x80072751)

The solution came up as the following, but not sure how to go about doing
any of the actions listed below:

a.. Verify that the local computer is capable of contacting the desired
source. In most cases, a simple connectivity test such as "ping" is
adequate.

a.. Confirm that Windows Time Service (or other NTP Time Service) is
running and available on the source system.

a.. If you are using a manually configured peer, such as time.windows.com,
verify that the name is typed correctly and that the system is available.

a.. Confirm that there are no network devices that block traffic on port
123 between the local computer and the time source.

Thanks for any assistance.

Virginia

TaurArian [MS-MVP] · 17-04-2007

Try another time server.

http://support.microsoft.com/kb/262680
A list of the Simple Network Time Protocol (SNTP) time servers that are available on the
Internet

Just type in the combo listbox.
No registry editing.

--

====================================
TaurArian [MS-MVP] 2005-2007 - Australia
====================================
How to make a good post: http://www.dts-l.org/goodpost.htm
Backup and data recovery: http://www.acronis.com.sg/
Enhancing file system performance: http://www.diskeeper.com/defrag.asp

"Virginia" <carlson@metrocast.net> wrote in message
news:OcMhw$GgHHA.4536@TK2MSFTNGP04.phx.gbl...
|I see the following error message, frequently, when I go into computer
| management/system tools/system:
|
| Win32Time
|
| Event ID 29
| The time provider NtpClient is configured to acquire time from one or more
| time sources, however none of the sources are currently accessible. No
| attempt to contact a source will be made for 15 minutes. NtpClient has no
| source of accurate time.
|
| or,
|
| Win32Time
|
| Event ID 17
|
| Time Provider NtpClient: An error occurred during DNS lookup of the manually
| configured peer 'time.windows.com,0x1'. NtpClient will try the DNS lookup
| again in 15 minutes. The error was: A socket operation was attempted to an
| unreachable host. (0x80072751)
|
| The solution came up as the following, but not sure how to go about doing
| any of the actions listed below:
|
| a.. Verify that the local computer is capable of contacting the desired
| source. In most cases, a simple connectivity test such as "ping" is
| adequate.
|
| a.. Confirm that Windows Time Service (or other NTP Time Service) is
| running and available on the source system.
|
| a.. If you are using a manually configured peer, such as time.windows.com,
| verify that the name is typed correctly and that the system is available.
|
| a.. Confirm that there are no network devices that block traffic on port
| 123 between the local computer and the time source.
|
| Thanks for any assistance.
|
|
| Virginia
|
|

Wesley Vogel · 17-04-2007

A recent Windows Update (Daylight Saving Time maybe) has messed this up.

Try this.

Double click your clock on the taskbar.
Date and Time Properties should open.
Click on the Internet Time Tab.
In the box next to Server, type or paste: time-b.nist.gov
Click the Apply button.
Then click the Update Now button and wait a while.
Close the Date and Time Properties when you see: The time has been
successfully...

Server...
[[Enables you to select the Internet time server with which you want to
synchronize your computer clock. Click one of the options or type in an
address.
The time server time.windows.com is operated by Microsoft, and time.nist.gov
is operated by the U.S. government. Other time servers provided by your
computer’s manufacturer might also be listed. You can type the name of a
time server if you want to use one that is not listed. Only time servers
that use the Simple Network Time Protocol (SNTP) will work. Inserting an
Internet address that uses the Hypertext Transfer Protocol (HTTP) will not
work.]]

Update Now button...
[[Click to synchronize your computer clock with the selected Internet Time
Server. You must be connected to the Internet, and the Automatically
synchronize with an Internet time server check box must be selected.
If synchronization fails, a message will display below explaining the
reason. Most corporate firewalls will block time synchronization, as will
some personal firewalls. If the network is too busy or not available for
some reason, try again later.]]

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:OcMhw$GgHHA.4536@TK2MSFTNGP04.phx.gbl,
Virginia <carlson@metrocast.net> hunted and pecked:
> I see the following error message, frequently, when I go into computer
> management/system tools/system:
>
> Win32Time
>
> Event ID 29
> The time provider NtpClient is configured to acquire time from one or more
> time sources, however none of the sources are currently accessible. No
> attempt to contact a source will be made for 15 minutes. NtpClient has no
> source of accurate time.
>
> or,
>
> Win32Time
>
> Event ID 17
>
> Time Provider NtpClient: An error occurred during DNS lookup of the
> manually configured peer 'time.windows.com,0x1'. NtpClient will try the
> DNS lookup again in 15 minutes. The error was: A socket operation was
> attempted to an unreachable host. (0x80072751)
>
> The solution came up as the following, but not sure how to go about doing
> any of the actions listed below:
>
> a.. Verify that the local computer is capable of contacting the desired
> source. In most cases, a simple connectivity test such as "ping" is
> adequate.
>
> a.. Confirm that Windows Time Service (or other NTP Time Service) is
> running and available on the source system.
>
> a.. If you are using a manually configured peer, such as
> time.windows.com, verify that the name is typed correctly and that the
> system is available.
> a.. Confirm that there are no network devices that block traffic on port
> 123 between the local computer and the time source.
>
> Thanks for any assistance.
>
>
> Virginia

Wesley Vogel · 17-04-2007

I didn't see your post when I posted. Cool.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:%23SV%23mMHgHHA.4284@TK2MSFTNGP06.phx.gbl,
TaurArian [MS-MVP] <taurarianREMOVECAPS@gmail.com> hunted and pecked:
> Try another time server.
>
> http://support.microsoft.com/kb/262680
> A list of the Simple Network Time Protocol (SNTP) time servers that are
> available on the Internet
>
> Just type in the combo listbox.
> No registry editing.
>
> --
>
> ====================================
> TaurArian [MS-MVP] 2005-2007 - Australia
> ====================================
> How to make a good post: http://www.dts-l.org/goodpost.htm
> Backup and data recovery: http://www.acronis.com.sg/
> Enhancing file system performance: http://www.diskeeper.com/defrag.asp
>
>
> "Virginia" <carlson@metrocast.net> wrote in message
> news:OcMhw$GgHHA.4536@TK2MSFTNGP04.phx.gbl...
>> I see the following error message, frequently, when I go into computer
>> management/system tools/system:
>>
>> Win32Time
>>
>> Event ID 29
>> The time provider NtpClient is configured to acquire time from one or
>> more time sources, however none of the sources are currently accessible.
>> No attempt to contact a source will be made for 15 minutes. NtpClient
>> has no source of accurate time.
>>
>> or,
>>
>> Win32Time
>>
>> Event ID 17
>>
>> Time Provider NtpClient: An error occurred during DNS lookup of the
>> manually configured peer 'time.windows.com,0x1'. NtpClient will try the
>> DNS lookup again in 15 minutes. The error was: A socket operation was
>> attempted to an unreachable host. (0x80072751)
>>
>> The solution came up as the following, but not sure how to go about doing
>> any of the actions listed below:
>>
>> a.. Verify that the local computer is capable of contacting the desired
>> source. In most cases, a simple connectivity test such as "ping" is
>> adequate.
>>
>> a.. Confirm that Windows Time Service (or other NTP Time Service) is
>> running and available on the source system.
>>
>> a.. If you are using a manually configured peer, such as
>> time.windows.com, verify that the name is typed correctly and that the
>> system is available.
>>
>> a.. Confirm that there are no network devices that block traffic on port
>> 123 between the local computer and the time source.
>>
>> Thanks for any assistance.
>>
>>
>> Virginia

TaurArian · 17-04-2007

Hi Wes,

Simple and effective, no reg editing. Don't know what the problem is with
the time server. I chose one in OZ for my home computer. The one at work is
still erroring out.

Kaylene

"Wesley Vogel" wrote:

> I didn't see your post when I posted. Cool.
>
> --
> Hope this helps. Let us know.
>
> Wes
> MS-MVP Windows Shell/User
>
>

Virginia · 17-04-2007

Thanks so much to all for the tips! Had no idea how to do this.

Virginia

"Wesley Vogel" <123WVogel955@comcast.net> wrote in message
news:eH1r09HgHHA.1244@TK2MSFTNGP04.phx.gbl...
>A recent Windows Update (Daylight Saving Time maybe) has messed this up.
>
> Try this.
>
> Double click your clock on the taskbar.
> Date and Time Properties should open.
> Click on the Internet Time Tab.
> In the box next to Server, type or paste: time-b.nist.gov
> Click the Apply button.
> Then click the Update Now button and wait a while.
> Close the Date and Time Properties when you see: The time has been
> successfully...
>
>
> Server...
> [[Enables you to select the Internet time server with which you want to
> synchronize your computer clock. Click one of the options or type in an
> address.
> The time server time.windows.com is operated by Microsoft, and
> time.nist.gov
> is operated by the U.S. government. Other time servers provided by your
> computer’s manufacturer might also be listed. You can type the name of a
> time server if you want to use one that is not listed. Only time servers
> that use the Simple Network Time Protocol (SNTP) will work. Inserting an
> Internet address that uses the Hypertext Transfer Protocol (HTTP) will not
> work.]]
>
> Update Now button...
> [[Click to synchronize your computer clock with the selected Internet Time
> Server. You must be connected to the Internet, and the Automatically
> synchronize with an Internet time server check box must be selected.
> If synchronization fails, a message will display below explaining the
> reason. Most corporate firewalls will block time synchronization, as will
> some personal firewalls. If the network is too busy or not available for
> some reason, try again later.]]
>
>
> --
> Hope this helps. Let us know.
>
> Wes
> MS-MVP Windows Shell/User
>
> In news:OcMhw$GgHHA.4536@TK2MSFTNGP04.phx.gbl,
> Virginia <carlson@metrocast.net> hunted and pecked:
>> I see the following error message, frequently, when I go into computer
>> management/system tools/system:
>>
>> Win32Time
>>
>> Event ID 29
>> The time provider NtpClient is configured to acquire time from one or
>> more
>> time sources, however none of the sources are currently accessible. No
>> attempt to contact a source will be made for 15 minutes. NtpClient has no
>> source of accurate time.
>>
>> or,
>>
>> Win32Time
>>
>> Event ID 17
>>
>> Time Provider NtpClient: An error occurred during DNS lookup of the
>> manually configured peer 'time.windows.com,0x1'. NtpClient will try the
>> DNS lookup again in 15 minutes. The error was: A socket operation was
>> attempted to an unreachable host. (0x80072751)
>>
>> The solution came up as the following, but not sure how to go about doing
>> any of the actions listed below:
>>
>> a.. Verify that the local computer is capable of contacting the desired
>> source. In most cases, a simple connectivity test such as "ping" is
>> adequate.
>>
>> a.. Confirm that Windows Time Service (or other NTP Time Service) is
>> running and available on the source system.
>>
>> a.. If you are using a manually configured peer, such as
>> time.windows.com, verify that the name is typed correctly and that the
>> system is available.
>> a.. Confirm that there are no network devices that block traffic on port
>> 123 between the local computer and the time source.
>>
>> Thanks for any assistance.
>>
>>
>> Virginia
>

Wesley Vogel · 17-04-2007

Hi Kaylene,

Say hi to the Wizard for me. ;-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:74AFBBA6-8120-43B1-A8C0-FC5E6E541B39@microsoft.com,
TaurArian <TaurArian@discussions.microsoft.com> hunted and pecked:
> Hi Wes,
>
> Simple and effective, no reg editing. Don't know what the problem is with
> the time server. I chose one in OZ for my home computer. The one at work
> is still erroring out.
>
> Kaylene
>
> "Wesley Vogel" wrote:
>
>> I didn't see your post when I posted. Cool.
>>
>> --
>> Hope this helps. Let us know.
>>
>> Wes
>> MS-MVP Windows Shell/User

Wesley Vogel · 17-04-2007

You're welcome, Virginia.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:utijUwOgHHA.3368@TK2MSFTNGP03.phx.gbl,
Virginia <carlson@metrocast.net> hunted and pecked:
> Thanks so much to all for the tips! Had no idea how to do this.
>
> Virginia
>
>
> "Wesley Vogel" <123WVogel955@comcast.net> wrote in message
> news:eH1r09HgHHA.1244@TK2MSFTNGP04.phx.gbl...
>> A recent Windows Update (Daylight Saving Time maybe) has messed this up.
>>
>> Try this.
>>
>> Double click your clock on the taskbar.
>> Date and Time Properties should open.
>> Click on the Internet Time Tab.
>> In the box next to Server, type or paste: time-b.nist.gov
>> Click the Apply button.
>> Then click the Update Now button and wait a while.
>> Close the Date and Time Properties when you see: The time has been
>> successfully...
>>
>>
>> Server...
>> [[Enables you to select the Internet time server with which you want to
>> synchronize your computer clock. Click one of the options or type in an
>> address.
>> The time server time.windows.com is operated by Microsoft, and
>> time.nist.gov
>> is operated by the U.S. government. Other time servers provided by your
>> computer’s manufacturer might also be listed. You can type the name of a
>> time server if you want to use one that is not listed. Only time servers
>> that use the Simple Network Time Protocol (SNTP) will work. Inserting an
>> Internet address that uses the Hypertext Transfer Protocol (HTTP) will
>> not work.]]
>>
>> Update Now button...
>> [[Click to synchronize your computer clock with the selected Internet
>> Time Server. You must be connected to the Internet, and the
>> Automatically synchronize with an Internet time server check box must be
>> selected. If synchronization fails, a message will display below
>> explaining the
>> reason. Most corporate firewalls will block time synchronization, as will
>> some personal firewalls. If the network is too busy or not available for
>> some reason, try again later.]]
>>
>>
>> --
>> Hope this helps. Let us know.
>>
>> Wes
>> MS-MVP Windows Shell/User
>>
>> In news:OcMhw$GgHHA.4536@TK2MSFTNGP04.phx.gbl,
>> Virginia <carlson@metrocast.net> hunted and pecked:
>>> I see the following error message, frequently, when I go into computer
>>> management/system tools/system:
>>>
>>> Win32Time
>>>
>>> Event ID 29
>>> The time provider NtpClient is configured to acquire time from one or
>>> more
>>> time sources, however none of the sources are currently accessible. No
>>> attempt to contact a source will be made for 15 minutes. NtpClient has
>>> no source of accurate time.
>>>
>>> or,
>>>
>>> Win32Time
>>>
>>> Event ID 17
>>>
>>> Time Provider NtpClient: An error occurred during DNS lookup of the
>>> manually configured peer 'time.windows.com,0x1'. NtpClient will try the
>>> DNS lookup again in 15 minutes. The error was: A socket operation was
>>> attempted to an unreachable host. (0x80072751)
>>>
>>> The solution came up as the following, but not sure how to go about
>>> doing any of the actions listed below:
>>>
>>> a.. Verify that the local computer is capable of contacting the desired
>>> source. In most cases, a simple connectivity test such as "ping" is
>>> adequate.
>>>
>>> a.. Confirm that Windows Time Service (or other NTP Time Service) is
>>> running and available on the source system.
>>>
>>> a.. If you are using a manually configured peer, such as
>>> time.windows.com, verify that the name is typed correctly and that the
>>> system is available.
>>> a.. Confirm that there are no network devices that block traffic on
>>> port 123 between the local computer and the time source.
>>>
>>> Thanks for any assistance.
>>>
>>>
>>> Virginia