FreeRADIUS 3.0.x reconfiguration of from LDAP to Windows Server 2022 AD

Alan DeKok aland at deployingradius.com
Thu Sep 5 22:44:04 UTC 2024


On Aug 29, 2024, at 5:46 PM, chucho.valdez <chucho.valdez at seznam.cz> wrote:
> However i have stuck on FreeRADIUS configuration.

  There is documentation on what information should be posted to the list:

  http://wiki.freeradius.org/list-help

> ...
> Unable to chase referral "ldap://ForestDnsZones.mydomain.com/DC=
> ForestDnsZones,DC=gyrec,DC=cz" (-1: Can't contact LDAP server)
> Unable to chase referral "ldap://DomainDnsZones.mydomain.com/DC=
> DomainDnsZones,DC=gyrec,DC=cz" (-1: Can't contact LDAP server)
> Unable to chase referral "ldap://mydomain.com/CN=Configuration,DC=gyrec,DC=
> cz" (-1: Can't contact LDAP server)

  That's pretty clear.

  You made FreeRADIUS use LDAP, and then the LDAP server (or one of the LDAP servers) is unresponsive.

  There are two paths forward:

a) fix FreeRADIUS so that it doesn't use LDAP

b) fix LDAP so it isn't broken.

  Alan DeKok.



More information about the Freeradius-Users mailing list