Groups | Blog | Home
all groups > dotnet remoting > march 2006 >

dotnet remoting : Security and Remoting Problem


David White
3/27/2006 4:27:29 PM
Thanks in advance for any pointers or help you can provide...

I am rather new to all this so forgive any newbie mistakes...

I have a WinNT Service written in C#. Once it starts up, it exports an
IPC-based remote object interface to permit another component of my application
(a C# Windows Forms application) to use the service as a proxy of sorts.

The Service runs in the LocalSystem account. The Windows Forms application is
running on the same machine but on the user's desktop.

When I attempt to access the remote object's method, I get an exception thrown
when the attempt is made to connect to the IPC port. It reads, "failed to
connect to an IPC port: access is denied".

Using SysInternals' ProcessExplorer, I have taken a look at the IPC which the
service has made available. I can see that its security permissions on the
named pipe basically grants all to the System account. But it denies all to
Network. There are no other accounts/groups listed.

From the above it seems to make sense that my application cannot connect to
complete the remote call. The question is, what is needed to permit this call
to complete and how do I do it?

David White
3/27/2006 5:39:15 PM
Thanks, found the answer myself. I needed to create the server channel using
one of the constructors that takes a dictionary argument. In that dictionary I
needed a name/value set = authorizedGroup/Everyone. Cheers!

[quoted text, click to view]
AddThis Social Bookmark Button