W32Time Problems

Our three main DC that synchronizing with Internet time server are working
correctly, it is only when we reboot these three DC that all the other DC
that point to the three DC start to start to show W32Time event errors (Event
ID: 47, 38, 36, and 29).
ll the other Domain Controllers in are environment, start to show W32Time
event errors (Event ID: 47, 38, 36, and 29). The only way we have found to
fix this is the stop and start w32time service on the Domain Controllers.
This is not practicable due to the number of Domain Controllers we have.
Back ground information:
8 * Windows 2003 SP2 32bit Domain Controllers
200 * Windows 2003 SP2 64bit Domain Controllers

The 200 * Windows 2003 SP2 64bit Domain Controllers are configured with
“w32tm /config /update /manualpeerlist:"Domain Controllers A Domain
Controllers B Domain Controllers C" /syncfromflags:MANUAL /reliable:YES�
(Where Domain Controllers A, Domain Controllers, Domain Controllers C are the
main time sources that are configured to get the time from a valid network
time source.)

w32time wrote:
> Our three main DC that synchronizing with Internet time server are
> working correctly, it is only when we reboot these three DC that all
> the other DC that point to the three DC start to start to show
> W32Time event errors (Event ID: 47, 38, 36, and 29).
> ll the other Domain Controllers in are environment, start to show
> W32Time event errors (Event ID: 47, 38, 36, and 29). The only way we
> have found to fix this is the stop and start w32time service on the
> Domain Controllers. This is not practicable due to the number of
> Domain Controllers we have. Back ground information:
> 8 * Windows 2003 SP2 32bit Domain Controllers
> 200 * Windows 2003 SP2 64bit Domain Controllers
>
> The 200 * Windows 2003 SP2 64bit Domain Controllers are configured
> with "w32tm /config /update /manualpeerlist:"Domain Controllers A
> Domain Controllers B Domain Controllers C" /syncfromflags:MANUAL
> /reliable:YES" (Where Domain Controllers A, Domain Controllers,
> Domain Controllers C are the main time sources that are configured to
> get the time from a valid network time source.)

What was wrong with using the default domain hierarchy for time sync?


--
/kj

Hello w32time,

In a domain the PDCEmulator is the time source, which should be configured
to an external time source. Nothing else has to be done by default. All other
DC's automatically sync with it and member servers and workstations use one
available DC for the time sync. So why did you change the default?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Our three main DC that synchronizing with Internet time server are
> working
> correctly, it is only when we reboot these three DC that all the other
> DC
> that point to the three DC start to start to show W32Time event errors
> (Event
> ID: 47, 38, 36, and 29).
> ll the other Domain Controllers in are environment, start to show
> W32Time
> event errors (Event ID: 47, 38, 36, and 29). The only way we have
> found to
> fix this is the stop and start w32time service on the Domain
> Controllers.
> This is not practicable due to the number of Domain Controllers we
> have.
> Back ground information:
> 8 * Windows 2003 SP2 32bit Domain Controllers
> 200 * Windows 2003 SP2 64bit Domain Controllers
> The 200 * Windows 2003 SP2 64bit Domain Controllers are configured
> with "w32tm /config /update /manualpeerlist:"Domain Controllers A
> Domain Controllers B Domain Controllers C" /syncfromflags:MANUAL
> /reliable:YES" (Where Domain Controllers A, Domain Controllers, Domain
> Controllers C are the main time sources that are configured to get the
> time from a valid network time source.)
>

I inherited the problem and just trying to resolve the issues?

"Meinolf Weber [MVP-DS]" wrote:

> Hello w32time,
>
> In a domain the PDCEmulator is the time source, which should be configured
> to an external time source. Nothing else has to be done by default. All other
> DC's automatically sync with it and member servers and workstations use one
> available DC for the time sync. So why did you change the default?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > Our three main DC that synchronizing with Internet time server are
> > working
> > correctly, it is only when we reboot these three DC that all the other
> > DC
> > that point to the three DC start to start to show W32Time event errors
> > (Event
> > ID: 47, 38, 36, and 29).
> > ll the other Domain Controllers in are environment, start to show
> > W32Time
> > event errors (Event ID: 47, 38, 36, and 29). The only way we have
> > found to
> > fix this is the stop and start w32time service on the Domain
> > Controllers.
> > This is not practicable due to the number of Domain Controllers we
> > have.
> > Back ground information:
> > 8 * Windows 2003 SP2 32bit Domain Controllers
> > 200 * Windows 2003 SP2 64bit Domain Controllers
> > The 200 * Windows 2003 SP2 64bit Domain Controllers are configured
> > with "w32tm /config /update /manualpeerlist:"Domain Controllers A
> > Domain Controllers B Domain Controllers C" /syncfromflags:MANUAL
> > /reliable:YES" (Where Domain Controllers A, Domain Controllers, Domain
> > Controllers C are the main time sources that are configured to get the
> > time from a valid network time source.)
> >
>
>
>

Hello w32time,

On the DC's run:
w32tm /config /syncfromflags:domhier /update

After that run:
net stop w32time
net start w32time

