The RPC server is unavailable. 0x800706BA
Last updated on January 15 2013
Make sure that the target computer is not switched off.
Run the Lansweeper Connection tester.
Download the latest Connection tester from here.
Make sure you run it from the same machine as the Lansweeper Service, with the same credentials you use for scanning.
If port 135 is closed, check your firewall settings (see below)
Make sure that windows firewall isn't blocking the needed WMI ports.
This is the most common problem.
How to configure the windows firewall using group policies.
To force the group policy to apply you can use the "gpupdate /force" command.
To check the group policies on the client you can use the "gpresult" command.
If for some reason you can't apply group policies you can use the following commands to set the firewall. (save as firewall.cmd)
call netsh firewall set service RemoteAdmin enable
call netsh firewall add portopening protocol=tcp port=135 name=DCOM_TCP135
Make sure that no third party firewalls are blocking the needed ports.
Third party firewalls that are known to cause this problem in the default configuration are:
Nvidia : Forceware Intelligent Application Manager firewall.
Cisco vpn secureclient.
Symantec endpoint protection.
Make sure that the computer name in dns is pointing to the correct IP address.
Try "ping computer.domain.local" (fully qualified name of the computer)
Try "ping -a IPAddress"
Verify that these are correct.
Make sure the local time is correctly set on the client machine, the scanning machine and the domain controller.
A time difference greater than 15 minutes between client and server can cause unexpected results in active directory domains.