RECOMMENDED: Click here to fix Windows errors and get the most out of your system performance
Error 0x800706ba “The RPC server is not available. (Exception from HRESULT: 0x800706BA)” can occur when running PowerShell scripts with a WMI request. RPC is classified as X11 protocol and is in the range of ports 6001 to 6032, generally 6007, which is blocked for this case.
Error code 0x800706BA indicates that the RPC (Remote Process Call) server is unavailable. This problem occurs when the client computer in Windows XP releases the remote COM+ object. Approximately 20 to 30 seconds after the client computer shares the remote COM+ object, the RPC ports used by DCOM on the server are closed. If the network connection is disconnected immediately after the client computer releases the remote COM+ object, the RPC ports used by DCOM on the server remain open for several hours. This can lead to connection exhaustion. Future requests from the client computer to the remote COM+ object fail.
You can test the RPC connectivity of the server you are on to another computer/server via the following command:
Get-WmiObject Win32_ComputerSystem –ComputerName OTHERSERVER
Viable cause of error 0x800706ba:
- This error is most likely caused by blocking of the RPC ports between the servers associated with the communication or server procedure you are attempting to complete.
- The RPC service is stopped on the remote server.
- Endpoint Mapper could not be entered on port 135 on the remote server.
Configure the Windows Firewall service to allow incoming remote management connections.
Open the Group Policy Object Editor (gpedit.msc) to change the Group Policy Object (GPO) that is used to manage Windows Firewall settings in your organization.
Open Computer Configuration, open Management Templates, open Network, Network Connections, open Windows Firewall, and then open Profile or Default Domain Profile, depending on which profile you want to configure.
Enable the following exceptions: “Allow exception for remote management” and “Allow exception for file and printer sharing”.
Check your firewall settings
To fix your problem, follow these steps:
Turn off the Windows Firewall service (or a third-party firewall) on the problem server.
OR
If you are using a third-party firewall, configure it to allow connections to the following TCP and UDP ports: 135, 445.
Modify the DCOM access group
There may be several solutions to this problem, but in most cases, the cause of the problem is that your computer is a member of the DCOM access group (DCOM Access to Certificate Service) or you are given the wrong authorization. Follow these steps:
In the controller domain where the certification service is provided, you must ensure that there is a domain group CERTSVC_DCOM_ACCESS or DCOM Access to Certificate Service;
Add the following domain groups to the CERTSVC_DCOM_ACCESS / Certificate Service DCOM Access group: Domain Users, Domain Controllers, Domain Computers;
Use the commands to update the DCOM security settings on the server with the CA role:
certutil -setreg SetupStatus -SETUP_DCOM_SECURITY_UPDATED_FLAG
net stop certsvc and net start certsvc
On a server with the CA provided, check the COM security permissions. Remote access and remote activation permissions must be allowed for this group.
Then try restarting the computer and verify that the certificate has been issued.
RECOMMENDED: Click here to fix Windows errors and get the most out of your system performance
