Share via

PDC crashed

ramin sa 261 Reputation points
2021-03-10T10:46:06.36+00:00

Hi dear expert

we have DC1 with FSMO and DC2

On DC1 we can not login and when trying to login to DC1 with domain administrator we get below error

"there are currently no logon servers available to service the logon request"
so please give me hand to recover our DC1 with all FSMO

Thank you in advance

Windows for business | Windows Client for IT Pros | Directory services | Active Directory
0 comments No comments

Answer accepted by question author

ramin sa 261 Reputation points
2021-03-13T04:53:01.533+00:00

Thank you dear expert

we fix our issue by change Administrator account in DC2 and Login to our Crashed DC1

Then change boot mod

after do above step DC1 back to work

Was this answer helpful?

0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Anonymous
    2021-03-11T03:47:30.83+00:00

    Hello @ramin sa ,

    Thank you for posting here.

    Hope the information provided by DSPatrick is helpful.

    And we can also try to troubleshoot and try to fix the PDC as below.

    1.If your PDC physical machine or virtual machine? If it is a physical machine, please check whether the network cable is plugged in well.

    2.Check if you can RDP to PDC? If so, you can RDP to PDC and check:

    2-1 DNS setting, if the Preferred DNS is correct DNS server.
    2-2 KDC service is running or not.
    2-3 Netlogon service is running or not.

    3.Boot to DSRM of PDC and check 2-1 to 2-3.

    Hope the information above is helpful.

    If it does not work above, would you please tell us if you make any changes before the issue occurs?

    Should you have any question or concern, please feel free to let us know.

    Best Regards,
    Daisy Zhou

    Was this answer helpful?

    0 comments No comments

  2. Anonymous
    2021-03-10T13:27:15.93+00:00

    You can seize roles to other healthy domain controller.
    https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/transfer-or-seize-fsmo-roles-in-ad-ds

    then perform clean up
    https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup
    https://techcommunity.microsoft.com/t5/itops-talk-blog/step-by-step-manually-removing-a-domain-controller-server/ba-p/280564

    then rebuild the failed one
    I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new one, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health.

    --please don't forget to Accept as answer if the reply is helpful--

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.