Time Sync Issue on DC's

[Guest Harleyd]

So I have inherited a new location which I am finding some problems with. I

am receiving continuous errors in the event log related to time

synchronization on our eight 2003 SP2 Domain Controllers. Here is what I am

getting on my PDC:

 

Event Type: Error

Event Source: W32Time

Event Category: None

Event ID: 29

Date: 4/1/2008

Time: 11:49:28 AM

User: N/A

Computer: FDC-P02

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 120 minutes. NtpClient has no

source of accurate time.

 

Event Type: Warning

Event Source: W32Time

Event Category: None

Event ID: 47

Date: 4/1/2008

Time: 11:49:28 AM

User: N/A

Computer: FDC-P02

Description:

Time Provider NtpClient: No valid response has been received from manually

configured peer time.windows.com,0x1 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: Information

Event Source: W32Time

Event Category: None

Event ID: 38

Date: 4/1/2008

Time: 6:49:28 AM

User: N/A

Computer: FDC-P02

Description:

The time provider NtpClient cannot reach or is currently receiving invalid

time data from time.windows.com

(ntp.m|0x1|10.XXX.XX.XXX:123->207.XX.XXX.XX:123).

 

Event Type: Warning

Event Source: W32Time

Event Category: None

Event ID: 36

Date: 4/1/2008

Time: 6:04:28 AM

User: N/A

Computer: FDC-P02

Description:

The time service has not synchronized the system time for 86400 seconds

because none of the time service providers provided a usable time stamp. The

time service is no longer synchronized and cannot provide the time to other

clients or update the system clock. Monitor the system events displayed in

the Event Viewer to make sure that a more serious problem does not exist.

 

Event Type: Error

Event Source: W32Time

Event Category: None

Event ID: 29

Date: 4/1/2008

Time: 3:49:28 AM

User: N/A

Computer: FDC-P02

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 60 minutes. NtpClient has no

source of accurate time.

 

Event Type: Warning

Event Source: W32Time

Event Category: None

Event ID: 47

Date: 4/1/2008

Time: 3:49:28 AM

User: N/A

Computer: FDC-P02

Description:

Time Provider NtpClient: No valid response has been received from manually

configured peer time.windows.com,0x1 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: Warning

Event Source: W32Time

Event Category: None

Event ID: 22

Date: 3/31/2008

Time: 6:00:37 AM

User: N/A

Computer: FDC-P02

Description:

The time provider NtpServer encountered an error while digitally signing the

NTP response for peer 10.X.XXX.XX:123. NtpServer cannot provide secure

(signed) time to the client and will ignore the request. The error was: Not

enough storage is available to process this command. (0x80070008)

 

On FDC-P03 time /querysntp shows it configured to Tock.usno.navy.mil, Net

time shows it pointing to another DC, FDC-P4

Note that Tock.usno.navy.mil seems to be restricted to just military and gov.

On my PDC, FDC-P02 SNTP Query shows it configured to Time.windows.com, Net

time shows it pointing to another DC, FDC-P4

On FDC-P04 through FDC-P08 SNTP Query shows it configured to

Time.windows.com, Net time shows it pointing to another DC, FDC-P4

 

FDC-P01 has the Schema and Domain Naming roles

FDC-P02 has the PDC, RID and Infrastructure roles

 

Thanks!

[Guest Meinolf Weber]

Re: Time Sync Issue on DC's

 

Hello Harleyd,

 

Configure the PDCEmulator to sync with an external time source and reconfigure

the other machines to use only domain time.

 

PDCEmulator:

w32tm /config /manualpeerlist:peers /syncfromflags:manual /reliable:yes /update

 

With "peers" you can set the time source, either DNS name (time.windows.com)

or an ip address from a reliable time source.

 

Here you can find some of them:

http://www.pool.ntp.org/

 

 

All other machines:

To configure a client computer for automatic domain time synchronization

 

1. Open a Command Prompt.

 

2. Type the following command and then press ENTER:

 

w32tm /config /syncfromflags:domhier /update

 

3. Type the following command and then press ENTER:

 

net stop w32time

 

4. Type the following command and then press ENTER:

 

net start w32time

 

 

 

 

 

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

> So I have inherited a new location which I am finding some problems

> with. I am receiving continuous errors in the event log related to

> time synchronization on our eight 2003 SP2 Domain Controllers. Here is

> what I am getting on my PDC:

>

> Event Type: Error

> Event Source: W32Time

> Event Category: None

> Event ID: 29

> Date: 4/1/2008

> Time: 11:49:28 AM

> User: N/A

> Computer: FDC-P02

> 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 120 minutes. NtpClient

> has no

> source of accurate time.

> Event Type: Warning

> Event Source: W32Time

> Event Category: None

> Event ID: 47

> Date: 4/1/2008

> Time: 11:49:28 AM

> User: N/A

> Computer: FDC-P02

> Description:

> Time Provider NtpClient: No valid response has been received from

> manually

> configured peer time.windows.com,0x1 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: Information

> Event Source: W32Time

> Event Category: None

> Event ID: 38

> Date: 4/1/2008

> Time: 6:49:28 AM

> User: N/A

> Computer: FDC-P02

> Description:

> The time provider NtpClient cannot reach or is currently receiving

> invalid

> time data from time.windows.com

> (ntp.m|0x1|10.XXX.XX.XXX:123->207.XX.XXX.XX:123).

> Event Type: Warning

> Event Source: W32Time

> Event Category: None

> Event ID: 36

> Date: 4/1/2008

> Time: 6:04:28 AM

> User: N/A

> Computer: FDC-P02

> Description:

> The time service has not synchronized the system time for 86400

> seconds

> because none of the time service providers provided a usable time

> stamp. The

> time service is no longer synchronized and cannot provide the time to

> other

> clients or update the system clock. Monitor the system events

> displayed in

> the Event Viewer to make sure that a more serious problem does not

> exist.

> Event Type: Error

> Event Source: W32Time

> Event Category: None

> Event ID: 29

> Date: 4/1/2008

> Time: 3:49:28 AM

> User: N/A

> Computer: FDC-P02

> 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 60 minutes. NtpClient has

> no

> source of accurate time.

> Event Type: Warning

> Event Source: W32Time

> Event Category: None

> Event ID: 47

> Date: 4/1/2008

> Time: 3:49:28 AM

> User: N/A

> Computer: FDC-P02

> Description:

> Time Provider NtpClient: No valid response has been received from

> manually

> configured peer time.windows.com,0x1 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: Warning

> Event Source: W32Time

> Event Category: None

> Event ID: 22

> Date: 3/31/2008

> Time: 6:00:37 AM

> User: N/A

> Computer: FDC-P02

> Description:

> The time provider NtpServer encountered an error while digitally

> signing the

> NTP response for peer 10.X.XXX.XX:123. NtpServer cannot provide

> secure

> (signed) time to the client and will ignore the request. The error

> was: Not

> enough storage is available to process this command. (0x80070008)

>

> On FDC-P03 time /querysntp shows it configured to Tock.usno.navy.mil,

> Net

> time shows it pointing to another DC, FDC-P4

> Note that Tock.usno.navy.mil seems to be restricted to just military

> and gov.

> On my PDC, FDC-P02 SNTP Query shows it configured to Time.windows.com,

> Net

> time shows it pointing to another DC, FDC-P4

> On FDC-P04 through FDC-P08 SNTP Query shows it configured to

> Time.windows.com, Net time shows it pointing to another DC, FDC-P4

> FDC-P01 has the Schema and Domain Naming roles

> FDC-P02 has the PDC, RID and Infrastructure roles

> Thanks!

>