ADinsight from the sysinternals toolset is a great tool , but I seem to have problems with it at times. Specifically on Server 2008 & Vista (maybe due to the way it hooks wldap32.dll)
On Vista OS and beyond, there is built in client ldap tracing which can give you similar results ( with a wee bitmore effort )
In order to start the trace you use tracelog.exe ( may be able to use logman.exe as well but I have not tried it )
First , create a new key under HKLM\System\CurrentControlSet\Services\ldap\tracing\
The key name should be the name of the .exe you want to trace , mmc.exe for example.
C:\tools>Tracelog.exe -start ldap -guid #099614a5-5dd7-4788-8bc9-e29f43db28fc -f ldap.etl -flag x1FFFDFF3
After your repro or whatnot, when you want to stop the trace use the following command:
C:\tools>tracelog -stop ldap
In order to format the trace to a readable format use tracerpt.exe
C:\tools>tracerpt.exe ldap.etl -o ldap2.csv -of CSV
Now, open the CSV in excel . There is a whole gob of information, but I have found that if I filter the Event ID column I can easily get what I want from it.
Below I filter on ID = 20
Have fun with it… works nicely in a pinch when you don’t have any other tools at your disposal except for the built in ones. Also works nice for the detailed returns and code flow, as well as how much time it took to perform.