DCOM problem within a Samba controlled domain

[Michael Keightley]

We have been having problems with NT DCOM client and server when the NT
machines are in a Samba domain (Samba-2.2.1a).  Below is an explanation of the
problem one of devlelopers is having:
Anyone got any ideas?

  Problem Overview:
  DCOM client and server running on different NT4 workstations within the same
  SAMBA controlled domain. The client can launch the server, create an object
  within the server and obtain an interface to the object (using
  CoCreateInstanceEx), but the first method call on the interface generates an
  HRESULT of 0x80070005 (E_ACCESSDENIED). When run under the debugger, the
  debugger shows that the method body is not entered, so it appears to be some
  access problem with the actual method call.

  When client and server are run on a similar setup within an NT server
  controlled domain the method call succeeds.

  More Details:
  The DCOM server is running as a system service which runs within the
  System Account context.
  The DCOM server has no programmatically set security.
  The DCOM server's security permissions (as set within DCOMCnfg) are:
  Authentication Level: none 
  Impersonation Level: Identity (though same problem when set as any of
  other levels)
  Access Permissions: Allow Access for "Domain Users" and "Everyone"  

-- 
Michael Keightley <Michael.Keightley at quadstone.com>    Tel: +44 131 220 4491
Systems Manager,  Quadstone Limited,                   Fax: +44 131 220 4492
16 Chester Street,  Edinburgh EH3 7RA,  Scotland       http://www.quadstone.com