08-12-2015 06:27 AM - edited 08-13-2015 01:38 AM
Ldap authentification doesn’t work after we’ve implemented a new management AD and changed the ldap authentification server to the new domain. The new AD (Active Directory) is running on “Windows server 2012 R2” with domain functional level “Windows server 2012 R2”.
Ldap authentification works perfectly against our old AD witch is running on “Windows server 2012”, domain functional level “Windows Server 2008 R2”.
The Brocade switch FOS is v. 7.3.0c.
According to the Brocade FOS Admin Guide v. 7.3.0 page 162, it’s actually also stated that:
Have anyone got ldap authentification to work against a Windows Server 2012 r2 domain?
Have anyone a roadmap or information from Brocade when they expect to support ldap authentification against “Windows Server 2012 r2” domain?
Solved! Go to Solution.
09-07-2017 02:07 AM
Found the problem.
Brocade switches can only authenticate using LDAPS (ldap over SSL) on port 636, and since we didnt have LDAPS configures on our AD it didnt work.