Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1072
  • Last Modified:

W32Time Error

I configured all windows servers as NTP client to a non-windows based NTP server.

I made the registry changes as described in this article:
http://support.microsoft.com/kb/816042

and then I kept getting the errors in event viewer as follows (event 38, 27, 49)
Event Type: Information
Event Source: W32Time
Event Category: None
Event ID: 38
Computer: ComputerName
Description: The time provider NtpClient cannot reach or is currently receiving invalid time data from NTP_server_IP_Address.

Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 47
Computer: ComputerName
Description: Time Provider NtpClient: No valid response has been received from manually configured peer NTP_server_IP_Address after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS name.

Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Computer: ComputerName
Description: 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.

I thought the answer is as the following link suggests: (configure Windows Time to use client mode when it synchronizes with the time server):
http://support.microsoft.com/kb/875424

However, I am still getting the same errors all the time!!

 
0
datacomsmt
Asked:
datacomsmt
  • 4
  • 3
1 Solution
 
ChiefITCommented:

Have you read this article?

http://www.chicagotech.net/troubleshooting/eventid47.htm

This one usually gets you going.
0
 
ChiefITCommented:
Another thing it could be is a firewall blockage. Do you have firewalls up on server and/or client. The time port is UDP 123.
0
 
datacomsmtAuthor Commented:
I will check the link in a minute, as for udp 123 it is open on the FW.
Thanks
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
datacomsmtAuthor Commented:
chief,
i checked the link, it is exactly as "http://support.microsoft.com/kb/875424" suggests... which is to get windows to send sync requests in client mode.... i've done that, but it is still not working and i'm still getting the events
0
 
ChiefITCommented:
Here is the method I like to use for time: (authoritative time server)
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Q_22799695.html
0
 
datacomsmtAuthor Commented:
yes, that is what i did, as you see in my question, i used http://support.microsoft.com/kb/816042 to configure an authoritative time server which is what you suggest! but it is not working!!
0
 
ChiefITCommented:
http://support.microsoft.com/kb/816042

On the article, it also says, "if the PDC master is set to synchronize with itself you will see the following events." The events they describe are the events shown on your issues.

If you download Symmtime, it will synchronize your PDC to an outside source for you. It uses port 80, so it is not often blocked.
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Q_22799695.html

Right now, I think you are synchronizing the time server, (your PDCe), to itself.

0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now