I did NOT upgrade from 2.3, but instead performed a fresh install. I've followed the docs and cannot get this to work.

I tried the wmic and it connected w/ the acct I'm trying to use in Zenoss. Zenoss does not.

If someone could followup to jason's post, he'll be able to
troubleshoot it a bit.

Thanks,
Matt Ray
Zenoss Community Manager
community.zenoss.com
mray@zenoss.com



On Dec 8, 2008, at 4:53 PM, ionut1985 wrote:

 

 

i have the same problem... did anyone find a fix for this yet?







_______________________________________________
zenoss-users mailing list
zenoss-users@zenoss.org
http://lists.zenoss.org/mailman/listinfo/zenoss-users

_______________________________________________
zenoss-users mailing list
zenoss-users@zenoss.org
http://lists.zenoss.org/mailman/listinfo/zenoss-users

anyone know anything about this yet?

I just wanted to let you guys know that this issue hasn't been dropped. We haven't been able to reproduce but we're still investigating.

-jason

I am experiencing issues that are close to this issue. I have created a fresh stack install of Zenoss and am experiencing random issues with getting the OS, Hardware, Software information to come in. Regardless on initial device model or re-model the items wont show.

I have checked snmp as well as wmi and the server is accepting connections and returning the correct data with the account that I have inserted into the wmiuser and wmiuserpassword fields.

This is not happened for every machine. Only about 1/2 and it seems that sometimes if after the initial load I can go into the zProperties of the machine in question and just click save it will model it correctly.

I hope I'm not jumping in too late, but in response to the query as to where this is happening - only my Exchange 2007 box is giving me the NT_STATUS_CONNECTION_REFUSED error. And as mentioned above, it's a Server 2003 R2 64 bit box. I'm attaching through WMI, and would prefer to not have to install a SNMP agent.

My server is Zenoss 2.3.2, Centos 5.2 (i386)

Cheers,

Eric

mdzen01:~# /usr/local/zenoss/common/bin/wmic -d 10 -U domain/user%password //2003server "select * from Win32_ComputerSystem"
Initialising global parameters
lp_load: refreshing parameters from /dev/null
params.c:pm_process() - Processing configuration file "/dev/null"
pm_process() returned Yes
adding hidden service IPC$
adding hidden service ADMIN$
failed to get principal from default ccache: No such file or directory: open(/tmp/krb5cc_0): No such file or directory
AUTH backend 'winbind_samba3' registered
AUTH backend 'winbind' registered
AUTH backend 'name_to_ntstatus' registered
AUTH backend 'fixed_challenge' registered
AUTH backend 'unix' registered
AUTH backend 'anonymous' registered
AUTH backend 'sam' registered
AUTH backend 'sam_ignoredomain' registered
GENSEC backend 'krb5' registered
gensec subsystem fake_gssapi_krb5 is disabled
GENSEC backend 'schannel' registered
GENSEC backend 'spnego' registered
gensec subsystem gssapi_spnego is disabled
GENSEC backend 'gssapi_krb5' registered
GENSEC backend 'gssapi_krb5_sasl' registered
GENSEC backend 'ntlmssp' registered
Using binding ncacn_ip_tcp:2003server
Mapped to DCERPC endpoint 135
rpc request data:
rpc fault: DCERPC_FAULT_ACCESS_DENIED
librpc/rpc/dcerpc.c:1089: dcerpc_request_recv status = NT_STATUS_ACCESS_DENIED
dcerpc_ndr_request_recv returned NT_STATUS_ACCESS_DENIED
ERROR: Login to remote object.
NTSTATUS: NT_STATUS_ACCESS_DENIED - Access denied


Hmm - maybe this will be of some assistance?

I added the user Zenoss to our Administrators group, and set the zWinUser to Domain\zenoss.

That resolved the issue on the Domain Controller, but the error is still showing up on the other servers in the Domain.