DCOM authentication problems

[yves puelings]

Launching a (local server) COM object on a remote system fails when XP
is involved, at least I know it is if the server runs on the XP
system. When setting the DCOMCNFG settings to launch as 'Interactive
user',setting security to full control for everyone and SYSTEM,setting
the connetion to TCP/IP and the authentication level to 'NONE', I
manage to start the application remotely on W2000 but not on an XP
system. In case of an XP system, it does launch the exe (e.g. Excel),
I can verify in the taskmngr on the remote system, but it does not
succeed in visualizing and returns an error 'Can't create ActiveX
object' to the client system. The System event log on the client
system shows a message 'DCOM received a "General access denied" error
from system ...'. When both users are logged in on the same domain, it
does work however, even on an XP host system. Any ideas on how to
overcome this problem?
There seems to be very little or no help for tracking down this
problem.Any help would be greatly appreciated.
Regards.

 

[Roger Abell [MVP]]

Have you tried asking in MSDN ??
I am trying to follow what you are trying, but I get lost when
you say you have set the launch identity to be Interactive.
This means it will be whatever account is then logged into
the system with the class factory. Why would you expect
this to work ? Doesn't it need to launch in an account that
is trusted for delegation, so that it can then create the further
objects in the context of the connecting account ??

Roger