Local vs Domain Member Accounts for WMI
Posted: Mon Jun 04, 2018 3:55 pm
I tried, and failed to get WMI working with Nagios when using a domain member account. I find it odd that I had to use an account local to the WMI client server to authorize the WMI service. Both accounts, had the same permissions set for the test server. Both should have worked.
Is my expectation that an AD member account used to provide permissions to the WMI service for Nagios mistaken?
Thanks,
[librpc/rpc/dcerpc_util.c
dcerpc_pipe_auth_recv()] Failed to bind to uuid redacted - NT_STATUS_NET_WRITE_FAULT
[librpc/rpc/dcerpc_connect.c:790:dcerpc_pipe_connect_b_recv()] failed NT status (c0000022) in dcerpc_pipe_connect_b_recv
[wmi/wmic.c:196:main()] ERROR: Login to remote object.
NTSTATUS: NT_STATUS_ACCESS_DENIED - Access denied
Is my expectation that an AD member account used to provide permissions to the WMI service for Nagios mistaken?
Thanks,
[librpc/rpc/dcerpc_util.c
[librpc/rpc/dcerpc_connect.c:790:dcerpc_pipe_connect_b_recv()] failed NT status (c0000022) in dcerpc_pipe_connect_b_recv
[wmi/wmic.c:196:main()] ERROR: Login to remote object.
NTSTATUS: NT_STATUS_ACCESS_DENIED - Access denied