I am struggling to get 3 entities to work together to allow remote Dial-Up VPN user to authenticate to AD. I have Server 2008 R2 hosting LDAP. I can do a simple BIND using 2 different LADP tools, LDAPAdministrator and JExplorer. I can use these tools to bind and browse my SCHEMA. I have a Juniper SSG 5 that is configured with LDAP BUT, it does not have a filter to define my samAccountName, on using a version of DN and can only see the CN of Full Name. The 3rd entity is NCP VPN Client that is totally relient upon the JUNIPER VPN.
I am at a loss and am trying not to spend any money from an exhausted Tech budget. I am wondering if it is possible to config the Server 2008 R2 LDAP to "route" or define the CN to samAccountName. Doe sany of this make sense to any GURU's? Any help at all would be greatly appreciated.
Thanks,
Ed