Re: Domain could not be contacted problem

From: Joe Kaplan \(MVP - ADSI\) (joseph.e.kaplan_at_removethis.accenture.com)
Date: 11/23/04

  • Next message: Joe Kaplan \(MVP - ADSI\): "Re: Configuration Differences"
    Date: Mon, 22 Nov 2004 22:58:41 -0600
    
    

    The way I see it, you have two choices. You can either get your code
    running under a domain account so that you don't have to supply credentials
    and a server name, or you can supply a server or domain name and supply
    credentials.

    If you go the former route, you have a lot of options. Essentially, you can
    either make the process run under a domain account, or you can impersonate a
    domain account so that your current thread will take on that identity.

    To change the process account, you can either make the worker process run as
    a domain account or move the code into a COM+ component and run that under a
    domain identity.

    To impersonate a domain account, you generally do this by enabling
    impersonation in web.config. If you do that, then you will be impersonating
    the authenticated user in IIS. That will either be the user logging on or
    the anonyous user account (which you can make a domain account if you want).

    It is also possible to impersonate a specific user via web.config by
    specifying credentials and you can impersonate an account through code.
    Thus, you have lots of options. Some of these options vary by the OS you
    are running and your security settings.

    All of the IIS security settings are configured via the IIS MMC on the
    directory security tab.

    Normally, I just supply the server or domain in the binding string and
    supply som credentials from a service account and don't worry about all of
    the above.

    HTH,

    Joe K.

    "Grant" <gpsnett@hotmail.com> wrote in message
    news:u0LvQcN0EHA.1524@TK2MSFTNGP09.phx.gbl...
    > Thank you for the reply! Looking at my web.config file I dont have this
    > "identity impersonate="true"" section and also it says to "security
    > mechanism to Anonymous only" - where do I find this security mechanism,
    > and how would i set the identity impersonate setting?
    >
    > -------------
    > When the Web.config file is set to identity impersonate="true"/ and
    > authentication mode="Windows", use the Anonymous account with the
    > following settings: . On the ASPX page, set the security mechanism to
    > Anonymous only.
    > . Clear the Allow IIS to control the password check box.
    > . Set the Anonymous account to be a domain user.
    >
    > -------------
    >
    > Cheers
    > Grant
    >
    >
    > "Joe Kaplan (MVP - ADSI)" <joseph.e.kaplan@removethis.accenture.com> wrote
    > in message news:Op5qpNN0EHA.3244@TK2MSFTNGP10.phx.gbl...
    >> This is a security context issue. The account your code is running under
    >> might not be a domain account, so you can't use serverless binding (which
    >> is what you are doing when you don't put a server name in the binding
    >> string below).
    >>
    >> This document has a lot more detail:
    >>
    >> http://support.microsoft.com/default.aspx?scid=kb;en-us;329986
    >>
    >> Joe K.
    >>
    >> "Grant" <gpsnett@hotmail.com> wrote in message
    >> news:u2KGc%23M0EHA.2528@TK2MSFTNGP10.phx.gbl...
    >>> Hello,
    >>>
    >>> I got some sample code off the MSDN website on how to loop through a
    >>> group in active directory and list the members. I can run the code from
    >>> a console app but I cant run it from an ASP solution? I get the folowing
    >>> message:
    >>>
    >>> "The specified domain either does not exist or could not be contacted"
    >>>
    >>> Heres the code Im using:
    >>> ---------------------------------------------------
    >>> try
    >>> {
    >>> DirectoryEntry group = new
    >>> DirectoryEntry("LDAP://CN=Administrators,CN=builtin,DC=ourdomain,DC=com");
    >>> object members = group.Invoke("Members",null); //CODE IS FAILING HERE
    >>> foreach( object member in (IEnumerable) members)
    >>> {
    >>> DirectoryEntry x = new DirectoryEntry(member);
    >>> }
    >>> }
    >>> catch ( Exception ex )
    >>> {
    >>> lblResults.Text = ex.Message;
    >>>
    >>> }
    >>> ---------------------------------------------------
    >>>
    >>> I havent done any ASP programming before. This is a standard
    >>> webapplication created using Visual Studio.NET 2003. I have IIS
    >>> installed and Ive set the permissions to interactive user. The above
    >>> code works from my console app and works a beaut but just not from my
    >>> ASP page..
    >>>
    >>> can anyone tell me what Im doing worng here?
    >>>
    >>> Thanks,
    >>> Grant
    >>>
    >>
    >>
    >
    >


  • Next message: Joe Kaplan \(MVP - ADSI\): "Re: Configuration Differences"

    Relevant Pages

    • Re: Opening Files On Other Server ?
      ... > to access a remote resource, the asp.net needs a primary security token ... > a domain account with access to the resource. ... >> server but i am getting security issues. ...
      (microsoft.public.dotnet.framework.aspnet)
    • Re: Problem using ASP.Net Impersonation to access UNC share
      ... You can't directly impersonate a domain account on a workgroup server (your app tier server) because the app tier server is unable to logon the domain account. ...
      (microsoft.public.inetserver.iis.security)
    • Re: Opening Files On Other Server ?
      ... to access a remote resource, the asp.net needs a primary security token for ... a domain account with access to the resource. ... > server but i am getting security issues. ...
      (microsoft.public.dotnet.framework.aspnet)
    • Re: Domain could not be contacted problem
      ... running under a domain account so that you don't have to supply credentials ... and a server name, or you can supply a server or domain name and supply ... To impersonate a domain account, you generally do this by enabling ... All of the IIS security settings are configured via the IIS MMC on the ...
      (microsoft.public.dotnet.framework.aspnet.webservices)
    • Re: Error 80004005 - Database ... does not exist
      ... Set it up as a domain account. ... SQL BI Product Unit ... > utilize any windows security). ... > server, which now that I think of it, would not have access to ANYTHING ...
      (microsoft.public.sqlserver.olap)