Hello Experts -

I have been told to achieve linux AD authentication failover , by configuring multiple AD domain controllers in the linux configs. So that, if one AD domain controller is down, OS should lookup for another domain controller in the config and continue to authenticate, even if one of the domain controller is down.

Please suggest how this can be achieved.

OS used: RHEL 6.9 64 bit
AD solution: Windows Active Dir Services



Thanks

If you have a licensed copy of RHEL you should be able to use the Red Hat support pages, documentation, and forums. Have you researched SAMBA setup with Red Hat already?

1 members found this post helpful.

Read the "Question Guidelines" link in my posting signature. We're happy to help, but you need to do some basic research first, before posting. As said by wpeckham, since you're using RHEL you are paying for it, RIGHT?? Since you are, there is ample documentation in the Red Hat knowledgebase you can access, with complete how-to guides.

Putting "how to configure linux as active directory server" into Google pulls up, as the VERY FIRST HIT:
https://wiki.samba.org/index.php/Set...ain_Controller

...including a link to the complete documentation where they take you through setting up replication:
https://wiki.samba.org/index.php/User_Documentation

In many tools you can specify multiple Active Directory (AD) servers (usually called domain controllers) simply by separating them with a comma.

For example using the ldapsearch command line to see various fields:
ldapsearch -x -H "ldap://<first_domain_contorller>,ldap://<second_domain_controller>" -D "<ad_user>@<ad_domain>" -w '<ad_password>' -b "dc=<ad_domain before the dot>,dc=<ad_domain_after the dot>" -E "pr=1000/noprompt" -s sub cn streetAddress physicalDeliveryOfficeName postalcode title telephoneNumber mobile facsimileTelephoneNumber mail

If your domain were billybob.net what follows -b would be "dc=billybob,dc=net".

1 members found this post helpful.

It is not about multiple domains, it is about fail over to next DC in same domain, right ?

It do fail over to next DC if DC completely dead. But if it still up, linux locked on it without rolling to next. Even service restart was not helped. The solution was ask windows team fix broken DC that was done with many thanks for alert.

The last time I configured SAMBA the DC was not defined. You set the DOMAIN and it FINDS the DC the same way Windows clients do. I do not remember the version for certain, but that was CentOS v6 so it should be the same version available to you in the RHEL repos.