RECOMMENDED: Click here to fix Windows errors and get the most out of your system performance
Error 0x800706ba “El server RPC no está disponible. (Excepción de HRESULT: 0x800706BA) ”puede ocurrir cuando se ejecutan scripts de PowerShell con una solicitud WMI. RPC se clasifica como protocolo X11 y está en el rango de puertos 6001 a 6032, de forma general 6007, que está bloqueado para este caso.
El código de error 0x800706BA indica que el servidor RPC (llamada a proceso remoto) no está disponible. Este problema se genera cuando el equipo client en Windows XP libera el objeto COM + remoto. Aproximadamente de 20 a 30 segundos luego de que el equipo cliente comparte el objeto COM + remoto, se cierran los puertos RPC utilizados por DCOM en el servidor. Si la conexión de red se desconecta inmediatamente luego de que el equipo cliente libera el objeto COM + remoto, los puertos RPC utilizados por DCOM en el servidor permanecen abiertos durante varias horas. Esto puede provocar el agotamiento de las conexiones. Las solicitudes futuras del equipo cliente al objeto COM + remoto fallan.
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 el servicio Firewall de Windows para permitir conexiones entrantes de gestión remota.
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.
Abra Configuración del equipo, abra Plantillas de gestión, abra la red, Conexiones de red, abra el Firewall de Windows y después abra el perfil o perfil de domain predeterminado, según el perfil que desee configurar.
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
