AD RPC Troubleshooting RPC error Article 2

When you perform any of the following server-based tasks, you might receive an error that says the RPC server is unavailable: here

  • Replication
  • Winlogon
  • Enable trusted relationships
  • Connect to domain controllers
  • Connect to trusted domains
  • User authentication

The “RPC server unavailable” error can occur for the following reasons:

  • DNS problems
  • Time synchronization problem
  • RPC service is not running
  • Network connectivity problem

Review some typical issues and solutions for the “RPC server is unavailable” error:

  1. The remote computer may be blocked by the firewall.

Solution: Configure firewall properly.

NOTE. If you are using WIndows firewall, open the Group Policy Object Editor snap-in (gpedit.msc) to edit the Group Policy object (GPO) that is used to manage Windows Firewall settings in your organization.
Navigate to Computer Configuration – Administrative Templates – Network – Network Connections – Windows Firewall, and then open either Domain Profile or Standard Profile, depending on which profile you are using.
Enable the following exceptions: Allow Remote Administration Exception and Allow File and Printer Sharing Exception.

  1. Hostname or IP address is wrong or the remote computer is shutdown.

Solution: Make sure that hostname and IP address. are correct, make sure the machine is turned on and reachable. Also make sure FQDN name is resolved to correct IP address.

  1. The Windows Management Instrumentation service is not running on the remote computer.

Solution: Verify that the Windows Management Instrumentation serviceis running and set to auto start after restart. 

  1. The TCP/IP NetBIOS Helper service is not running.

Solution: Verify that TCP/IP NetBIOS Helper service is running and set to auto start after restart.

  1. The Remote Procedure Call (RPC) service is not running on the remote computer.

Solution: Verify that Remote Procedure Call (RPC) service is running and set to auto start after restart.