Jul 30 2023 12:18 PM
Hello,
I have an environment with 3 DC's where I want to remove 1 DC. I manage to transfer all roles but whenever I disconnect the DC I want to remove I lose access to the AD and authentication starts to fail. If you use the netdom query fsmo command, the roles appear on the correct DCs, but if you run the nltest /dsgetdc:mydomain.local command, it points to the DC I want to remove, as well as if you run the command Get-ADDomainController -domainname edoc.local -Discover -Service PrimaryDC I start having errors if the PDC role is not on the DC I want to remove. I don't see any problems with the DNS Server.
It seems that the reference to the PDC is always pointing to the DC I want to remove.
Best regards,
Sérgio Raposo
Aug 05 2023 02:45 AM
@Dave Patrick I already did that and the roles are in the DC's to where i moved them and it seams that everything is alright. But every time i query the domain (ping -a <domain>) the IP that i receive is from the DC that i want the remove and when I use netdom query fsmo it point the PDC is the new server. Another thing is that when the roles are in the new server's if i shutdown the DC I want to remove i lost the Active Directory. To regain access again i have to start the old DC. I have done transfer the role without problem, i have seized the role but nothing worked.
Aug 05 2023 05:43 AM
if i shutdown the DC I want to remove i lost the Active Directory.
How are you verifying this? Might also check the DHCP server hands out the addresses of healthy domain controllers.
Aug 06 2023 09:40 AM
Aug 06 2023 12:40 PM
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.
Aug 06 2023 02:16 PM
Aug 07 2023 10:57 AM
Domain controllers should never have DHCP assigned ip addresses. Also appears there may be a rouge IPv6 DHCP server on the network (router?) with could be problematic.
Check the DFS Replication event logs on EDOCCOM2 for details as there seems to be errors. (the Event Source and Event IDs of any found)
Warning: DsGetDcName returned information for \\EDOCCOM2.EDOC.local, when we were trying to reach EDOCAD
Warning: DsGetDcName returned information for \\EDOCCOM2.EDOC.local, when we were trying to reach EDOCAD2.
could be related to DHCP addressing.
Are the sysvol / netlogon shares visible on all?
10.0.0.10 (EDOCCOM4) [Invalid (unreachable) renamed? or an old one?
The domain controller System and DFS Replication event logs should also guide you.
Aug 07 2023 11:43 AM
Aug 07 2023 02:41 PM
Only in the server that i want to disconnect i can see the share SYSVOL and NETLOGON. The other have the folder SYSVOL but aren´t shared.
The error that i found in EDOCCOM2 is the following:
The DFS Replication service failed to contact domain controller to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle
Ok, I think I finally get it now. Sounds like the single domain controller may not have been in a healthy state and then three more were added that is complicating the situation. If it were me, I'd probably get rid of the additional ones and work to bring health on the one to 100% then try again. It may be some or all do not get the domain network profile which blocks the required ports.
Aug 10 2023 12:54 PM