Nagios Support Forum

Theses settings are to allow the local user on the machine access. If you need to query WMI from multiple computers across the domain, then you would need to supply domain admin credentials. No other settings should need to be changed if your user is a a domain admin.

There must be a hangup somewhere then. The user is already part of the domain admin and admin groups but I still receive the previous error. Where else could the problem lie?

The individual servers don't have this user on them. The user is only on active directory.

Is this a 2008 domain controller or 2003 your authenticating against?

Here are the firewall settings needed to allow WMI traffic for server 2008:
http://msdn.microsoft.com/en-us/library ... s.85).aspx

also I would double check the DCOM remote activation permissions on the domain admin just to be certain.

If you have a windows machine to test from, try authentication with WMBMTEST

start > run > WBEMTEST

I'm not sure about the esx plugin yet. i'll keep researching what the issue might be.

cwscribner,

Just checking to see if this issue has been resolved for you. I noticed the firewall link I posted didn't appear correct in my last message.

Let's try again:
"http://msdn.microsoft.com/en-us/library ... s.85).aspx"

At any rate, Vmware can authenticate against Active Directory, but you must define the users from AD in VMware vsphere client. Once that's done, it look like you can just point to the VMware vsphere server with a valid u:p as defined in active directory. No need to access AD directly for authentication.

Let us know if you have any other questions/issues.

As of right now, it's still open. I'm working with a tech at the client site to go through the troubleshooting methods in this thread.

Ugh...still no changes even after the recommended tests. The nagios user for WMI is confirmed as a domain and administrative user. The client's senior tech performed WMI queries with the Nagios user directly on the machines and returned data so the hangup is still at the logon portion of the wmi monitoring. Is it possible that the problem is in the plugins? Some misformed code or an accidental space at the end of the password? I'm at a loss for what the problem could be. Attached are screen shots the tech forwarded to me.

We're currently testing an updated version of the WMI wizard that will hopefully allow support for strong passwords for WMI. We'll post the results once we finish testing.

Oh happy day! We solved this issue!!!!!

http://support.nagios.com/forum/viewtop ... =16&t=4111

Glad to hear it's resolved! Specifying the domain is important