View Single Post
  #4 (permalink)  
Old 10-19-2009, 01:17 PM
RadHaz75's Avatar
RadHaz75 RadHaz75 is offline
BES Expert
Join Date: May 2009
Location: Philadelphia, PA
Posts: 98

All of our users are contained in 2 child domains under our parent domain. We ran into a problem where if LDAP settings were enabled on the BES (which is in Child A), the BES could not resolve users in Child B, even with DC enabled (port 3268).

My problem is we have a Load Balanced VIP in Child A that I need to point to (pointing to the parent domain is not an option for me). Thus I called RIM and they presented me with a key that is not really documented anywhere, "LDAPUseForestRootNamingContext"=dword:00000001. Since there is no way to specify your own SearchDN, enabling this key will force the SearchDN to start from the parent domain (DC=Domain,DC=com) as opposed to the child that it is in (DC=Child,DC=Domain,DC=com).

Just wanted to share this since this caused me a lot of frustration.
Two months ago, I saw a provocative movie on cable TV. It was called The Net, with that girl from the bus.
Reply With Quote