The post on the list serve that I found this on said they thought it was related to VMWare not being able to query the nested domain group's members, that you had to add the individual IDs from that domain group individualy into the local mqm group. They weren't 100% sure though.
Yes, I think this is a known problem - that MQ can't go via AD groups to identify users. Does this apply to vmware only and is there a solution to it?
The user(s) we're trying with are added directly to the local mqm group.
Joined: 28 Sep 2007 Posts: 1 Location: Birmingham, UK
Hi, I have a similar problem with V5.3 on W2K3. I have tried all the things mentioned but I am still unable connect to the QMs when logged in as a domain account. One thing to add is that I have logged in with another account from a trusted domain (i.e. not the domain the server is a member of) and this works OK. Problem only seems to occur when logged in using a domain account that is in the same domain as the server.
you either add the domain user explicitly to an authorized group on the MQServer(non domain service account) or allow the domain service account to query for domain membership and domain group membership....
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum