Ok, well it sounds like you do not have an active directory domain controller at this time and that seems to be the crux of the problem.
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello family.
I hope all is well, I have something with Windows Server I would like to configure it to have access to the Server Role to Activate the options required for the IIS. I can't when I open Windows Server > add other server to manage > Active Directory: "The local computer is either no domain-join, or it cannot access a domain controller".
I tried to change the domain by accessing System > change settings > Computer name -> change then in Member of i Select Domain and i Enter the domain This is the error i get when i submit "An Active Directory Domain Controller (AD DC) for the domain 'domain' couldn't be contacted".
I use the nltest /dsgetdc:domainname command to check the location of the domain controller, i get this in output: Getting DC name failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN
And ipconfig /registerdns to force host registration registration.
Its not working too.
Ok, well it sounds like you do not have an active directory domain controller at this time and that seems to be the crux of the problem.
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
Thank you David.
I happen to be new to this system. If you don't mind, I would like you to develop a little about the PDC emulator, such as how to run the PDC emulator?
Something here could help. (same basic steps for Server 2019 or 2022)
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
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:\problemwmember.txt
(run on problem one)
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.