DCOM Authentication failure

[gcar2]

I am running a VB application on a W95 client and using DCOM to create an Object on a Windows 2000 server (The client is not in the same Domain as the Server for many good reasons) and thus no trusted connection exists between client and Server. It seems that DCOM will only work if a trusted connection is in place. Any ideas on how to get around this constraint.

Any help received with much appreciation

 

[almoes]

On the server, did you try adding on the security tab this user from this domain?

cheers,
alej

 

[gcar2]

My real need is to be able to run DCOM on the server from a client for which I cannot create a trusted connection (I have no control over access control on the client side which services different Server scenarios). As ther are some three thousand clients involved, management of a trusted connection for each becomes impossible and I would ideally like to bypass security checking as this is adequately provided from within the application. It seesm that the "None" authentication option does not fully exclude the authnetication I am trying to bypas.

Thanks for the help

 

[SemperFiDownUnda]

Your stuck. You either have to set up a trust or have the client log in with a domain account. This is a big problem on Novell networks that are not using ADS. Despite what it looks like with turning off security in Component services the caller must be trusted once they try to actually call a method of a component running on the server. Welcome to NT Security 101.

 

[NoFrills]

I have a similar problem. Launching a (local server) COM object on a remote system fails when XP is involved. When setting the DCOMCNFG settings to launch as 'Interactive user' and setting security to full control for everyone, I manage to start the application remotely on W2000 but not on an XP system. It does lauch 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. 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? I already specified 'Everyone' full control on the server system for that component, but I'm wondering if there's something else I can do. Do I need to specify some additional access rights for the client system somewhere else?
Any help would be appreciated.
Regards.

 

[almoes]

well, I am still trying to figure it out...if you find something new could you please post it? I will do the same. Thanxs.

Cheers,
alej