Re: Time Syncing Issues on Servers
- From: Meinolf Weber [MVP-DS] <meiweb(nospam)@gmx.de>
- Date: Thu, 30 Apr 2009 23:35:40 +0000 (UTC)
Hello Broonie,
See inline
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
Hi There,
Domain is 3 2003 DCs, functional level Server 2000 (don't ask why it;s
not been upgraded). Clients are a mix of XP and Vista.
You can change it to windows server 2003 without any problem if no older OS DC's are there.
I am having problems with the time syncing on my domain member
servers. I have set my PDC emulator to point to an external source and
that is working fine. I then set a group policy that forces the
clients and member servers to look to that PDC using the NTP method.
Let the default setting within the domain.
I understand the NT5DS method is the default domain one but it was that
method that was failing me so that's why i've forced the clients to
use NTP.
What errors did you have? You have to make sure that port 123 udp is opened on the firewalls if in use.
Now, the time seems to be syncing OK but when I do a "net
time /querysntp" on the 2003 servers it brings back "time.windows.com,
0x1" as the time source which is incorrect as that is the default MS
entry. I've done a result set of policy on the servers and they are
all picking up the time sync settings I configured in the policy.
By default you don't have to configure any GPO for time sync. The PDCEmulator is the time source in the domain and should be configured to an external time source, as you did. That's all. All other DC's sync with that one and member servers and workstations sync with one available DC automatic.
However, if I do a "w32tm /query /source" on my Vista machine (these
switches are not available on win 2003 servers version of w32tm) I get
my PDC returned, which is what I would expect. Further, if i do a "net
time /querysntp" on my PDC emulator i receve the correct external
source.
Domain internal you should only have one available DC, no external time servers.
All I can think is that "net time /querysntp" is not looking first in
the group policy "true" part of the registry and instead is going
straight to the persistent part of the registry.
I guess what I'm asking is should i trust group policy or net time?
So i would remove the GPO and run on the additional DC's, clients and member servers:
w32tm /config /syncfromflags:domhier /update
After that run:
net stop w32time
net start w32time
.
- Follow-Ups:
- Re: Time Syncing Issues on Servers
- From: Broonie
- Re: Time Syncing Issues on Servers
- References:
- Time Syncing Issues on Servers
- From: Broonie
- Time Syncing Issues on Servers
- Prev by Date: Re: Question about Win 2008 Server Core
- Next by Date: Re: Vbscript Mapped Drives
- Previous by thread: Time Syncing Issues on Servers
- Next by thread: Re: Time Syncing Issues on Servers
- Index(es):
Relevant Pages
|
