I'm strugling to configure ASP.NET when using DCOM to
talk to a COM server sitting on a seperate machine when
the COM server and client are not part of a domain.
I've tried making changes to the <processModel> element
in the machine.config file but still get an error trying
to connect as the target machine does not trust the
client IIS machine.
Re: IWbemServices::CreateInstanceEnum return E_ACCESSDENIED ... then there is no per-call / per-packet authentication.... There is one for other DCOM transports.... > I was able to use RPC_C_AUTHN_LEVEL_CALL on WinXP, with a client running... on the WbemServices object before your query calls. ... (microsoft.public.win32.programmer.wmi)
Re: DCOM security in Windows Server 2003 SP1 ... it's unfortunate that they chose a different name for it in the server edition if it's indeed the same thing. ...DCOM by one account or set COAUTHINFO in COSERVERINFO in CoCreateInstanceEx) with special activation privilege, for example, a domain account in the newly created build-in group "Distributed DCOM user", and switch back to the identity that runs the client program after the activation? ... like to grand remote activation permission to "Everyone" in the computerwide restrictions or DCOM limits whatever it is called, just because our client program fails. ... (microsoft.public.win32.programmer.ole)
DCOM authetication hell with SP2 ... We can get everything working if we add Remote Acess to Anonymous Login DCOM... The Client is a Win32 desktop app. ... Everything is started manually on both Client and Server.... >Now I need to find a way not to use anonymous-logon to ... (microsoft.public.win32.programmer.ole)
DCOM hell with SP2, Only way out seems to be system wide anonymous login ... We can get everything working if we add Remote Acess to Anonymous Login DCOM... The Client is a Win32 desktop app. ... Everything is started manually on both Client and Server.... >Now I need to find a way not to use anonymous-logon to ... (microsoft.public.windowsxp.security_admin)
Re: Authenticating user from another domain ...Client A starts application which attempts to use ... This same DCOM used to work when 'MemberServerDomainB' was a domain ...database instead of Domain B. ... (microsoft.public.security)
