- The Windows 2000\XP\.NET Resource Index
Home | About Us | Search

Last Updated December 10, 2003


Active Directory
  Getting Started
  Book Reviews
  Domain Controllers
  Group Policy
  How To Guides
  Install & Configure





Active Directory LDAP Articles

Lightweight Directory Access Protocol (LDAP)  is an established Internet standard that enables cross-network operating system interoperability between directory services that support it. In Windows 2000, LDAP is the primary way the Operating System accesses the Active Directory database. By using this open standard, Microsoft is enabling 3rd party vendors and other platforms (Unix) to be able to work in a Windows 2000 environment and use AD services.
Active Directory and LDAP
LDAP fills a huge hole in NT and provides authenticated access to all network resources. By Mark Minasi , Windows NT Magazine, December 1997

Common LDAP RFCs
Microsoft Knowledge Base Article: 221606 - Enumerates the RFCs that define Lightweight Directory Access Protocol (LDAP). 

How to Change a Windows 2000 User's Password Through LDAP
Microsoft Knowledge Base Article: 269190 - You can set a Windows 2000 user's password through the Lightweight Directory Access Protocol (LDAP) given certain restrictions. This article describes how to set or change the password attribute. 

HOW TO: View and Set Lightweight Directory Access Protocol Policies by Using Ntdsutil.exe 
Microsoft Knowledge Base Article: 315071 -  This step-by-step article describes how to manage Lightweight Directory Access Protocol (LDAP) policies by using the Ntdsutil.exe tool. To ensure that domain controllers (DCs) can support service-level guarantees, you need to specify operational limits for a number of LDAP operations. These limits prevent specific operations from adversely impacting the performance of the server, and also make the server resilient to denial of service attacks 

Introduction to Lightweight Directory Access Protocol (LDAP)
Microsoft Knowledge Base Article: 196455 - To understand Lightweight Directory Access Protocol (LDAP) better, let's discuss X.500 and Directory Access Protocol (DAP).

LDAP & the Future of Directory Services (Part 1)
A new version of LDAP is on the horizon. This first installment of a two-part article examines how the revised protocol might change and how those changes might affect the future of directory services. Source: Windows & .NET Magazine, October 1997.

LDAP & the Future of Directory Services (Part 2)
This conclusion of a two-part article examines how Netscape, Novell, and Microsoft implement LDAP in their directory service solutions. Source: Windows & .NET Magazine, November 1997.

LDAP: Necessary But Not Sufficient
By David Chapell in ENT magazine, May 19, 1999.

The Evolution of LDAP
A brief history of the evolution of LDAP. Source: Windows & .NET Magazine, April 1998.

Using Ldp.exe to Find Data in the Active Directory
Microsoft Knowledge Base Article: 224543 - LDP.EXE is a Windows 2000 Resource Kit utility that can be used to perform LDAP (Lightweight Directory Access Protocol) searches against the Active Directory for specific information given search criteria.

 Troubleshooting Articles
An Access Violation Occurs in Lsass Because of a Stack Overflow 
Microsoft Knowledge Base Article: 319709 - When you are running complex Lightweight Data Access Protocol (LDAP) queries against Active Directory, a domain controller may stop responding (hang) with stack-overflow exception c00000fd.

BUG: Windows 2000 LDAP API Cannot Bind to LDAP Servers
Microsoft Knowledge Base Article: 258811 - The Microsoft LDAP API (wldap32.dll) cannot access LDAP servers that are multi-homed and have more than 51 IP addresses registered. This problem prevents the Active Directory Administration tools from accessing multi-homed Windows 2000 Domain Controllers with more than 51 IP addresses 

Exchange Server and Active Directory Utilize the Same LDAP Ports
Microsoft Knowledge Base Article: 240078 - Windows 2000-based domain controllers utilize Lightweight Directory Access Protocol (LDAP) port 389 for communication to the Active Directory. This port is utilized for client queries and administrative tasks. 

LDAP Sessions Do Not Time Out Properly
Microsoft Knowledge Base Article: 258066 - The time-out mechanism for Lightweight Directory Access Protocol (LDAP) may not work, causing old connections to remain connected. As a result, hundreds of stale LDAP connections may exist on a computer.

"LDAP UDP Operations Per Second" Counter Always Returns Zero
Microsoft Knowledge Base Article: 268969 - When you run System Monitor on a Windows 2000-based domain controller, the "LDAP UDP operations per second" counter from the NTDS Settings object always returns a value of zero instead of the expected values. 

Microsoft LDAP Error Codes
Microsoft Knowledge Base Article: 218185 - Microsoft Windows 2000 Active Directory uses the Internet-standard Lightweight Directory Access Protocol (LDAP) to access information. In response to various LDAP requests, a domain controller returns responses containing field LDAP error 

Multiple LDAP Binds to the Same Connection Cause Memory Leak
Microsoft Knowledge Base Article: 289644 - On a Windows 2000-based domain controller, multiple Lightweight Directory Access Protocol (LDAP) binds over the same connection to that domain controller cause a memory leak.

Stand-Alone "LDAP://" Query Does Not Work
Microsoft Knowledge Base Article: 220594 - When you attempt a stand-alone query using LDAP://, you may receive the following error message: An error occurred while performing the search. Your computer, your Internet service provider, or the specified directory service may be disconnected. Check your connections and try again. 

Entire contents
© 1999
All rights reserved

This site and its contents are Copyright 1999-2003 by Microsoft, NT, BackOffice, MCSE, and Windows are registered trademarks of Microsoft Corporation. Microsoft Corporation in no way endorses or is affiliated with The products referenced in this site are provided by parties other than makes no representations regarding either the products or any information about the products. Any questions, complaints, or claims regarding the products must be directed to the appropriate manufacturer or vendor.