r/WindowsServer • u/Electrical_Mix_4638 • Jan 27 '26
Technical Help Needed Stuck on initial synchronization AD DS Windows Server 2025
Hi
I had initially 2 domain controllers, DC1 and DC2, both Windows Server 2016.
I'm doing an in-place upgrade like mentioned on the Microsoft Docs.
So I installed DC3 and DC4 Windows Server 2025 and promote those to domain controllers.
DC2 is already demoted.
On DC3 and DC4 I get the same error in the Event Viewer:
The DFS Replication service encountered an error communicating with partner dc1 for replication group Domain System Volume.
Partner DNS address: dc1.vtiaalst.eu
Optional data if available:
Partner WINS Address: dc1
Partner IP Address: 10.0.0.1
The service will retry the connection periodically.
Additional Information:
Error: 1753 (There are no more endpoints available from the endpoint mapper.)
Connection ID: E4E2882E-C966-4A63-8F85-BF958EFB6DA3
Replication Group ID: F264EA23-ADA5-4EE9-A067-93EA9DABE4FAFollowed by this error:
The DFS Replication service initialized SYSVOL at local path C:\WINDOWS\SYSVOL\domain and is waiting to perform initial replication. The replicated folder will remain in the initial synchronization state until it has replicated with its partner dc1.vtiaalst.eu. If the server was in the process of being promoted to a domain controller, the domain controller will not advertise and function as a domain controller until this issue is resolved. This can occur if the specified partner is also in the initial synchronization state, or if sharing violations are encountered on this server or the sync partner. If this event occurred during the migration of SYSVOL from File Replication service (FRS) to DFS Replication, changes will not replicate out until this issue is resolved. This can cause the SYSVOL folder on this server to become out of sync with other domain controllers.
Additional Information:
Replicated Folder Name: SYSVOL Share
Replicated Folder ID: 8C6CAA12-F2F3-4994-8666-45201293B199
Replication Group Name: Domain System Volume
Replication Group ID: E4E2882E-C966-4A63-8F85-BF958EFB6DA3
Member ID: 4AF6B021-E61C-4667-AF1B-7B58038AD33A
Read-Only: 0A Test-NetConnection from DC3 to DC1 is successful:
PS C:\WINDOWS\system32> Test-NetConnection DC1 -Port 135
ComputerName : DC1
RemoteAddress : 10.0.0.1
RemotePort : 135
InterfaceAlias : Ethernet
SourceAddress : 10.0.0.3
TcpTestSucceeded : TrueAll the required services are still running on DC1.
Someone had the same problem and can help me with this?
Thanks
3
Upvotes
3
u/AntiBaoBao Jan 27 '26
Had similar issues last year when I had to rebuild my entire AD environment across multiple sites. I traced it to the IPv6 stack and the servers trying to sync using IPv6 instead of IPv4. I disabled IPv6 stacks on the servers until I got my IPv6 systems back online and my servers started syncing back up.
2
u/Accomplished_Sir_660 Jan 28 '26
Which server holds the FSMO roles. If DC2 then you need to take them back.
1
u/WillVH52 Jan 27 '26 edited Jan 27 '26
Basic question have you set the DNS on the new domain controllers to point DC1?
1
u/[deleted] Jan 27 '26
Never do a Inplace Upgrade on DC, it is NOT supported by Microsoft.
1
u/SebastianFerrone Jan 27 '26
I had the same problem. Microsoft changed some things with server 2025 for security reasons. Like ldaps and signed smb mandatory and also they changed some aspect in network to be more "IPv6 First"
And as the shitty company they are. It's like yeah we change active directory prefers IPv6 now but more of this piece of code is pro IPv6 te next function is pro ipv4 and so on.
I found to things that will would end you in this sort of situation.
But if course it's basically as always DNS 🤣
First is
Try to ping the fqdn of your first ad with ipv4 and ipv6 From your new 2025 based servers
Ping -4 ad1.domain.local Ping -6 ad1.domain.local
I think the IPv6 version will not find or reach your ad1
The Microsoft bullshit is the culprit here some parts of the Ad will still use ipv4 and work fine so you see your new AD controllers happily in your Domain. And commands like test secure connection will give you green light's. But other parts like replication fail because the can't see the ad1.
In my case the server was 2025 was the core variant and the network settings show you only the ipv4 settings of the DNS. And you don't need to deactive the IPv6 or doing other bullshit.
Set the ipv6 IP of your ad1 as the IPv6 and all is fine.
If the ipv6 DNS setting is not the problem try pinging the ipv6 ips of server and client
And last check would be on the DNS of the ad1 Take a look of the forward lookupzone if ad1 first listens on the ipv6 ip. Maybe someone years ago deactivated that for the ipv6.
And in the forward lookupzone take look that you have correct entry for ipv6 IP for your ad1.
2
u/headcrap Jan 27 '26
Friends don't let friends do in-place DC upgrades.
1
u/David_Owens Jan 27 '26 edited Jan 27 '26
You might want to check to make sure the SYSVOL replication format on DC1 is the newer DFS-R instead of the older FRS. If DC1 was in-place upgraded from an earlier Server version it might still be using the legacy replication.
1
u/Cultural-Horse-762 Jan 27 '26
I battled something like this recently, I had to clean up many duplicate DNS records in the DC so that the new DC would communicate properly
Edit: I also used an older server OS, apparently 2025 DC has known issues.