Jul 29 2023 05:40 AM
Dear Support Team,
Our Active Directory (AD) server is currently experiencing replication issues with the corporate AD server. Upon reviewing the logs, I noticed an issue that I believe requires support assistance. I've already attempted to ping and perform port queries (TCP and UDP) to the Corporate AD, and everything seems to be working fine from our end. However, it appears that from the corporate side, they can ping our server but are unable to perform a port query. I already open all the port from my AD server firewall but still not work
Please assist me in check this issue
The File Replication Service is having trouble enabling replication from APSGDCV01ADGC01 to ANVNHTADGC01 for e:\windows\sysvol\domain using the DNS name APSGDCV01ADGC01.xx.xx.xx.com. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name APSGDCV01ADGC01.xx.xx.xx.com from this computer.
[2] FRS is not running on APSGDCV01ADGC01.xx.xx.xx.com
[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
The DFS Replication service encountered an error communicating with partner APSGDCV01ADGC01 for replication group Domain System Volume.
Partner DNS address: APSGDCV01ADGC01.xx.xx.xx.com
Optional data if available:
Partner WINS Address: APSGDCV01ADGC01
Partner IP Address: xx.xx.xx.xx
The service will retry the connection periodically.
Additional Information:
Error: 1727 (The remote procedure call failed and did not execute.)
Connection ID: 7FCAD924-0F33-45B6-B962-2EFB0D6BF917
Replication Group ID: E288372E-C215-4598-AEB9-D49952F50CD1
Jul 29 2023 12:15 PM
Somethings amiss, what you posted indicated FRS and DFS Replication services running when it's either one or the other and never both. Please run;
`Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log (run on PDC emulator)
repadmin /showrepl >C:\repl.txt (run on **any** domain controller)
ipconfig /all > C:\%computername%.txt (run on **EVERY** domain controller)
ipconfig /all > C:\problemworkstation.txt (run on problem pc)
Also check the domain controller ***System*** and ***Replication*** (DFS or FRS) event logs for errors since last boot. Post the ***Event Source*** and ***Event IDs*** of any found. (no evtx files)
then put `unzipped` text files up on OneDrive and share a link.
Jul 31 2023 12:20 PM
@Phu_Tran just checking if there's any progress or updates? please don't forget to mark helpful replies.