Frequently Asked Questions

This rare error is usually a firewall issue. If you're running with the inbuilt (MS) software firewall, make sure you've enabled the remote eventlog administration exception either via the UI or via (elevated) command line:

netsh firewall set service RemoteAdmin

or

Netsh advfirewall firewall set rule group=”Windows Firewall Remote Management” new enable =yes

If you have a hardware firewall to configure, then the process can be made much simpler by constraining DCOM to a smaller, specific range of ports of your choosing and opening them along with 135 (which always seems to be required). This takes a registry edit on all sides of the connection; consult the Help under the section "Other firewalls" for the procedure here, or the following article also covers it:

http://logmeister.com/support/kb/faq.php?id=5

Finally please make sure the Remote Registry service is running and set to start automatically.