Re: W32Time Problems

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I have setup two domain controllers in a test environment to test this
solution.
I am still receiving the same errors. The domain controller that has the PDC
Emulator role in DomainSRV1. See below events.

DomainSRV20 11:42am 20/04/09 ran command "w32tm /config /update
/manualpeerlist:"DomainSRV1.internal.testdomain.com" /syncfromflags:MANUAL
/reliable:YES"

DomainSRV20 11:42am 20/04/09 ran command "net stop w32time && net start
w32time"

DomainSRV20 11:43:17am 20/04/09

Event Type: Information
Event Source: W32Time
Event Category: None
Event ID: 35
Date: 4/20/2009
Time: 11:43:30 AM
User: N/A
Computer: DomainSRV20
Description:
The time service is now synchronizing the system time with the time source
DomainSRV1.internal.testdomain.com
(ntp.m|0x0|169.254.10.60:123->169.254.10.10:123).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

DomainSRV1 11:56am 20/04/09 rebooted server DomainSRV1

Event Type: Information
Event Source: W32Time
Event Category: None
Event ID: 38
Date: 4/20/2009
Time: 11:57:12 AM
User: N/A
Computer: DomainSRV20
Description:
The time provider NtpClient cannot reach or is currently receiving invalid
time data from DomainSRV1.internal.testdomain.com
(ntp.m|0x0|169.254.10.60:123->169.254.10.10:123).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: W32Time
Event Category: None
Event ID: 38
Date: 4/20/2009
Time: 11:57:12 AM
User: N/A
Computer: DomainSRV20
Description:
The time provider NtpClient cannot reach or is currently receiving invalid
time data from DomainSRV1.internal.testdomain.com
(ntp.m|0x0|169.254.10.60:123->169.254.10.10:123).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 50
Date: 4/21/2009
Time: 6:15:42 AM
User: N/A
Computer: DomainSRV20
Description:
The time service detected a time difference of greater than 5000
milliseconds for 900 seconds. The time difference might be caused by
synchronization with low-accuracy time sources or by suboptimal network
conditions. The time service is no longer synchronized and cannot provide the
time to other clients or update the system clock. When a valid time stamp is
received from a time service provider, the time service will correct itself.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


DomainSRV20 9:57am 21/04/09 ran command "w32tm /config /syncfromflags:domhier"

DomainSRV20 9:57am 21/04/09 ran command "net stop w32time && net start
w32time"

Event Type: Information
Event Source: W32Time
Event Category: None
Event ID: 37
Date: 4/21/2009
Time: 9:57:17 AM
User: N/A
Computer: DomainSRV20
Description:
The time provider NtpClient is currently receiving valid time data from
DomainSRV1.internal.testdomain.com
(ntp.m|0x0|169.254.10.60:123->169.254.10.10:123).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

DomainSRV1 10:47am 21/04/09 shutdown server DomainSRV1

DomainSRV20 10:51:51am

Event Type: Information
Event Source: W32Time
Event Category: None
Event ID: 38
Date: 4/21/2009
Time: 10:51:51 AM
User: N/A
Computer: DomainSRV20
Description:
The time provider NtpClient cannot reach or is currently receiving invalid
time data from DomainSRV1.internal.testdomain.com
(ntp.m|0x0|169.254.10.60:123->169.254.10.10:123).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 47
Date: 4/21/2009
Time: 10:56:40 AM
User: N/A
Computer: DomainSRV20
Description:
Time Provider NtpClient: No valid response has been received from manually
configured peer DomainSRV1.internal.testdomain.com 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.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: 4/21/2009
Time: 10:56:40 AM
User: N/A
Computer: DomainSRV20
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.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Information
Event Source: W32Time
Event Category: None
Event ID: 38
Date: 4/21/2009
Time: 10:51:51 AM
User: N/A
Computer: DomainSRV20
Description:
The time provider NtpClient cannot reach or is currently receiving invalid
time data from DomainSRV1.internal.testdomain.com
(ntp.m|0x0|169.254.10.60:123->169.254.10.10:123).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 47
Date: 4/21/2009
Time: 10:56:40 AM
User: N/A
Computer: DomainSRV20
Description:
Time Provider NtpClient: No valid response has been received from manually
configured peer DomainSRV1.internal.testdomain.com 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.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: 4/21/2009
Time: 10:56:40 AM
User: N/A
Computer: DomainSRV20
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.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

