DC servers not time syncing

[Scott]

Here is my small and simple environment. I have one
domain and two sites. One site is in NJ and the other
site is in NC. At both locations I have one server.
Each server is a DC. Now my problem is that I cannot
keep their time synchronized with each other. After one
day their times are off by one minute. After two days
their times are off by 2 minutes. Etc. etc. I have to
use the "net time" command on the remote site to get them
back together. How can I configure my remote server to
auto sync its time with the main server here?

 

[Thiago Zanolo Mainente - Jornal Regional]

I resolve a same problem with it, maybe works with you too...

Do the folowing: at one of the server, for example, server2:
net time /setsntp xxx.xxx.com
where xxx.xxx.com is the full qualified dns name of the other server,
(server1) so server1 will syncronize automactly with server1.

 

[ptwilliams]

That's not the best way of doing this! It's best to let w32time do all the
synchronising -just configure the PDCe to synchronise and leave everything
else run as is.

If one's losing time it probably cannot connect to the other. Ensure that
UDP123 is open (both ways) on the firewall.

Typing the following on the one that is supposed to get time from the other,
and posting the output here may help:

C:\>net stop w32time
C:\>w32tm /once /v
C:\>net start w32time


If it's losing time that quick, I'd think about the CMOS battery too.

If it's neither of these, please provide a little more info. on sites,
setup, firewalls, VPN, etc.


--

Paul Williams
_________________________________________
http://www.msresource.net


Join us in our new forums!
http://forums.msresource.net
_________________________________________


message I resolve a same problem with it, maybe works with you too...

Do the folowing: at one of the server, for example, server2:
net time /setsntp xxx.xxx.com
where xxx.xxx.com is the full qualified dns name of the other server,
(server1) so server1 will syncronize automactly with server1.

 

[Cary Shultz [A.D. MVP]]

Exactly,

Maybe just a bit more on this.

In Windows 2000 there is absolutely no need to include the 'net time'
section in a logon script. This is a WINNT concept. The way that things
are suppose to work is that the Domain Controller that holds the FSMO Role
of PDC Emulator ( aka PDCe ) is the time source ( okay, do not shoot
me...the 'external source' is the actual time source - or stratum one with
the PDCe being stratum two ) . All other Domain Controllers synch from the
PDCe. All member servers and work stations synch from the DC that
authenticated them.

I am assuming a single domain / tree / forest in this explanation.

HTH,

Cary