Preparing for the LDAP/s transition, I noticed some strange behavior that I can't explain. I used the ldp.exe tool to test these connections. I have successfully configured LDAP/s on port 636 as well as continuing to allow the standard non-ssl connections over 389. Here's the weirdness.. one of our domains allows the tree to be browsed without performing a bind after connecting. It only works if the connection is made over 636 (ssl), not if made over 389.
So to sum up, if I connect over 389 without ssl, then attempt to browse the tree, I get the expected:
"Error comment: In order to perform this operation a successful bind must be completed on the connection"
If I connect over 636 with SSL, I am able to add the tree and browse all nodes.
This is only happening in one of our domains, and it doesn't make any sense. There are no anonymous permissions delegated, but I can't see why that would even matter, since it only let's me browse when I'm connected via 636. Keep in mind I am not attempting a bind in either scenario. Thoughts?