Re: Windows Server 2003 Windows Time Sync
- From: Meinolf Weber <meiweb(nospam)@gmx.de>
- Date: Mon, 8 Oct 2007 21:46:31 +0000 (UTC)
Hello ketz,
Can you give some more info about the network setup? And also a bit how your DNS is set up.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
This has been done, but like I previously said it take 30-40min for
the time to get replicate across the network.
"Meinolf Weber" wrote:
Hello ketz,
Did you change back the configuration like Coraleigh mentioned? You
have
to configure in the domain only the PDCEmulator for the external time
source.
And do you have additional errors in the eventviewer?
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
Can anyone please help.
Thanks
"ketz" wrote:
sp2.
"Meinolf Weber" wrote:
Hello ketz,
Which SP do you run?
http://support.microsoft.com/kb/830092
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties,
and
confers
no rights.
Hi Meinolf,
Thanks for the quick reply.
This does work. thank you. but i still get the:
Source: W32time
Event Id: 50
The time service detected a time difference of greater than 0
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.
"Meinolf Weber" wrote:
Hello ketz,
Check out this one and also look at the right pane from the
article>
http://technet2.microsoft.com/windowsserver/en/library/fcc66e8b-
58 d9- 41c9-83ee-56d07397e3e01033.mspx?mfr=true
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties,
and
confers
no rights.
Thanks for your quick reply.
I have basically configured window time sync on each server to
point to an external source. The reason why I did this was
because each server takes over 20-30min to get an update time
from the domain controller. Is there a way for the servers to
get an update every 60 secs.
Thanks you
"Coraleigh Miller" wrote:
Hi Ketz,
Im not sure exactly how your time service is config'd so i'll
share with you the simple proper way to do it, for you to
check against your setup...
Only have your PDC emmulator server sync to an external time
server.
All of
your other (post 2000) windows servers and workstations should
not
be
adjusted; upon joining the domain they automatically point to
the
PDCe for
time. If they have been changed, an easy way to fix them is
to
run
a
net time /setsntp:
at a command prompt, which should put the registry value of
nt5ds
back into
the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\P
ar
ame
te
rs
key.
On the PDCe you can simply set the external time server by
running
a
net time /setsntp:[your chosen time server goes here]
Once you have done this restart your windows time service and
then
run a
w32tm /resync /rediscover
command on your PDCe.
Then check if you have any errors.
Here is a list of time servers you can use...
http://support.microsoft.com/kb/262680
Coraleigh Miller
"ketz" <ketz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:11C429F5-749C-4B59-993F-FBC895757608@xxxxxxxxxxxxxxxx
Hi All,
I am getting the below error on all servers that are
configured
with
windows
time sync. I have configured with a external time source
using
NTP.
I fix
a
hotfix on the microsoft website regarding this problem, but
was
applying
it
does not work...I am so stuff on this problem. I have so
many
event log
entries for this problem. Is there a way stop it producing
event
logs.
Please Help...Thank you very much.....
Source: W32time
Event Id: 50
The time service detected a time difference of greater than 0
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.
.
- References:
- Re: Windows Server 2003 Windows Time Sync
- From: ketz
- Re: Windows Server 2003 Windows Time Sync
- Prev by Date: Re: Server shutdown task
- Next by Date: domain controller prevent failure?
- Previous by thread: Re: Windows Server 2003 Windows Time Sync
- Next by thread: Re: IIS6 installation
- Index(es):
Relevant Pages
|
Loading
