<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ldap problem in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/ldap-problem/m-p/3472862#M16109</link>
    <description>One other method is to use your DNS server and just set the two ldap boxes to a common name like ldap_server and then list both IP addresses     &lt;BR /&gt;&lt;BR /&gt;You would end up with three DNS entries&lt;BR /&gt;&lt;BR /&gt;ldap1.company.com   145.x.x.x &lt;BR /&gt;ldap2.company.com    145.x.2.x&lt;BR /&gt;&lt;BR /&gt;ldap.company.com      ldap1 ldap2&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 31 May 2005 18:03:41 GMT</pubDate>
    <dc:creator>Sid Shorter_2</dc:creator>
    <dc:date>2005-05-31T18:03:41Z</dc:date>
    <item>
      <title>ldap problem</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ldap-problem/m-p/3472859#M16106</link>
      <description>Hi all,&lt;BR /&gt;I've an openldap server (say ldap-master) that replicates the db to a slave server (say ldap-slave).&lt;BR /&gt;The replication works very well, every change i make on the master take effect also on the slave.&lt;BR /&gt;&lt;BR /&gt;The problem is: &lt;BR /&gt;How can i set the ldap client so that if the master is down it makes the authentication queries to the slave??&lt;BR /&gt;I tried to put two lines in /etc/openldap/ldap.conf on the client&lt;BR /&gt;&lt;BR /&gt;host  IP_master&lt;BR /&gt;host  IP_slave&lt;BR /&gt;&lt;BR /&gt;but it doesn't work&lt;BR /&gt;&lt;BR /&gt;Suggestions&lt;BR /&gt;Thanks</description>
      <pubDate>Thu, 27 Jan 2005 13:13:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ldap-problem/m-p/3472859#M16106</guid>
      <dc:creator>Marco_113</dc:creator>
      <dc:date>2005-01-27T13:13:33Z</dc:date>
    </item>
    <item>
      <title>Re: ldap problem</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ldap-problem/m-p/3472860#M16107</link>
      <description>Just list multiple servers (space separated) on one line, like this:&lt;BR /&gt;&lt;BR /&gt;host IP_master IP_slave&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;-b&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 27 May 2005 16:04:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ldap-problem/m-p/3472860#M16107</guid>
      <dc:creator>Bryan Swanson_1</dc:creator>
      <dc:date>2005-05-27T16:04:59Z</dc:date>
    </item>
    <item>
      <title>Re: ldap problem</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ldap-problem/m-p/3472861#M16108</link>
      <description>You should give the list of servers separated by space. if you are using newer version of ldap HOST is deprecated and URI is the replacement for it. i have attached description for both of them for your referrence.&lt;BR /&gt;&lt;BR /&gt;URI &lt;LDAP&gt;&lt;BR /&gt;      Specifies the URI(s) of an LDAP server(s) to  which the  LDAP  library  should connect.  The URI scheme may be either ldapor ldaps which refer to LDAP over TCP  and  LDAP  over  SSL (TLS) respectively. each server's name can be specified  as  a  domain-style name  or  an  IP  address literal.  Optionally, the server's name can followed by a ':'  and  the  port number the LDAP server is listening on.  If no port number is provided, the default port for the scheme is  used  (389  for  ldap://, 636 for ldaps://).  A space separated list of URIs may be provided.&lt;BR /&gt;&lt;BR /&gt;HOST &lt;NAME&gt;&lt;BR /&gt;      Used to specify the name(s) of an LDAP  server(s)  to  which ldap  library  should connect to.  Each serverâ  s name can be specified as a  domain-style  name  or  an  IP  address  and optionally  followed  a  â  :â    and  the  port number the ldap server is listening on.  A space separated  listed  of  host may be provided.&lt;BR /&gt;&lt;BR /&gt;Rega&lt;/NAME&gt;&lt;/LDAP&gt;</description>
      <pubDate>Sat, 28 May 2005 04:11:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ldap-problem/m-p/3472861#M16108</guid>
      <dc:creator>Gopi Sekar</dc:creator>
      <dc:date>2005-05-28T04:11:10Z</dc:date>
    </item>
    <item>
      <title>Re: ldap problem</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ldap-problem/m-p/3472862#M16109</link>
      <description>One other method is to use your DNS server and just set the two ldap boxes to a common name like ldap_server and then list both IP addresses     &lt;BR /&gt;&lt;BR /&gt;You would end up with three DNS entries&lt;BR /&gt;&lt;BR /&gt;ldap1.company.com   145.x.x.x &lt;BR /&gt;ldap2.company.com    145.x.2.x&lt;BR /&gt;&lt;BR /&gt;ldap.company.com      ldap1 ldap2&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 31 May 2005 18:03:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ldap-problem/m-p/3472862#M16109</guid>
      <dc:creator>Sid Shorter_2</dc:creator>
      <dc:date>2005-05-31T18:03:41Z</dc:date>
    </item>
  </channel>
</rss>

