|
Posted by Joe Kaplan on May 2, 2008, 12:17 pm
Please log in for more thread options Do "View | Tree" and select the domain naming context from the list. It
won't be either the configuration partition or the schema partition and will
usually be the last one in the list unless you have any application
partitions defined for things like DNS.
Note that View | Tree in LDP shows all the objects, not just the users and
groups. If you want to see just users and groups, you would need to query
for that. That won't show you the data in a tree though.
It may be the case that LDP may not be the tool for you for viewing AD data
if you don't know anything about AD or LDAP programming. A tool like AD
Users and Computers may be easier to use.
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
>I would like to view a tree of users and groups. I have not been able to
> figure that out with the ldp tool.
> --
> Arne Garvander
> Certified Geek
> Professional Data Dude
>
>
> "Joe Kaplan" wrote:
>
>> Exactly. LDP is actually a tool designed for LDAP programmers, not
>> really
>> so much for admins as it doesn't really have any task-oriented
>> functionality. It just lets you execute LDAP operations against an LDAP
>> server like AD.
>>
>> You could start by doing a "view tree" and looking around in the tree of
>> one
>> of the partitions.
>>
>> Joe K.
>> --
>> Joe Kaplan-MS MVP Directory Services Programming
>> Co-author of "The .NET Developer's Guide to Directory Services
>> Programming"
>> http://www.directoryprogramming.net
>> --
>> >I guess a good next step would be to formulate what is that you were
>> >going
>> >to do with LDAP?
>> > We cannot help you without knowing that.
>> >
>> > --
>> > Svyatoslav Pidgorny, MS MVP - Security, MCSE
>> > -= F1 is the key =-
>> >
>> > * http://sl.mvps.org * http://msmvps.com/blogs/sp *
>> >
>> >> Blank for server seems to have connected to something.
>> >> I have no clue what to do next. I am a developer not an admin.
>> >>
>> >> --
>> >> Arne Garvander
>> >> Certified Geek
>> >> Professional Data Dude
>> >>
>> >>
>> >> "Joe Kaplan" wrote:
>> >>
>> >>> Generally, if AD is deployed correctly and the current machine is
>> >>> domain
>> >>> joined, you can provide ldp with a null value for the server name and
>> >>> it
>> >>> will locate a domain controller based on the domain that the current
>> >>> user is
>> >>> logged in to. You can also usually just put in the DNS name of the
>> >>> domain
>> >>> you want to use and it will find a DC in that domain.
>> >>>
>> >>> There is generally no reason to change the port as AD always uses
>> >>> port
>> >>> 389
>> >>> for LDAP.
>> >>>
>> >>> Joe K.
>> >>> --
>> >>> Joe Kaplan-MS MVP Directory Services Programming
>> >>> Co-author of "The .NET Developer's Guide to Directory Services
>> >>> Programming"
>> >>> http://www.directoryprogramming.net
>> >>> --
>> >>> > Either check with your network admin or use a port scanner on your
>> >>> > network
>> >>> > and scan for responses at port 389 (for example).
>> >>> >
>> >>> > Jack
>> >>> >
>> >>> >> Thanks,
>> >>> >> I have no idea at what Ip address I would find my active
>> >>> >> directory.
>> >>> >> Any tips?
>> >>> >> --
>> >>> >> Arne Garvander
>> >>> >> Certified Geek
>> >>> >> Professional Data Dude
>> >>> >
>> >>> >
>> >>>
>> >>>
>> >>>
>> >
>> >
>>
>>
>>
| 
XML Sitemap