I would certainly check into it, it is implying the
machines aren't syncing their time which could be bad for you.
Normally I just set this with
net time /setsntp:server
However it would appear they just do the same
thing.
It used to be w32tm had a cool switch for testing the time
sync process and outputting a verbose listing of all of the steps and values,
that doesn't appear to be in there now. I would wonder how people are supposed
to troubleshoot now.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James Carter
Sent: Wednesday, May 03, 2006 3:47 AM
To: [email protected]
Subject: [ActiveDir] Query regarding Windows Time Service
I have a query regarding the Windows Time Service.
Our environment is Windows 2003 FFL, Single Domain.
We have a Network Time Server which I have configured our PDCe to use.
Having read other posts I also configured our Core DC's to use this Time Server
so that if the PDCe failed, I could just seize the role to another DC and have
one less thing to configure.
What I am receiving is Eventlog messages saying "the time provider
NtpClient is configured to acquire a 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 960 minutes. Ntpclient has no source of accurate time" Event ID
29
This is received on all of the Core DC's that I have configured to use the
Network Time Server rather than the PDCe.
All I did was run the following command on each DC that could potentially
be used as a PDCe
w32tm /config /manualpeerlist:10.1.1.225 /syncfromflags:manual
/reliable:yes /update
Anyone know why I would be receiving these event messages, should I be
concerned?
James
Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2ยข/min or less.
