Hello,
Please try the following steps:
Check the FSMO roles:
Ensure that all FSMO roles have been transferred correctly and that the new DC has assumed the role of PDC Emulator, as this role is responsible for handling password changes, account lockouts, etc.
Verify DNS settings:
Verify that the new DC's DNS settings are correct, including pointing to the correct DNS servers and having the correct reverse lookup zones.
Ensure that the new DC can resolve to other domain controllers via DNS.
Check the replication status:
Use the repadmin /replsummary command to check the replication status of AD DS.
If any problems are found, use repadmin /syncall to force an immediate synchronization.
Check the FRS/DFSR service:
Make sure the DFSR service is running and check its event log for error messages.
Check SYSVOL and NETLOGON share permissions:
Ensure that the SYSVOL and NETLOGON directories on the new DC have the correct NTFS permissions.
Check that both directories have been properly configured for sharing.
Check firewall settings:
Ensure that there are no firewall rules blocking necessary port communications such as RPC, LDAP, etc., which are critical for proper communication between domain controllers.
Check event logs:
Check the system logs and security logs on the new DC for reports of problems related to SYSVOL or NETLOGON.
Best Regards,
Hania Lian
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.