RE: Domain Time Sync'ing
- From: Brian Edwards <BrianEdwards@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 11 Oct 2007 08:06:04 -0700
Thank you Mark.
Yes, the Windows Time service is started on the PDC Emulator.
Yes, I have tried those commands with a few different 2nd level public NTP
servers. The PDC Emulator is in sync with them. The clients remain off by
various amounts, some as much as 10 minutes. I've verified that port 123 is
open on our ISA server; the server commands below do not error out. When I
run "w32tm /resync" on the server I want to be the time server, the PDC
Emulator, the results are "The command completed successfully". When I run
"w32tm /resync" on the clients, after running the client commands below, the
result is always "The computer did not resync because no time data was
available".
Any thoughts as to what to try next? I am at a total loss.
Thank you again.
"Mark" wrote:
First, is the Windows Time Service started on the server that the clients.
will be httting? Next, have you tried this?:
To configure the Windows Time service on the PDC emulator
1. Open a Command Prompt.
2. Type the following command to display the time difference between the
local computer and a target computer, and then press ENTER:
w32tm /stripchart /computer:target /samples:n/dataonly
Value Definition
target
Specifies the DNS name or IP address of the NTP server that you are
comparing the local computer's time against, such as time.windows.com.
n
Specifies the number of time samples that will be returned from the target
computer to test basic NTP communication.
3. Open UDP port 123 for outgoing traffic if needed.
4. Open UDP port 123 (or a different port you have selected) for incoming
NTP traffic.
5. Type the following command to configure the PDC emulator and then press
ENTER:
w32tm /config /manualpeerlist:peers /syncfromflags:manual /reliable:yes
/update
where peers specifies the list of DNS names and/or IP addresses of the NTP
time source that the PDC emulator synchronizes from. For example, you can
specify time.windows.com. When specifying multiple peers, use a space as the
delimiter and enclose them in quotation marks.
=====================================
To configure a client computer for automatic domain time synchronization
1. Open a Command Prompt.
2. Type the following command and then press ENTER:
w32tm /config /syncfromflags:domhier /update
3. Type the following command and then press ENTER:
net stop w32time
4. Type the following command and then press ENTER:
net start w32time
=======================================
"Brian Edwards" wrote:
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.
- References:
- RE: Domain Time Sync'ing
- From: Mark
- RE: Domain Time Sync'ing
- Prev by Date: Re: Copying AD accounts to another AD domain
- Next by Date: Re: Domain Time Sync'ing
- Previous by thread: RE: Domain Time Sync'ing
- Next by thread: Re: Domain Time Sync'ing
- Index(es):
Relevant Pages
|
