Re: LookupAccountName fails with error 1332

From: Matt (anonmous_at_nospam.nospam)
Date: 08/08/05

  • Next message: Joe Kaplan \(MVP - ADSI\): "Re: LookupAccountName fails with error 1332" 
    Date: Mon, 8 Aug 2005 14:55:35 -0700

    Joe,
       Thanks for your response. That was my initial thought as well. However,
    the documentation for LookupAccountName states the following regarding the
    lpSystemName parameter (which is NULL in my case):

    If this string is NULL, the account name translation begins on the local
    system. If the name cannot be resolved on the local system, this function
    will try to resolve the name using domain controllers trusted by the local
    system.

    The way this reads to me is that if the local security authority cannot
    resolve it, it will try the domain controller.

    Matt

    "Joe Richards [MVP]" wrote:

    > I would guess that you aren't asking a machine that knows what server operators
    > is. This name could only be resolved on a domain controller.
    >
    > --
    > Joe Richards Microsoft MVP Windows Server Directory Services
    > www.joeware.net
    >
    >
    > Matt wrote:
    > > Hello,
    > > LookupAccountName fails with error '1332' whenever I use "Server
    > > Operators" as the lpAccountName argument. This call fails on both Windows
    > > 2000 Server SP2 and SP3 systems. The same code handles "Administrators" and
    > > "System" for example with no problem.
    > >
    > > Thanks,
    > >
    > > Matt
    >

  • Next message: Joe Kaplan \(MVP - ADSI\): "Re: LookupAccountName fails with error 1332"

    Relevant Pages

    • Re: Unix Bind and Windows DNS coexist problem with forwarder ON
      ... >> resolve to the IP address of the domain controller so client can ... If the record points to a web server your ... Create in Windows or UNIX Bind? ...
      (microsoft.public.windows.server.dns)
    • Re: Preparing Network Connections... forever
      ... Remeber both domains need to resolve each other, so make sure that both servers can reach eachother zone and that the new tree can resove the _msdcs domain. ... Active Directory was unable to establish a connection with the global catalog. ... Make sure a global catalog is available in the forest, and is reachable from this domain controller. ...
      (microsoft.public.windows.server.active_directory)
    • RE: Windows Server 2003 and slow login
      ... >Yes, the Domain Controller should point to itself only, ... >forwarders to resolve externally. ... >connection in dns is checked in the TCP/IP advanced ... >net start netlogon ...
      (microsoft.public.windows.server.networking)
    • Re: Error 1005 & 1030
      ... > into the event log, i see the same error everytime someone log in his ... the Domain name is not resolved to an IP address on the Domain Controller ... NTI.NEXXLINK.INT, this means that if you resolve that name, it must resolve ... > On the 2k computers i have always the error 1000 with still UserEnv as ...
      (microsoft.public.windows.server.dns)
    • Re: Replication Problem, Event ID 1988
      ... Free Windows event logs reports ... > Can anyone help me to resolve this problem which is messing up the> replication between servers? ... > called "Corporate Enquiries" - this used to be a folder on our> Exchange Server. ... > The local domain controller has attempted to replicate the following> object from the following source domain controller. ...
      (microsoft.public.windows.server.active_directory)
    • Quantcast