Results 1 to 3 of 3
  1. #1
    New Lounger
    Join Date
    Jan 2004
    Location
    Johannesbutg, South Africa
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    ASP.Net across multiple servers in a domain (ASP.Net 1.1)

    Hi
    I'm trying to install a client ASP.Net application within a domain, where the SQL database resides on one server, and IIS is on a different server within the same domain. The IWAM_servername user account created by the .net framework install is a local account on the IIS server, which means that it can't be authenticated by SQL, as the
    IWAM_servername account is not recognised at domain level.

    How can I get SQL to find the ASP user account when IIS resides on a different server?

    Many thanks
    <img src=/S/confused.gif border=0 alt=confused width=15 height=20> DLS

  2. #2
    Lounger
    Join Date
    May 2002
    Location
    Fort Worth, Texas, USA
    Posts
    36
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: ASP.Net across multiple servers in a domain (ASP.Net 1.1)

    If you have access to the SQL table and are getting the "Not ...trusted user connection" message, try this on your end. I am not sure if these are all of the pieces to your puzzle, I have no clue what the SQL and Network guys did:

    1. Add this line of code to the web.config: <pre><identity impersonate="true" /></pre>

    2. Double check these lines in the web.config and make sure they are as follows:
    <pre> <authentication mode="Windows" />
    <allow users="*" /> </pre>

    3. Make sure the folder where the project resides is an

  3. #3
    Silver Lounger
    Join Date
    Jan 2001
    Location
    Indianapolis, Indiana, USA
    Posts
    1,862
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: ASP.Net across multiple servers in a domain (ASP.Net 1.1)

    Hi DLS,

    In addition to what Loren Ann pointed out, let me share the method I use. I typically use a separate SQL Login rather than a Windows login. This way, the SQL User has permissions ONLY to the specified objects needed for the web process - normally only specified Stored Procedures. This seems more secure than giving a domain-level account access through the network, although that really depends on the way it's applied.

    FWIW - my company's site uses ASP.NET Forms authentication against our own members database. We use a SQL Login for all of our SQL connections, although we also use Impersonation in order to access some FoxPro resources.

    Hope this helps!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •