Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Server > Account Group Membership Visible in Active Directory Users and Computers but not Found in LDAP Query

Reply
Thread Tools Display Modes

Account Group Membership Visible in Active Directory Users and Computers but not Found in LDAP Query

 
 
dln
Guest
Posts: n/a

 
      12-30-2008
Hello all,

I've just run across a problem I've never seen before and was hoping someone
could help me with it. We have an in-house (.NET) application that uses
LDAP to query Active Directory (Server 2003 R2 native mode) and check if a
user is a member of a specific group. With certain accounts (mine
included), this check fails. For other accounts, this same check succeeds.
I have replicated the call the .NET application uses via LDP and the
following query yields no results from within LDP, either:

(&(objectClass=group)(CN=Corporate)(member=<my user account's
distinguishedName goes here>))

I started digging a bit further into it and via Active Directory Users and
Computers, I can see my account as a member of the group in question.
However, if I look at the "member" attribute of the group via adsiedit.msc,
my account's distingishedName is nowhere to be found. For that matter, my
account doesn't appear in any of the group's LDAP attributes. If I attempt
to add my user account's distingishedName directly to the member attribute
of the group through adsiedit, adsiedit fails stating that the user is
already a member of the group (yes I know, modifying data via adsiedit is
not recommended but I'm grasping at straws at this point). My account is in
there somewhere, it's just not being reported back via the LDAP properties.

How is it that I can be a member of this group, yet not see a reference to
my account anywhere within the group's LDAP properties? Is there a
different attribute I should be looking at?

Thanks.

 
Reply With Quote
 
 
 
 
dln
Guest
Posts: n/a

 
      12-30-2008
So to resolve this, I removed my account from the group via AD Users and
Computers and then added my account's distinguishedName via adsiedit. It
fixed it, but I'm still curious as to how the group arrived in the state it
was in to begin with.

Cheers.

"dln" <> wrote in message
news:5E662752-A713-4139-B353-...
> Hello all,
>
> I've just run across a problem I've never seen before and was hoping
> someone could help me with it. We have an in-house (.NET) application
> that uses LDAP to query Active Directory (Server 2003 R2 native mode) and
> check if a user is a member of a specific group. With certain accounts
> (mine included), this check fails. For other accounts, this same check
> succeeds. I have replicated the call the .NET application uses via LDP and
> the following query yields no results from within LDP, either:
>
> (&(objectClass=group)(CN=Corporate)(member=<my user account's
> distinguishedName goes here>))
>
> I started digging a bit further into it and via Active Directory Users and
> Computers, I can see my account as a member of the group in question.
> However, if I look at the "member" attribute of the group via
> adsiedit.msc, my account's distingishedName is nowhere to be found. For
> that matter, my account doesn't appear in any of the group's LDAP
> attributes. If I attempt to add my user account's distingishedName
> directly to the member attribute of the group through adsiedit, adsiedit
> fails stating that the user is already a member of the group (yes I know,
> modifying data via adsiedit is not recommended but I'm grasping at straws
> at this point). My account is in there somewhere, it's just not being
> reported back via the LDAP properties.
>
> How is it that I can be a member of this group, yet not see a reference to
> my account anywhere within the group's LDAP properties? Is there a
> different attribute I should be looking at?
>
> Thanks.


 
Reply With Quote
 
Richard Mueller [MVP]
Guest
Posts: n/a

 
      12-31-2008
If you can see the user on the Members tab in ADUC, then the user is a
direct member of the group. The only way the DN of the user will not be in
the "member" attribute of the group object is if the user has the group
designated as their "primary" group (or the membership was just changed and
has not yet replicated to all DC's). When you removed the user from the
group did you assign some other group as "primary"? If so, when you added
the user back into the group the DN was added to the "member" attribute
because the user no longer had the group designated as their "primary". Does
that explain what you saw? Click on the user in ADUC, check the Member Of
tab, and find which group is listed as "Primary group" near the bottom.

The memberOf attribute of the user includes the DN of all groups the user is
a direct member, except the group designated as the "primary" group of the
user. The member attriute of any group includes the DN of all direct
members, except any that have the group designated as their "primary".

--
Richard Mueller
MVP Directory Services
Hilltop Lab - http://www.rlmueller.net
--

"dln" <> wrote in message
news:53B2FC4B-D2BD-4D03-B3E9-...
> So to resolve this, I removed my account from the group via AD Users and
> Computers and then added my account's distinguishedName via adsiedit. It
> fixed it, but I'm still curious as to how the group arrived in the state
> it was in to begin with.
>
> Cheers.
>
> "dln" <> wrote in message
> news:5E662752-A713-4139-B353-...
>> Hello all,
>>
>> I've just run across a problem I've never seen before and was hoping
>> someone could help me with it. We have an in-house (.NET) application
>> that uses LDAP to query Active Directory (Server 2003 R2 native mode) and
>> check if a user is a member of a specific group. With certain accounts
>> (mine included), this check fails. For other accounts, this same check
>> succeeds. I have replicated the call the .NET application uses via LDP
>> and the following query yields no results from within LDP, either:
>>
>> (&(objectClass=group)(CN=Corporate)(member=<my user account's
>> distinguishedName goes here>))
>>
>> I started digging a bit further into it and via Active Directory Users
>> and Computers, I can see my account as a member of the group in question.
>> However, if I look at the "member" attribute of the group via
>> adsiedit.msc, my account's distingishedName is nowhere to be found. For
>> that matter, my account doesn't appear in any of the group's LDAP
>> attributes. If I attempt to add my user account's distingishedName
>> directly to the member attribute of the group through adsiedit, adsiedit
>> fails stating that the user is already a member of the group (yes I know,
>> modifying data via adsiedit is not recommended but I'm grasping at straws
>> at this point). My account is in there somewhere, it's just not being
>> reported back via the LDAP properties.
>>
>> How is it that I can be a member of this group, yet not see a reference
>> to my account anywhere within the group's LDAP properties? Is there a
>> different attribute I should be looking at?
>>
>> Thanks.

>



 
Reply With Quote
 
dln
Guest
Posts: n/a

 
      01-14-2009
Yep, that's exactly what it is. Thanks - I would have never picked up on
that!

"Richard Mueller [MVP]" <rlmueller-> wrote in
message news:%...
> If you can see the user on the Members tab in ADUC, then the user is a
> direct member of the group. The only way the DN of the user will not be in
> the "member" attribute of the group object is if the user has the group
> designated as their "primary" group (or the membership was just changed
> and has not yet replicated to all DC's). When you removed the user from
> the group did you assign some other group as "primary"? If so, when you
> added the user back into the group the DN was added to the "member"
> attribute because the user no longer had the group designated as their
> "primary". Does that explain what you saw? Click on the user in ADUC,
> check the Member Of tab, and find which group is listed as "Primary group"
> near the bottom.
>
> The memberOf attribute of the user includes the DN of all groups the user
> is a direct member, except the group designated as the "primary" group of
> the user. The member attriute of any group includes the DN of all direct
> members, except any that have the group designated as their "primary".
>
> --
> Richard Mueller
> MVP Directory Services
> Hilltop Lab - http://www.rlmueller.net
> --
>
> "dln" <> wrote in message
> news:53B2FC4B-D2BD-4D03-B3E9-...
>> So to resolve this, I removed my account from the group via AD Users and
>> Computers and then added my account's distinguishedName via adsiedit. It
>> fixed it, but I'm still curious as to how the group arrived in the state
>> it was in to begin with.
>>
>> Cheers.
>>
>> "dln" <> wrote in message
>> news:5E662752-A713-4139-B353-...
>>> Hello all,
>>>
>>> I've just run across a problem I've never seen before and was hoping
>>> someone could help me with it. We have an in-house (.NET) application
>>> that uses LDAP to query Active Directory (Server 2003 R2 native mode)
>>> and check if a user is a member of a specific group. With certain
>>> accounts (mine included), this check fails. For other accounts, this
>>> same check succeeds. I have replicated the call the .NET application
>>> uses via LDP and the following query yields no results from within LDP,
>>> either:
>>>
>>> (&(objectClass=group)(CN=Corporate)(member=<my user account's
>>> distinguishedName goes here>))
>>>
>>> I started digging a bit further into it and via Active Directory Users
>>> and Computers, I can see my account as a member of the group in
>>> question. However, if I look at the "member" attribute of the group via
>>> adsiedit.msc, my account's distingishedName is nowhere to be found. For
>>> that matter, my account doesn't appear in any of the group's LDAP
>>> attributes. If I attempt to add my user account's distingishedName
>>> directly to the member attribute of the group through adsiedit, adsiedit
>>> fails stating that the user is already a member of the group (yes I
>>> know, modifying data via adsiedit is not recommended but I'm grasping at
>>> straws at this point). My account is in there somewhere, it's just not
>>> being reported back via the LDAP properties.
>>>
>>> How is it that I can be a member of this group, yet not see a reference
>>> to my account anywhere within the group's LDAP properties? Is there a
>>> different attribute I should be looking at?
>>>
>>> Thanks.

>>

>
>


 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Event 1202 Warnings after Renaming Administrator Account on SBS200 Dave2U Windows Server 9 02-26-2008 10:00 PM
Very slow startup proccess after installing W2003 SP1 on DC's JAV Windows Server 5 06-24-2005 02:58 PM
2000 Server users and security groups and group policies! Users n Security groups n Group Policies Windows Server 5 03-14-2005 12:59 AM
Re: Active Directory - How can I give users local admin rights on all domain computers? nwalker Windows Server 1 09-10-2004 12:55 AM
Event viewer security issue John Windows Server 11 08-17-2004 01:14 AM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59