LDAP Browser for AD in Windows Server 2003
Started by
defmonk
, Jun 25 2007 02:43 AM
#1
Posted 25 June 2007 - 02:43 AM
#2
Posted 26 June 2007 - 04:07 AM
I just discovered that I did not configure DNS properly. I had to create PTR records in DNS when I noticed that nslookup returns an error, and in Event Viewer, DNS error says something about not being able to list the content of AD.
My problem with ldap browser is not solved yet, but I know I'm moving in the right direction.
I welcome whatever input anyone has to give and I'll keep y'all posted on how it goes. Cheers.
My problem with ldap browser is not solved yet, but I know I'm moving in the right direction.
I welcome whatever input anyone has to give and I'll keep y'all posted on how it goes. Cheers.
#3
Posted 28 June 2007 - 05:15 AM
Thanks for viewing my post. I eventually downloaded another LDAP Browser (Softerra LDAP Browser 2.6) and I noticed that for every connection failure, the error message says 'Invalid Credentials', so I changed the user account on the browser to LDAP_USER in the AD and set the appropriate password; I also removed 'cn=' from the entry from the USER DN: box.
Now I am able to enumerate the content of the AD.
Cheers.
Now I am able to enumerate the content of the AD.
Cheers.
#4
Posted 28 June 2007 - 07:22 AM
sorry nobody got to you..but yeah...can't browse LDAP without the right creds...some of those viewers handle the credentials differently as well so...always good to read the manual
#5
Posted 11 July 2007 - 06:25 PM
Hello Defmonk,
I don't know if you are still monitoring this thread, but I can offer you some assistance. There are multiple LDAP browsers available.
LDP is a low level LDAP utility from Microsoft. - http://support.microsoft.com/kb/224543
ADSIEdit is another low level LDAP utility that is directly available from Microsoft as well. You will need to download either the Windows 2003 Resource Kit or 2003 Support Tools (I can't remember) to get this utility.
"Active Directory Schema" is a readily available MMC snap-in you can use to your LDAP directory. You will simply need to register it first though to make it available. type "REGSVR32 SCHMMGMT.DLL" at the command prompt to make it available.
A brand spankin new LDAP browser was just made available yesterday from Sysinternals called ADExplorer. You can grab it here...
http://www.microsoft...adexplorer.mspx
And finally, if you prefer to do LDAP queries by command line, then you will want to go get ADFind from Joeware.net.
What sort of LDAP specific problems are you having?
I don't know if you are still monitoring this thread, but I can offer you some assistance. There are multiple LDAP browsers available.
LDP is a low level LDAP utility from Microsoft. - http://support.microsoft.com/kb/224543
ADSIEdit is another low level LDAP utility that is directly available from Microsoft as well. You will need to download either the Windows 2003 Resource Kit or 2003 Support Tools (I can't remember) to get this utility.
"Active Directory Schema" is a readily available MMC snap-in you can use to your LDAP directory. You will simply need to register it first though to make it available. type "REGSVR32 SCHMMGMT.DLL" at the command prompt to make it available.
A brand spankin new LDAP browser was just made available yesterday from Sysinternals called ADExplorer. You can grab it here...
http://www.microsoft...adexplorer.mspx
And finally, if you prefer to do LDAP queries by command line, then you will want to go get ADFind from Joeware.net.
What sort of LDAP specific problems are you having?
Edited by ben.watson, 11 July 2007 - 06:27 PM.
#6
Posted 11 July 2007 - 06:48 PM
Also, you should also perform a...
DCDIAG /V
NETDIAG /V
And look for any errors and resolve those. Once all the tests pass, you should have a largely well running domain controller. You can also add the /FIX switch on the end of both of those commands to allow those utilities to perform safe and trivial fixes for issues you may be experiencing.
DCDIAG /V
NETDIAG /V
And look for any errors and resolve those. Once all the tests pass, you should have a largely well running domain controller. You can also add the /FIX switch on the end of both of those commands to allow those utilities to perform safe and trivial fixes for issues you may be experiencing.
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users