WMI The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)

My application requirement is like below. Application will run on domain admin system which will ping all machine under that domain, it will take disk drive, CPU and RAM details from all domain systems.

Whenever I'm trying to ping machine I'm getting error that

"The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)"

Code I'm using to connect remote machine is

ConnectionOptions options = new ConnectionOptions();
options.EnablePrivileges = true;
options.Impersonation = ImpersonationLevel.Impersonate;
options.Username = System.Configuration.ConfigurationSettings.AppSettings["AccessUserName"].ToString();
options.Password = System.Configuration.ConfigurationSettings.AppSettings["AccessPassword"].ToString();
options.Authority = "ntlmdomain:" + System.Configuration.ConfigurationSettings.AppSettings["DomainName"].ToString();
options.Authentication = AuthenticationLevel.Packet;
ManagementScope scope = new ManagementScope("\\\\" + sMachineIP + "\\root\\cimv2", options);
scope.Connect();

I found the solution for this. I did it by enabling Windows Management Instrumentation (WMI) rule in Windows Firewall.

1. Open Windows Firewall.
2. Allow app or feature through Windows Firewall.
3. Enable Domain Privilege for Windows Management Instrumentation(WMI).

There are some other things also that you can check.

1. The remote computer is blocked by the firewall.
   Solution: 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. Open Computer Configuration, open Administrative Templates, open Network, open Network Connections, open Windows Firewall, and then open either Domain Profile or Standard Profile, depending on which profile you want to configure. Enable the following exception: Allow Remote Administration Exception and Allow File and Printer Sharing Exception.
2. Host name or IP address is wrong or the remote computer is shutdown.
   Solution: Verify correct host name or IP address.
3. The "TCP/IP NetBIOS Helper" service isn't running.
   Solution: Verity that "TCP/IP NetBIOS Helper" is running and set to auto start after restart.
4. The "Remote Procedure Call (RPC)" service is not running on the remote computer.
   Solution: Open services.msc using Windows Run. In Windows Services, Verify that Remote Procedure Call (RPC) is running and set to auto start after restart.
5. The "Windows Management Instrumentation" service is not running on the remote computer.
   Solution: Open services.msc using Windows Run. Verity that Windows Management Instrumentation service is running and set to auto start after restart.