The error is, alas, precise - we have attempted, and been explicitly denied, access to the logs.
This can happen for the following reasons :
you're not in a domain (see below)
Splunkd service is running with Local System permissions
Splunkd is running as a domain account, but cannot do at least one of these:
log on as a service on the remote box
bypass the firewall on the remote box, specifically IPSEC challenges
use Remote Launch and Remote Activation DCOM rights
Profile System Performance and Access this Computer from the Network GPO rights
The RPC service is running, but DCOM and/or WMI services are not
Whew. That's a lot of reasons, and there can be even more edge cases. For testing, try a domain admin account for the splunkd service login to verify connectivity is possible, then go from there to improve security. See:
http://docs.splunk.com/Documentation/Splunk/5.0/Data/MonitorWMIdata
or
http://msdn.microsoft.com/en-us/library/aa394603%28VS.85%29.aspx
RE: Domains. If you are NOT in a domain, it is possible to have identically named accounts with exactly the same login name and password who are both Local Administrators on both machines work with WMI. The polling Splunkd needs to have this account as it's service login.
Note this will NOT work if either machine is actually in a domain; both must be stand alone.
... View more