Return
-
Title
Check connection fails on Windows Asset error: "The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)" -
Description
When Checking the connection on a Windows Asset in Safeguard, a GetComputerName function is run against the Windows Asset to verify its NetBIOS name using RPC / WMI.
When this process fails due to a firewall blocking the connection, Safeguard will show the error below:
Warning Caught COM Exception System.Runtime.InteropServices.COMException (0x800706BA): The RPC server is unavailable. (Exception from HRESULT: 0x800706BA) -
Cause
Firewall is blocking WMI traffic to the target Windows Asset -
Resolution
Configure the system's firewall to allow the following predefined incoming rules:- Windows Management Instrumentation (DCOM-In)- Windows Management Instrumentation (WMI-In)- NetLogon Service (NP-In)WMI / RPC uses TCP port 135 to initiate the communication to the target. The subsequent conversation then continues on a random negotiated port. On Windows 7 / 2008 and above, ports can range between: 49152 - 65535.
To limit the ports that can be used by WMI/DCOM refer to the following Microsoft KB, How to configure RPC dynamic port allocation to work with firewalls. Or the following Microsoft MSDN document: Setting Up a Fixed Port for WMI.