The RPC Server is unavailable on one of my Domain Controllers

Question

Dear Support,

I am having this error on Domain Controller that says "RPC Server is Unavailable".

Kindly help me to resolve it.

Answer 1

Since the problem is on a single domain controller the simplest solution may be to stand up a new one for replacement.

I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2012, 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, when all is good you can decommission / demote old one.

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

Answer 2

Hi,

Thank you very much for your reply.

Common causes of RPC errors include:

• Errors resolving a DNS or NetBIOS name.
• The RPC service or related services may not be running.
• number of connectivity Problems with network connectivity.
• File and printer sharing is not enabled.

For better understand your issue, could you please help to confirm the following information:

1. When did this error occurred? It was occurred when opened Group Policy Management Console?
2. How many DCs in your environment? May I know whether this error occurred on all DCs or occurred on the specific DC only ?
3. Please kindly follow DSPatrick's suggestion to see if the issue can be resolved.

Best Regards,
Sunny

----------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Hi,

I just ran it on the affected domian controller and following is the result after running the dcdiag.

Answer 4

The simplest solution may be to decommission the problematic one, stand up a new one for replacement.

I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2012, 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, when all is good you can decommission / demote old one.

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