DomainSRV1 10:58:30am 21/04/09 started server DomainSRV1

DomainSRV20 11:11:42am 21/04/09
Event Type: Information
Event Source: W32Time
Event Category: None
Event ID: 37
Date: 4/21/2009
Time: 11:11:42 AM
User: N/A
Computer: DomainSRV20
Description:
The time provider NtpClient is currently receiving valid time data from
DomainSRV1.internal.testdomain.com
(ntp.m|0x0|169.254.10.60:123->169.254.10.10:123).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

DomainSRV1 11:18am 21/04/09 shutdown server DomainSRV1

DomainSRV20 10:28:38am 21/04/09
Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 50
Date: 4/21/2009
Time: 11:28:38 AM
User: N/A
Computer: DomainSRV20
Description:
The time service detected a time difference of greater than 5000
milliseconds for 900 seconds. The time difference might be caused by
synchronization with low-accuracy time sources or by suboptimal network
conditions. The time service is no longer synchronized and cannot provide the
time to other clients or update the system clock. When a valid time stamp is
received from a time service provider, the time service will correct itself.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

DomainSRV20 11:28:38am 21/04/09

Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 50
Date: 4/21/2009
Time: 11:28:38 AM
User: N/A
Computer: DomainSRV20
Description:
The time service detected a time difference of greater than 5000
milliseconds for 900 seconds. The time difference might be caused by
synchronization with low-accuracy time sources or by suboptimal network
conditions. The time service is no longer synchronized and cannot provide the
time to other clients or update the system clock. When a valid time stamp is
received from a time service provider, the time service will correct itself.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

DomainSRV20 3:43:37am 21/04/09

Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 50
Date: 4/21/2009
Time: 11:28:38 AM
User: N/A
Computer: DomainSRV20
Description:
The time service detected a time difference of greater than 5000
milliseconds for 900 seconds. The time difference might be caused by
synchronization with low-accuracy time sources or by suboptimal network
conditions. The time service is no longer synchronized and cannot provide the
time to other clients or update the system clock. When a valid time stamp is
received from a time service provider, the time service will correct itself.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 50
Date: 4/21/2009
Time: 3:43:37 PM
User: N/A
Computer: DomainSRV20
Description:
The time service detected a time difference of greater than 5000
milliseconds for 900 seconds. The time difference might be caused by
synchronization with low-accuracy time sources or by suboptimal network
conditions. The time service is no longer synchronized and cannot provide the
time to other clients or update the system clock. When a valid time stamp is
received from a time service provider, the time service will correct itself.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

.

Relevant Pages

  • Re: W32Time Problems
    ... You are not receiving an error, it is a warning and the time should correct itself. ... The time service detected a time difference of greater than 5000 ... synchronization with low-accuracy time sources or by suboptimal ... see Help and Support Center at ...
    (microsoft.public.windows.server.setup)
  • Re: W32Time Problems
    ... synchronization with low-accuracy time sources or by suboptimal network ... The time service is no longer synchronized and cannot provide the ... see Help and Support Center at ... The time provider NtpClient cannot reach or is currently receiving ...
    (microsoft.public.windows.server.setup)
  • Re: W32Time Problems
    ... Go to "Configuring the Windows Time service to use an internal hardware clock" in: ... see Help and Support Center at ... The time provider NtpClient cannot reach or is currently receiving ... time sources, however none of the sources are currently accessible. ...
    (microsoft.public.windows.server.setup)
  • Time issues
    ... we are receiving issues with the time service on all our ... The time provider NtpClient is configured to acquire time from one or more ... see Help and Support Center at ... The time provider NtpClient cannot reach or is currently receiving invalid ...
    (microsoft.public.windows.server.setup)
  • Re: W32Time Problems
    ... This domain controller will be discarded as a time source and NtpClient will ... The time provider NtpClient is configured to acquire time from one or more ... I am still receiving the same errors. ... The time service detected a time difference of greater than 5000 ...
    (microsoft.public.windows.server.setup)