I like the concept of Zenoss, and it looks great, but so far it's been pretty 
buggy.

WMI connect error on clserver.uent.com: 1326: DOS code 0x0000052e

I have tried configuring the username/password multiple times.  Tried both 
Domain\Username  and just plain old username multiple times.  

I have another server, nearly identical, that's working fine using just plain 
old username.  However I had tried both ways dozens of times before it just 
started working all of a sudden.

server1  set up as username, run modeler, works fine.
server2  set up as username, run modeler, unknown username/password
server2  set up as domain\username, run modeler, doesn't complain about 
username/password, but give the above WMI connect error.
Just ran WBEMTest can connect using DOMAIN\username just fine.

As I'm typing this...the error just went away.  username is currently set to 
just plain old username, like server1.

If I run modeler on Server1, everything works fine.
If I now run modler on Server2:

WARNING         zen.zenwinmodeler       WMI Com error: ERROR_LOGON_FAILURE: 
Logon failure: unknown user name or bad password. (1326)

At the very top just underneath the header for Discover Devices, I see the 
following:
Failed to bind to uuid 4d9f4ab8-7d1c-11cf-861e-0020af6e7c57 - 
NT_STATUS_NET_WRITE_FAULT ERROR: dcom_create_object. 

Event logs on server2 are clean.

I also have the following recurring event on this system:

eventClass      /Perf/Memory
eventKey        MemUsage
summary         Unknown


Any ideas on what's going on?

Thanks.




-------------------- m2f --------------------

Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=25765#25765

-------------------- m2f --------------------



_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to