http://www.minasi.com/newsletters/nws0306.htm
Fixing Time Synchronization Problems
My XP desktop stopped synchronizing its time with the domain. The Event
Log kept showing that the desktop hadn't time-synced with any of my DCs
in weeks. That worried me because if my workstation's time drifted more
than five minutes from the domain controllers' time then I'd not be able
to log on. Once I was three minutes off, I figured it was time to figure
out what had happened.
I tried to re-synchronize from the command line:
w32tm /resync
And got "the computer did not resync because no time data was
available." Oooh, that doesn't look good. But then I realized that I'd
fixed my system's time server as an experiment rather than letting AD
set it. Some free time sync programs do that also, so many of you may be
in this position. I just cleared out
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters's
"NtpServer" value entry, and then I restarted the Windows Time Service.
Sadly, no dice ... still no sync. For some reason, if your domain
doesn't find all of the Registry entries to be "just right," then it
won't sync with your system. You can, thankfully, fix it with this command:
w32tm /config /syncfromflags:DOMHIER /update
Type that from a command line, and then restart Windows Time Service and
retry the w32tm /resync or, better,
w32tm /resync /rediscover
A command that cleans out and rebuilds a few other Registry entries. I
had that problem with my XP box about a year ago; since then I've found
these commands useful on a number of systems. When workstations get more
than five minutes out of sync with the DC, then they stop authenticating
but they're not very forthcoming about the reason -- so when
authentication's a problem then first look at DNS, and if that doesn't
help then look at time!
Rimmerman, Russ wrote:
I tried it, it says:
The computer did not resync because no time data was available
I followed http://support.microsoft.com/kb/929276 but it was already
set right….
Try the command...
w32tm /resync /rediscover
See if that helps the client figure out where it should look for time.
~Ben
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rimmerman, Russ
Sent: Wednesday, January 10, 2007 2:12 PM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] Client time sync
I have a machine (at least one I know of) that isn't syncing time with
the domain controller its logging into. I've restarted the win32time
service on it to see if that would sync it and it doesn't. Any
suggestions on where to start? The DC and the client are off by about 9
minutes.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This email message is for the sole use of the intended recipient(s)
and may contain confidential and privileged information of Cameron
and its Operating Divisions. Any unauthorized use or disclosure is
prohibited. If you are not the intended recipient, please contact
the sender by reply email and delete and destroy all copies of the
original message inclusive of any attachments.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
Letting your vendors set your risk analysis these days?
http://www.threatcode.com
If you are a SBSer and you don't subscribe to the SBS Blog... man ... I will
hunt you down...
http://blogs.technet.com/sbs
List info : http://www.activedir.org/List.aspx
List FAQ : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ma/default.aspx
