Help with CLR security

  • Thread starter Thread starter Robert Ellis
  • Start date Start date
R

Robert Ellis

Hi,

I would be grateful for advice on the following.

Server 1 (Windows 2003 Server)
COMSRV1 VB6 COM ActiveX EXE
NETSRV1 .NET (VB2005) .DLL

Workstation 1 (Windows XP Professional)
APP1 VB6 Standard EXE application



APP1 calls COMSRV1 using DCOM. This works fine for Domain Users and Domain
Admins.

COMSRV1 then calls NETSRV1, which as you can see above, is installed on the
same Server. This works fine for Domain Admins, but will NOT work for Domain
Users.

I have downloaded the .NET SDK so that I can use the .NET configuration tool
to configure CLR Security, which I figure is the issue. I've added NETSRV1
to the GAC and set permissions (I think) that should allow NETSRV1 full
access to all resources on the machine and also full access to all resources
at the Intranet level.

Can someone advise how I should configure security to allow Domain Users to
be able to execute all three components in sequence?

Thanks,

Robert
 
Robert Ellis said:
Hi,

I would be grateful for advice on the following.

Server 1 (Windows 2003 Server)
COMSRV1 VB6 COM ActiveX EXE
NETSRV1 .NET (VB2005) .DLL

Workstation 1 (Windows XP Professional)
APP1 VB6 Standard EXE application



APP1 calls COMSRV1 using DCOM. This works fine for Domain Users and Domain Admins.

COMSRV1 then calls NETSRV1, which as you can see above, is installed on the same Server.
This works fine for Domain Admins, but will NOT work for Domain Users.

I have downloaded the .NET SDK so that I can use the .NET configuration tool to configure
CLR Security, which I figure is the issue. I've added NETSRV1 to the GAC and set
permissions (I think) that should allow NETSRV1 full access to all resources on the
machine and also full access to all resources at the Intranet level.

Can someone advise how I should configure security to allow Domain Users to be able to
execute all three components in sequence?

Thanks,

Robert
Click to expand...


This doesn't relate to clr or .NET security, your issue is pure DCOM security. You have to
set the security on the proxy object in code, or you need to adapt the security settings for
the remote server by running DComcnfg.msc.

Willy.
 
Back
Top