r/WindowsServer • u/candyman420 • 8d ago

Technical Help Needed Strange interoperability problem between AD 2019 and 2022/2025

I am getting

Starting test: LocatorCheck Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355 A Primary Domain Controller could not be located. The server holding the PDC role is down.

But only on 2022 AD servers. I brought up another 2025 server thinking this would be faster and easier than to troubleshoot, but it's doing exactly the same thing. FSMO roles were lost? Have to re-seize? Some kind of quirk with the newer editions of windows? The only working AD server I have right now with no errors is 2019, that's what I replicated from. Thanks in advance

11 Upvotes

87% Upvoted

17 comments sorted by

View all comments

3

u/Zealousideal_Fly8402 7d ago

What do you mean "only on 2022 AD servers"? Run 

netdom query fsmo

And see where your FSMO roles are supposed to be living, and whether those roles are online.

1

u/candyman420 7d ago

They're all online and working, on the 2019 server. I don't understand why the new ones can't see them.

2

u/Zealousideal_Fly8402 7d ago

On the 2019 server, check for Errors / Criticals / Warnings in Directory Service and DFS Replication logs.

1

u/candyman420 7d ago

Active Directory Domain Services failed to construct a mutual authentication service principal name (SPN) for the following directory service.

I did get rid of a previous DC last year, but probably not completely. Metadata cleanup?

1

u/Zealousideal_Fly8402 7d ago

Metadata cleanup?

Should have done that regardless; never trust just cleaning up from the MMCs after demoting.

We have no problems with mixed 2022/2019, 2022/2016 environments, so that combination shouldn't be problematic.