Windows 2003 W32Time Errors

  • Thread starter Thread starter kilacali11
  • Start date Start date
K

kilacali11

Server has consistently logged the following errors:



W32Time, Event ID: 38

The time provider NtpClient cannot reach or is currently receiving invalid
time data from *server_address*(ntp.m|0x1|192.168.37.15|->*IP_Address*:123).



W32Time, Event ID: 47
Time Provider NtpClient: No valid response has been received from manually
configured peer *Server_Address*,0x0
after 8 attempts to contact it. This peer will be discarded as a time source
and NtpClient will attempt to
discover a new peer wiht this DNS Name.

W32Time, Event ID: 29
The time provider NtpClient si 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 *(Value varies)* minutes. NtpClient has no source of accurate time.

Each instance where an attempt is made to validate the time, the above
errors occur within minutes of each other.



Some information / Some things I've already tried:

-Server's W32Time Parameters show the type as NTP.
-The different time services I've attempted are NTP servers. They can all be
pinged by the server successfully.
-I used the command prompt to send requests to each address in both Symmetic
Active Mode and Client PC.
-All outbound ports are open, port 123 UDP is allowed by the firewall.



Any help on the matter would be greatly appreciated. Thank you
 
To resolve this problem, configure Windows Time to use client mode with 0x08. This search result may help,

Event ID 38, 47 and 29To resolve this problem, configure Windows Time to use client mode with 0x08 (send request as Client mode) when it synchronizes with the time server. ...
http://www.chicagotech.net/troubleshooting/eventid47.htm


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"kilacali11" <kilacali11@discussions.microsoft.com> wrote in message news:686A15DA-5B7A-47A6-A6A7-3859E4CBBABE@microsoft.com...
Server has consistently logged the following errors:



W32Time, Event ID: 38

The time provider NtpClient cannot reach or is currently receiving invalid
time data from *server_address*(ntp.m|0x1|192.168.37.15|->*IP_Address*:123).



W32Time, Event ID: 47
Time Provider NtpClient: No valid response has been received from manually
configured peer *Server_Address*,0x0
after 8 attempts to contact it. This peer will be discarded as a time source
and NtpClient will attempt to
discover a new peer wiht this DNS Name.

W32Time, Event ID: 29
The time provider NtpClient si 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 *(Value varies)* minutes. NtpClient has no source of accurate time.

Each instance where an attempt is made to validate the time, the above
errors occur within minutes of each other.



Some information / Some things I've already tried:

-Server's W32Time Parameters show the type as NTP.
-The different time services I've attempted are NTP servers. They can all be
pinged by the server successfully.
-I used the command prompt to send requests to each address in both Symmetic
Active Mode and Client PC.
-All outbound ports are open, port 123 UDP is allowed by the firewall.



Any help on the matter would be greatly appreciated. Thank you
 
Back
Top