Fibre Channel (SAN)

Reply
Occasional Contributor
Posts: 5
Registered: ‎05-24-2010
Accepted Solution

SAN switch ldap authentication doesn’t work against Active Directory running on a “Windows Server 2012 R2”, domain functional level “Windows Server 2012 R2”

[ Edited ]

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:

  • Only IPv4 is supported for LDAP on Windows 2000 and LDAP on Windows Server 2003. For LDAP on Windows Server 2008, both IPv4 and IPv6 are supported
  • Active Directory LDAP 2000, 2003, and 2008 are supported

 

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?

Occasional Contributor
Posts: 5
Registered: ‎05-24-2010

Re: SAN switch ldap authentication doesn’t work against Active Directory running on a “Windows Server 2012 R2”, domain functional level “Windows Server 2012 R2”

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.

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.

vADC is now Pulse Secure
Download FREE NVMe eBook