DCOM configuration problem

upstream_at_nospam.com
Date: 05/25/04 

Date: Tue, 25 May 2004 14:06:05 -0700

Hello,

I have a Windows client application written in VB 6 running on "Computer A"
that is creating a DCOM object on "Computer B". The DCOM object is an out-of-proc server (EXE) also
written in VB 6. The DCOM object instancing is set to SingleUse. We are also running Active Directory
using a domain. Both computers are on the domain and both users are domain admins.
"Computer A" is running Windows XP Professional and
"Computer B" is running Windows 2003 Server.

On "Computer A", I am logged in as "User A".
On "Computer B" running DCOMCNFG, the DCOM object has the following properties set:
  - Identity is This User set to to run under the account "User B".
  - Launch Permissions has custom "SYSTEM" and "User B" to allow launch
  - Access Permissions has custom "SYSTEM" and "User B" to allow access
  - Location is Run application on this computer

Now I run the Windows client application on "Computer A" and call:

CreateObject("MyDCOM.Object", "Computer B")

I get the error (70) Permission denied.

Since "User A" does not have launch and access permissions, this makes sense.
So I go to DCOMCNFG on "Computer B" and give "User A" launch and access permissions to my DCOM object.
Then I run the program again from "Computer A" and still the same error. I reboot "Computer B" and
try again, but still the same error.

The only way I can get it to work is if I add "User A" to Default Security and give that user
launch and access permissions to all DCOM objects on "Computer B". Then it works.

So my question is why can't I give "User A" launch and access permissions on the object level
instead of the machine level?

Please help.

Thank you,
George

Relevant Pages
Quantcast