So they should use the normal domain sync with the PDCEmulator again.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> I inherited the problem and just trying to resolve the issues?
>
> "Meinolf Weber [MVP-DS]" wrote:
>
>> Hello w32time,
>>
>> In a domain the PDCEmulator is the time source, which should be
>> configured to an external time source. Nothing else has to be done by
>> default. All other DC's automatically sync with it and member servers
>> and workstations use one available DC for the time sync. So why did
>> you change the default?
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Our three main DC that synchronizing with Internet time server are
>>> working
>>> correctly, it is only when we reboot these three DC that all the
>>> other
>>> DC
>>> that point to the three DC start to start to show W32Time event
>>> errors
>>> (Event
>>> ID: 47, 38, 36, and 29).
>>> ll the other Domain Controllers in are environment, start to show
>>> W32Time
>>> event errors (Event ID: 47, 38, 36, and 29). The only way we have
>>> found to
>>> fix this is the stop and start w32time service on the Domain
>>> Controllers.
>>> This is not practicable due to the number of Domain Controllers we
>>> have.
>>> Back ground information:
>>> 8 * Windows 2003 SP2 32bit Domain Controllers
>>> 200 * Windows 2003 SP2 64bit Domain Controllers
>>> The 200 * Windows 2003 SP2 64bit Domain Controllers are configured
>>> with "w32tm /config /update /manualpeerlist:"Domain Controllers A
>>> Domain Controllers B Domain Controllers C" /syncfromflags:MANUAL
>>> /reliable:YES" (Where Domain Controllers A, Domain Controllers,
>>> Domain
>>> Controllers C are the main time sources that are configured to get
>>> the
>>> time from a valid network time source.

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.

Hello w32time,

You can not use a domain internal server as a time source that way for the
PDCEmulator. Use either an external form the internet or configure the PDCEmulator
to use the hardware clock.

Go to "Configuring the Windows Time service to use an internal hardware clock"
in:
http://support.microsoft.com/kb/816042

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> 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.
>

Sorry, I should have specified that the last entry in the forum was a log of
the step taken to test your posting from the 1/4/2009. Here is some greater
details:

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 which points to an external time
source (working correctly). The other Domain Controller, DomainSRV20 I have
run the command “w32tm /config /syncfromflags:domhier�. Then when I reboot
the Domain Controller, DomainSRV1, the other Domain Controller, DomainSRV20
shows the below errors is in the event log. The only way we can see to fix
this is to stop and start the w32time service on DomainSRV20.

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.


"Meinolf Weber [MVP-DS]" wrote:

> Hello w32time,
>
> You can not use a domain internal server as a time source that way for the
> PDCEmulator. Use either an external form the internet or configure the PDCEmulator
> to use the hardware clock.
>
> Go to "Configuring the Windows Time service to use an internal hardware clock"
> in:
> http://support.microsoft.com/kb/816042
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > 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

Hello w32time,

You are not receiving an error, it is a warning and the time should correct
itself. Or is event id 50 followed bey error entries? Also in fresh installed
doamin youhave nothing to do with any domain member for time configuration
by default, only the PDCEmulator should be conifgured for hardware clock
or external and youa re done.

Time sync in a domain runs atuomatic, no need to initiate it manal.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Sorry, I should have specified that the last entry in the forum was a
> log of the step taken to test your posting from the 1/4/2009. Here is
> some greater details:
>
> 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 which points to an
> external time source (working correctly). The other Domain Controller,
> DomainSRV20 I have run the command "w32tm /config
> /syncfromflags:domhier". Then when I reboot the Domain Controller,
> DomainSRV1, the other Domain Controller, DomainSRV20 shows the below
> errors is in the event log. The only way we can see to fix this is to
> stop and start the w32time service on DomainSRV20.
>
> 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.
>
> "Meinolf Weber [MVP-DS]" wrote:
>
>> Hello w32time,
>>
>> You can not use a domain internal server as a time source that way
>> for the PDCEmulator. Use either an external form the internet or
>> configure the PDCEmulator to use the hardware clock.
>>
>> Go to "Configuring the Windows Time service to use an internal
>> hardware clock"
>> in:
>> http://support.microsoft.com/kb/816042
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> 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

After leaving the test environment’s domain controllers for a week or so, we
are now receiving the event id 24 (Warning), then followed by event id 29
(Error).

Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 24
Date: 28/04/2009
Time: 3:53:59 AM
User: N/A
Computer: DomainSRV20
Description:
Time Provider NtpClient: No valid response has been received from domain
controller DomainSRV1.internal.testdomain.com after 8 attempts to contact it.
This domain controller will be discarded as a time source and NtpClient will
attempt to discover a new domain controller from which to synchronize.

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: 28/04/2009
Time: 3:53:59 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.

"Meinolf Weber [MVP-DS]" wrote:

> Hello w32time,
>
> You are not receiving an error, it is a warning and the time should correct
> itself. Or is event id 50 followed bey error entries? Also in fresh installed
> doamin youhave nothing to do with any domain member for time configuration
> by default, only the PDCEmulator should be conifgured for hardware clock
> or external and youa re done.
>
> Time sync in a domain runs atuomatic, no need to initiate it manal.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > Sorry, I should have specified that the last entry in the forum was a
> > log of the step taken to test your posting from the 1/4/2009. Here is
> > some greater details:
> >
> > 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 which points to an
> > external time source (working correctly). The other Domain Controller,
> > DomainSRV20 I have run the command "w32tm /config
> > /syncfromflags:domhier". Then when I reboot the Domain Controller,
> > DomainSRV1, the other Domain Controller, DomainSRV20 shows the below
> > errors is in the event log. The only way we can see to fix this is to
> > stop and start the w32time service on DomainSRV20.
> >
> > 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.
> >
> > "Meinolf Weber [MVP-DS]" wrote:
> >
> >> Hello w32time,
> >>
> >> You can not use a domain internal server as a time source that way
> >> for the PDCEmulator. Use either an external form the internet or
> >> configure the PDCEmulator to use the hardware clock.
> >>
> >> Go to "Configuring the Windows Time service to use an internal
> >> hardware clock"
> >> in:
> >> http://support.microsoft.com/kb/816042
> >> Best regards
> >>
> >> Meinolf Weber
> >> Disclaimer: This posting is provided "AS IS" with no warranties, and
> >> confers
> >> no rights.
> >> ** Please do NOT email, only reply to Newsgroups
> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> >>> 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