Re: Domain Time Sync'ing

Interesting.

One thing to note about your situation: if some of the machines can sync and
some cannot, then it seems reasonable that the problem is client-side. You
may want to start with the event logs on the clients that don't work.

Good luck,

Al

"Brian Edwards" <BrianEdwards@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:43D7789D-F8EF-4E50-B841-207ED47E8B4D@xxxxxxxxxxxxxxxx
Thanks again Al.


After more research, I came across
http://www.msfn.org/board/lofiversion/index.php/t67060.html. That solved
the
problem of why the server wasn't sync'ing with an outside source. It's
working fine now. There were settings in the Default Domain Controllers
Policy, which I was under the impression we no longer employed, fouling up
time sync'ing from the PDC to a public NTP server.

Now, some member servers and clients respond positively to the "w32tm
/resync /rediscover" command, while many others do not (no time data
available). I think I will wait until tomorrow morning to try them again
and
see if their time will sync to the PDC. No reason it shouldn't, afaik. I
checked that no GPOs were setting this policy for clients.

Thanks for the help guys, and if you have any further thoughts, I would
love
to hear them.

:)



"Al Mulnick" wrote:

I think the other advice you got was good advice, but just to be sure,
have
a look at the following:

http://technet2.microsoft.com/windowsserver/en/library/ce8890cf-ef46-4931-8e4a-2fc5b4ddb0471033.mspx?mfr=true

http://technet2.microsoft.com/windowsserver/en/library/a0fcd250-e5f7-41b3-b0e8-240f8236e2101033.mspx?mfr=true

Also, be sure your PDCe is at least 2003 SP1 or later. There were some
bugs
similar to what you describe prior to that.

Note that time is UDP and not TCP. You'll want to be sure that your time
is
correctly updating.
Just for curiousity, how do you allow your other devices to sync time?
Your
routers and such?

Last, let us know what you find.

"Brian Edwards" <BrianEdwards@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:04BED403-E132-4BD0-ABC9-C5AEAA4B5B72@xxxxxxxxxxxxxxxx
Thank you Al.

The System event log contains warnings averaging about twice per day,
event
ID 50:

"The time service detected a time difference of greater than 128
milliseconds for 90 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."

I'm not sure how to force the time service to attempt a sync with the
public
NTP source I configured when following the commands Mark suggested. I
did
stop/start the time service afterwards and no error was generated on
the
server, but clients still can't sync to the server.

Thoughts?

Thank you.



"Al Mulnick" wrote:

Event logs? What's in the event logs regarding w32time? usually,
after
startup of the service you'll see entries indicating that it's
successfully
sync'ing time. Or you'll see entries indicating that it is not. If
you
see
nothing, that's a different issue.

Can you check and let us know?




"Brian Edwards" <BrianEdwards@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:ABFC5862-FB79-4502-9932-4E58EC60B3FB@xxxxxxxxxxxxxxxx
1 domain, all Win2k3 servers
2 DC's, shared roles (1 has 4 of the 5 roles, the other has the
remaining
role)

We had our PDC crash two months ago. I was able to bring it back
online,
but only after a complete rebuild. Afterwards I cleaned up Active
Directory
and got all of the roles straightened out. Dcdiag reports all tests
pass
on
both DC's. However, we've been noticing client clocks out of sync
with
the
servers, which are in sync with each other.

Can someone please start from scratch and tell me what I need to do
to
get
the clients to sync with either of the DC's, which both state that
they
are
successfully advertising themselves as time servers? I've read KB's
and
posts all day long and have only gotten more and more confused.
It's
amazing
that something this simple requires more than a few clicks of a
mouse
to
get
working properly.

Feel free to bash me, and I will answer any questions you have.

TIA

PS - I've tried the "w32tm /config /syncfromflags:domhier /update"
then
stop/start net time on several different clients and although those
do
not
error out, the clocks are still off, even after reboots.









.

Relevant Pages

  • Problem with popen
    ... Under linux x86 I'm running a stress test which opens some tcp server ... applications and then about 70 clients in each their thread. ... The server however is started as an async process using fork and then ... sync and async processes. ...
    (comp.unix.programmer)
  • Re: forcing an nfs sync
    ... >I used the sync option in the /etc/exports file of the server, ... and clients still didn't see immediate changes in the file on ... >the server. ... >"sync" did not affect the overall throughput, ...
    (comp.protocols.nfs)
  • Remote Connection Issue/Question
    ... I have and SBS 2003 R2 Std server with several XP Pro clients. ... off-line/sync folder with a folder on the server. ... network then just sync the folder (either manually or by scheduling at the ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem
    ... branch office VPN that will tunnel the traffic or the clients in location B ... need to connect individually via VPN to the SBS server at location A. ... When I log in it says it can't sync the files to the domain so it will ... was in the old router which I had to reset. ...
    (microsoft.public.windows.server.sbs)
  • Re: Domain Time Syncing
    ... problem of why the server wasn't sync'ing with an outside source. ... some member servers and clients respond positively to the "w32tm ... how do you allow your other devices to sync time? ... "The time service detected a time difference of greater than 128 ...
    (microsoft.public.windows.server.active_directory)