Active Directory (AD) replication & Ports used in replication
Active Directory (AD) replication ensures consistency of AD data across all Domain Controllers (DCs) within a forest by synchronizing changes made on one DC to all others. It's a vital process for maintaining network integrity and preventing conflicting information.
To check the status of AD replication, you can use tools
like repadmin in a command prompt or specialized monitoring tools like Azure
Log Analytics. These tools help identify replication failures, which can stem
from various issues like network connectivity problems, DNS issues, or resource
constraints.
Here's a more detailed look:
What is AD Replication?
- Data
Consistency:
Replication ensures that all DCs have an up-to-date copy of AD data, so changes made on one DC are reflected on all others. - Forest-Wide
Synchronization:
It maintains consistency across the entire AD forest, which is a collection of one or more domains. - Automated
Process:
AD automatically handles replication based on the topology and site configurations. - Replication
Partners:
Each DC has replication partners, and changes are propagated between them.
How to Check Replication Status:
- repadmin command:
repadmin /replsummary: Provides a high-level overview of replication health across the entire forest or a specific domain. It highlights the "Largest Delta" (time since last sync) and any failure counts.
repadmin /showrepl: Displays detailed inbound replication status for each naming context (partition) on a specific DC. Use repadmin /showrepl * to see status for all DCs in the forest.
repadmin /syncall: Synchronizes a specific DC with all its replication partners.
- Azure
Log Analytics:
Azure Log Analytics monitors replication for failures and reports on the status of replication. - Third-party
tools:
Tools like those offered by Netwrix and ENow Software provide monitoring capabilities.
Potential Replication Issues and Solutions:
- Network
Connectivity:
Problems with network connectivity can prevent DCs from communicating and replicating data.
- DNS
Issues:
Incorrect DNS records can lead to replication failures as DCs can't find each other.
- Time
Synchronization:
If DCs are not synchronized with a common time source, replication may fail or be delayed.
- Replication
Topology Issues:
Improper site configurations can lead to slow or failed replication.
- Resource
Constraints:
Insufficient resources on DCs (CPU, memory) can impact replication performance.
- Security
Permissions:
Incorrect permissions can prevent a DC from replicating data to its partners.
- Event
Logs:
Reviewing the Event Logs on DCs for errors related to replication can help diagnose issues.
By regularly monitoring and troubleshooting AD replication, you can maintain a healthy and consistent AD environment, ensuring the smooth operation of your network.
The default Active Directory (AD) replication interval is
180 minutes (3 hours) for inter-site replication. For intra-site replication,
changes are replicated to the closest replication partner every 15 seconds
Repadmin.exe is a command-line tool used by administrators
to monitor, diagnose, and troubleshoot Active Directory (AD)
replication. It allows you to check replication health, force updates
between domain controllers (DCs), and view the internal replication topology.
Core Commands for Monitoring & Health
· repadmin
/replsummary: Provides a high-level overview of replication health across
the entire forest or a specific domain. It highlights the "Largest
Delta" (time since last sync) and any failure counts.
· repadmin
/showrepl: Displays detailed inbound replication status for each naming
context (partition) on a specific DC. Use repadmin /showrepl * to see
status for all DCs in the forest.
· repadmin
/queue: Lists any inbound replication requests waiting to be processed. In
a healthy environment, this queue should ideally be zero.
· repadmin
/showobjmeta <ObjectDN>: Shows replication metadata for a specific AD
object, including its version number and when it was last modified.
Commands to Force Replication:
- repadmin
/syncall: Synchronizes a specific DC with all its replication
partners.
- Force
Forest-wide Sync: repadmin /syncall /AdeP (Synchronize All
partitions, across the enterprise, and Push
changes outward).
- repadmin
/replicate <DestDC> <SourceDC> <PartitionDN>:
Manually triggers the replication of a specific partition from one source
DC to a destination DC.
- repadmin
/kcc: Forces the Knowledge Consistency Checker (KCC) to
immediately recalculate the inbound replication topology for a DC.
Specialized Utility Commands
|
Command |
Description |
|
repadmin /showutdvec |
Displays the highest committed Update Sequence Number
(USN) for a DC and its transitive partners. |
|
repadmin /removelingeringobjects |
Removes objects that were deleted on other DCs but remain
on the target DC beyond the tombstone lifetime. |
|
repadmin /bind |
Tests the ability of a DC to respond to replication
requests. |
|
repadmin /experthelp |
Displays advanced commands intended for expert users. |
Ports used in replication
Active Directory replication utilizes several ports for
communication between domain controllers. Key ports include TCP 135 for RPC,
TCP/UDP 389 for LDAP, TCP/UDP 53 for DNS, and TCP/UDP 88 for Kerberos.
Additionally, dynamic ports (49152-65535 on Windows Server 2008 and above) are
used for RPC endpoint mapper communication.
Here's a breakdown of the ports used for Active Directory
replication:
- TCP
135:
This port is used by the Remote Procedure Call (RPC) service, which is essential for mapping dynamic ports for replication traffic.
- TCP/UDP
389:
This is the port for Lightweight Directory Access Protocol (LDAP), which is used for directory access and replication.
- TCP/UDP
53:
This port is used by the Domain Name System (DNS) for resolving domain names and locating domain controllers.
- TCP/UDP
88:
This port is used by the Kerberos protocol, which is a network authentication protocol used by Active Directory.
- TCP
3268:
This port is used for Global Catalog LDAP, which allows for searching across multiple domains.
- TCP
3269:
This port is used for Global Catalog LDAP over SSL.
- TCP/UDP
445:
This port is used for Server Message Block (SMB), which is used for file and printer sharing and can be involved in replication processes.
- Dynamic
Ports (49152-65535):
After Windows Server 2008, these dynamic ports are used by RPC for communication.
These ports need to be open and properly configured in firewalls to allow for successful Active Directory replication

Comments
Post a Comment