Re: How to determine what permissions are required for an assembly

From: Hernan de Lahitte (hernan_at_lagash.com)
Date: 02/25/04 

Date: Wed, 25 Feb 2004 10:39:21 -0300

I think you should follow the "classic" network share guideline for this
scenario.

I recently posted a similar answer to this.

1.. On the Web server, open Administrative Tools, and then double-click
Microsoft .NET Framework Configuration.

  2.. Expand Runtime Security Policy, expand Machine, and then expand Code
Groups.

  3.. Right-click All_Code, and then click New.

  4.. Select Create a new code group. Give your code group a relevant name,
such as the name of the applications share. Click Next.

  5.. In the Choose the condition type for this code group list, select URL.

  6.. In the URL text box, type the path of the share in the following
format (where computername is the name of the computer that is hosting the
remote share, and sharename is the name of the share):
file:////\\computername\sharename\*7.. Click Next.
On the next page, select "Use an existing permission set" and then select
FullTrust.
Note: If your assembly does not require FullTrust it is far better to create
your own
named permission set with only the required permissions to execute all the
application. (In this case, SQL Client ans Security (Execution) permissions
might be used).

  8.. Click Next, and then click Finish.
I hope this help.

"surya" <suryanarayanan.varadarajan@honeywell.com> wrote in message
news:%234hTcP5%23DHA.3184@TK2MSFTNGP09.phx.gbl...
> Hi,
>
> I need an application to load signed assemblies from the network share.
The
> assembly in the network share connects to SQL Server database using the
SQL
> Server .Net provider. Because it is loaded from the share folder, the
> assembly gets "Local_Intranet" permissions. The Local_Intranet permissions
> does not have enough permissions to connect to the SQL Server DB. What
> permissions should I add to allow this assembly connect to the DB?
>
> Help is greatly appreciated
>
> Regards
> Surya
>
>

Relevant Pages

  • Re: Can not use network shares on Server 2003 standard edition wit
    ... Okay, I think that it is a permissions and or security issue, although I can ... The physical network topology, is working fine. ... are getting DCHP internal IP addresses, the Server has 2 NIC's which are ... passwords currently match the server's Users and passwords ...
    (microsoft.public.windowsxp.network_web)
  • Re: Users cant log in to sharted directory
    ... is a security issue as well, as the network is at a school for disruptive ... Apologies if this is going over old ground, but this server admin stuff is ... The shared directory has ... Permissions for the users directories is set as user/Administrator/full ...
    (microsoft.public.win2000.networking)
  • Re: How to Force Login Dialog Box when connecting to a computer?
    ... Leave everyone in the user right for access this computer from the network. ... logon/password that exists on the "server" in it's local users then the user ... can be granted seamless access to shares that they have permissions to. ... opens up and then users can see shared folders. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Windows/Exchange server migration
    ... First off all of your permissions will be lost. ... > Windows NT/Exchange 5.5 server to Windows 2003/Exchange ... I am thinking about setting up a new network ...
    (microsoft.public.exchange.design)
  • Re: Backend not connecting
    ... Have a look at the permissions on the server mdb file that you are trying to ... > end to the backend on a network. ... The network configuration seems to be the ...
    (microsoft.public.access.setupconfig)