There are really two primary reasons you'd get an access denied message: 1. an invalid username / password combination 2. the user in question is valid but does not have access to use DCOM and/or the WMI namespace
You can see if it's the first or the second by trying a different command from your zenoss host: Code: winexe -U domain/user%password //hostname 'typeperf -q' If you get the access denied message again then we know we've got a username/password/authentication issue and we can focus on that. If you get something else then we can focus on the latter. We've done testing with 64-bit Vista & Windows Server 2008 here, and I've seen 64-bit Windows Server 2003 work fine at customer sites so this should just be an environmental issue in the end (the best kind to fix!). -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=29827#29827 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
