Major - P3 Saying that it found the server implies that a network roundtrip has taken place. This can be misleading.
The following log was taken when my network was turned off:
sajack@spencerLaptop /home/sajack/mongo git master () % LDAPTLS_CACERT=/home/sajack/mongo-enterprise-modules/jstests/external_auth/assets/ldaptest-ca.pem ./mongoldap --ldapServers ldaptest.10gen.cc --ldapAuthzQueryTemplate 'cn={USER},ou=Users,dc=10gen,dc=cc?memberOf' --user ldapz_kerberos1
Running MongoDB LDAP authorization validation checks...
Version: 0.0.0
Checking that an LDAP server has been specified...
[OK] LDAP server found
Connecting to LDAP server...
[FAIL] Could not connect to any of the specified LDAP servers
* Error: OperationFailed: LDAP operation <ldap_search_ext_s>, Failed to perform query: Can't contact LDAP server' Query was: 'BaseDN: "", Scope: "base", Filter: "(objectclass=*)", Attributes: "supportedSASLMechanisms", '". (-1/Can't contact LDAP server): No error could be retrieved from the LDAP server.
* The server may be down, or 'security.ldap.servers' or 'security.ldap.transportSecurity' may be incorrectly configured.
* Alternatively the server may not allow anonymous access to the RootDSE.
A quick glance might lead the reader to believe mongoldap actually connected to the target server.