Hi, all ... I've been unable to connect via WMI to any of our Windows servers. They're all VMs, running 2008R2. I've gone through all of the postings and guides I can find here on the site, with no luck.
My desired end-state is not to have to use a userid with admin rights, but just to spiral in and get it working, i've added a user with domain level administrator rights. I avoided any special characters in the password, and I know the password I'm using is correct, because I can RDP into the server I'm attempting to access using those credentials. But no form of wmic command is successful (various quoting, using \\ instead of /, using full domain name in place of shortname, etc.).
On the Zenoss box, I always get the following errors:
[librpc/rpc/dcerpc_util.c:1290:dcerpc_pipe_auth_recv()] Failed to bind to uuid 4d9f4ab8-7d1c-11cf-861e-0020af6e7c57 - 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
On the Windows side, I always see a "bad userid or password" error - even though I'm using the exact same userid/password as used for an interactive login over RDP, e.g.
We're operating in a secured environment, and in the past, have run into problems with e.g. LDAP calls failing, because of the GPO settings that require certain things of any processes attempting to connect ... is there anything that anyone's encountered at the network connection level that could be in play?
On the other hand -- by doing this several times in a row, the account I'm trying to use does in fact get locked -- which might argue that the connection isn't being completely denied, since it's clearly getting to the point of passing the credentials over the connection.
To eliminate something with the domain being involved, I created an account local to the Windows server, with local administrator rights -- same behavior.
I'm assuming it's not something to do with DCOM permissions or such - since the error doesn't seem to target that.
So ... assuming that I'm correct, and that I'm not simply messing up the password (which again, I'm using on that same server to login via RDP at the exact same time) ... is there anything else anyone is aware of that can cause a "bad userid or password" error on the windows side?
Any other thoughts?
thx!