Replication failing due to time differences

  • Thread starter Thread starter Bbruce2k5
  • Start date Start date
B

Bbruce2k5

I have two AD DC's in two different sites, both are set to the same
exact time and date but when I use AD replication monitor I get errors
stating their is a time difference betwen the client and the server. I
use the net time command to synch the servers and what I noticed is
that replication will work for awhile then break again due to time
differences. I then skim through the replication monitor log and
notice that when the computer clock reaches to 11:59pm and then goes to
the next day, it will jump TWO days ahead instead of one. For example
if today is the 24th, once it hits midnight the date will skip to the
26th. Then later on it will report the time correctly as the 25th but
by then replication is already out of sync. Anyone have any ideas???
 
Both DCs in the same forest I presume?

Check the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters

key on both and determine whether the Type value reads "NT5DS" (this is
using the Windows Time model)

Under the Windows Time model, each DC should sync with the PDC on up to
the PDC of the forest. Make sure you dont have 3rd-party time utilities
fouling things up - make sure the Windows Time service is started, etc.
 
I have two AD DC's in two different sites, both are set to the same
exact time and date but when I use AD replication monitor I get errors
stating their is a time difference betwen the client and the server. I
use the net time command to synch the servers and what I noticed is
that replication will work for awhile then break again due to time
differences.
Click to expand...

Make sure you don't have any other time utilities running
OR perhaps your machine set to use an inaccurate HARDWARE
clock.

Make sure you haven't set the time zone or PM/AM incorrectly.
I then skim through the replication monitor log and
notice that when the computer clock reaches to 11:59pm and then goes to
the next day, it will jump TWO days ahead instead of one. For example
if today is the 24th, once it hits midnight the date will skip to the
26th. Then later on it will report the time correctly as the 25th but
by then replication is already out of sync. Anyone have any ideas???
Click to expand...

Make sure the PDC Emulator for the domain, and all other
domains in the forest is correct. The Root Forest domain
PDC Emulator is master clock for the forest, with each PDC
in other domain pulling time from the parent up to root, then
other DCs pulling from their own PDC emulator.
 
Everything is set correctly and none of our DC's are pointing to an
external clock. We do have a network issue with dropped packets
between our sites which our domain controllers are affected by.

Could this cause replication to fail entirely?
 
Replication uses by default RPC over TCP so the packets would
retransmit. Are both DCs on the same service pack? What's the build
(2k, 2k3)?
 
Hi

Your PDCe should use an external source to Sync the PDC clock
(time.windows.com).
The other Dcs in the domain should use the PDC as Time Master to the domain.

If you detected that your Dc is "jumping" one Day every time that reach to
the 23:59PM then you should look for any Time Software installed or Hardware
Problems (usually batteries, or motherboard probl).

To diagnose Replication Problems:

- Make sure that the Domain Name service (DNS) is correctly configured. A
correct DNS configuration is necessary to correct directory replication.
- Make sure that you can use the Ping.exe utility to "ping" the domain
controller by host name and IP address from its hub partner
- Make sure that computers in the branch can resolve names in the hub. For
example, "ping" server1.domain1.site1.forest.com
- Make sure that you can ping servers by their Globally Unique Identifiers
(GUIDs) as they are listed in the event logs. If you can successfully ping a
server by its host name, but not by its GUID, a DNS configuration problem
exists.
- Run the Dcdiag.exe utility. This utility runs a series of tests, with the
result of either "Passed" or "Failed". Make sure that all tests pass.

- View the Directory Service log of the Event Viewer on the branch with
which you experience problems. Investigate and resolve all errors.

- Verify correct site links by using the Repadmin.exe utility with the
/showreps switch

- Verify inbound connections by using the Repadmin.exe utility with the
/showconn switch

- View all the log files in the Winnt\Debug folder.
 
I ran dcdiag and everything checks out, the strangest thing is that the
last successful replication was at 4/25/06 at 01:03. Today is the 24th
and the time is set correctly so the problem with the clock skipping a
day ahead and then going back to normal is whats breaking replication.
I need to focus my attention here and no there is no time software on
the server and the bios clock seems to be ok. Any other causes? We do
drop a ton of packets between sites but this domain controller that has
the problem contains all the FSMO roles.
 
Hi
I ran dcdiag and everything checks out, the strangest thing is that the
last successful replication was at 4/25/06 at 01:03. Today is the 24th
and the time is set correctly so the problem with the clock skipping a
day ahead and then going back to normal is whats breaking replication.
I need to focus my attention here and no there is no time software on
the server and the bios clock seems to be ok. Any other causes? We do
drop a ton of packets between sites but this domain controller that has
the problem contains all the FSMO roles.
Click to expand...

check the vendor web site to see any related problems with your motherboard,
check for bios updates.
 
Sounds like a Hardware problem. Check web site for your motherboard and see
if you can find any bios updates to the related problem, or cotact your
motherboard vendor.


I Hop that helps

Best Regards
Systems Administrator
MCSA + Exchange
 
Back
Top