Re: Server cannot access client

Hi, I have tried using DCOM error logging but after I run my client and
server, (getting the usual access denied message), I can't find any
DCOM error logs on it except the ones created by Network Service which
I think is created even before I start my program. In any case it says
that

"The machine wide limit settings do not grant Local Access permission
for COM Server applications to the user NT AUTHORITY\NETWORK SERVICE
SID (S-1-5-20). "

But I've already granted local access to NETWORK in "My Computer"
properties.

Does this means that the DCOM permissions I've set is correct? I have
been following this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;892500

If it is not the dcom settings, then what can be giving the problem?

Atiz

Atiz wrote:
Hi all,

I managed to get my OPC client and server working in a domain, but am
having problems in no domain scenarios.
Now trying no domain scenarios, I have created same user account on
both pcs.

It seems I am able not able to DAdvise.

Result = PIDataObject->DAdvise(&formatetc, 0, pSink,
&dwUpdateConnection);
if(FAILED(Result)){
LogUtil::showError(Result,"Failed to get perform
PIDataObject->DAdvise");
throw OPCException("Failed to get perform PIDataObject->DAdvise");
return 1;
}

in DCOM config, I've set the COM Security of "My Computer" access
permissions to include admin , system and user, launch permission to
just include admin and system for the client side. I've also added TCP
ports 135 and 443 too.

Both sides the Firewall is down.
I read an article that if Advise fails, it means the server process
lacks access permissions in the clietn process. But how can it be when
I've set the same user accts, given access permissions to the admin,
system and user? Maybe I miss out something? Please suggestion
something so I can get a move on on this, thanks.

Atiz

ps: good article is here:
http://www.codeguru.com/cpp/com-tech/activex/security/article.php/c5555/

.

Relevant Pages

  • Re: Remote DCOM on WinCE 6.0
    ... as in the client case. ... allowing the selected user name to start the server or, at least, access the ... You have to make sure that your code to actually create the remote ... Once you have all of that, run your DCOM client application in the ...
    (microsoft.public.windowsce.embedded)
  • 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)
  • Re: Remote DCOM on WinCE 6.0
    ... Now we're focussing on loading the server ... as in the client case. ... applet's Network ID tab to be a user name and password that the remote ... Once you have all of that, run your DCOM client application in the ...
    (microsoft.public.windowsce.embedded)
  • Re: Remote DCOM on WinCE 6.0
    ... In fact, the WinCE device will run the server, not the client. ... You have to make sure that your code to actually create the remote object ... Once you have all of that, run your DCOM client application in the debugger ...
    (microsoft.public.windowsce.embedded)
  • Re: COM question
    ... A DLL-based server with a custom interface *not* involving any weird ... This server will run on Windows CE 3 on this device and can be ... A client for above server compiled for Windows XP and connecting to the ... The CE device has the DCOM flag in the registry ...
    (microsoft.public.windowsce.platbuilder)