Re: Time sync issue
- From: "Frankster" <Frank@xxxxxxxxxxxxxx>
- Date: Wed, 15 Nov 2006 07:54:21 -0700
I don't know if my reply will help or not, you probably know most/all of
this, but, just in case...
First, Net time /set has nothing to do with the built-in automatic SNTP time
synch of W2k, XP, and W2k3 machines. Net time /set is a legacy NETBIOS
command that should be unnecessary and does not use the w32tm.exe new(er)
SNTP protocol. It simply "sets" the time to match whatever NETBIOS machine
you point it to.
Next, with all W2K and above boxes, on a domain, you should not have to do
anything at all for proper time sync. It is built-in and on by default. Each
domain member automatically syncs to the DC holding the FSMO role (including
other DCs).
Next, only the DC holding the FSMO role normally should be set to obtain its
time sync from an external source. One typical source is time.windows.com.
Another is time.nist.gov. There are tons. The way you would do this is...
Go to the FSMO DC, open a command line and type: net time
/setsntp:time.nist.gov [enter]. That's it! Nothing else is required. This
will hold through reboots. Everything else should take care of itself (in a
domain). Workgroup stuff is a little different.
Anyway, here are some important things to guard against that will screw up
this automatic syncing.
- Do not set any of the boxes to any external or internal source manually
using the above technique. Only the FSMO DC.
-Do not incorporate a "net time /set \\pcname" line into any of your logon
scripts (this is the legacy command and has no real place in an enterprise
domain environment.
- Ensure that each domain member is not set to a specific time source by
going to each box and typing Net time /querysntp. You should get the
following response:
-----------------
U:\>net time /querysntp
This computer is not currently configured to use a specific SNTP server.
The command completed successfully.
----------------
This is the NORMAL repsonse. This means that this domain member computer is
automically syncing to the DC.
If you get a response showing that your domain member boxes are syncing to a
specified source, delete it thusly: net time /setsntp: [enter]. Rerun the
previous command to ensure they are not set to sync specifically with any
box.
-Frank
"Aaron" <Aaron@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BF892412-AF4C-4553-8E1E-EAA11E7E2002@xxxxxxxxxxxxxxxx
I have 3 DC's, 2 are server 2003 and one is a 2000 box. The 2000 box's time
is slowly moving ahead of the the 2003 servers. All clients on our domain
are
getting time from the 2000 box which is causing issues after about a week.
I have checked all of our GPO's to see if the Windows time setting has
been
set to point to the 2000 server and nothing is there. However even after
applying a GPO to point to one of the 03 servers when you run a net time
/set
on a client it still points to the 2000 box. I am not sure what else to
look
for. I have checked some registry settings on the 2000 box
HKLM/SYSTEM/CURRENTCONTROLSET/W32TIME/PARMS and found nothing conclusive.
Any
help muchy appreciated.
.
- Follow-Ups:
- Re: Time sync issue
- From: Aaron
- Re: Time sync issue
- Prev by Date: Re: Hijacked mail server?
- Next by Date: Re: files not in alpha order
- Previous by thread: Network scanning on HP 9130
- Next by thread: Re: Time sync issue
- Index(es):
Relevant Pages
|
