18.04 - Joining AD: realm join looking for the wrong LDAP server












0















After a fresh install and update && upgrade, I have followed this guide to add the machine to our AD infrastructure, but after basic configuration realm join -v [domain] returns



! Can't contact LDAP server
realm: No such realm found


So I fired up a CentOS minimal VM and was able to register the machine through that. Cross-referencing the two outputs, I noticed that on Ubuntu the same realm command is querying the wrong IP when looking up the LDAP server, but I did not find any info on how to change that parameter in config files or through man realm.



So I tried ldapsearch -h [server IP], manually specifying the server and this was returned:



ldap_sasl_interactive_bind_s: Local error (-2)
additional info: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No Kerberos credentials available (default cache: FILE:/tmp/krb5cc_0))


which it should not be an issue since the same result is given by the CentOS VM, despite it joining successfully. So, I copied over from the CentOS machine the config files for krb5.conf, sssd.conf and realmd.conf (after a backup), but the same original error was given.



I believe that the wrong LDAP DSE lookup is the issue but I cannot find the parameter to change anywhere.



Thank you for all your help.



The AD server runs Windows Server 2016.
Providing .conf files below:



krb5.conf



[libdefaults]
default_realm = MYDOMAIN.COM
dns_lookup_realm = true
dns_lookup_kdc = true
forwardable = true
rdns = false

[realms]
MYDOMAIN.COM = {
kdc = server.mydomain.com
admin_server = server.mydomain.com
default_domain = mydomain.com
}

[domain_realm]
.mydomain.com = MYDOMAIN.COM
mydomain.com = MYDOMAIN.COM


sssd.conf



[sssd]
services = nss, pam
domains = mydomain.com
config_file_version = 2


[domain/mydomain.com]
id_provider = ad
access_provider = ad
ad_domain = mydomain.com
krb5_realm = MYDOMAIN.COM
realmd_tags = manages-system joined-with-adcli
cache_credentials = True
krb5_store_password_if_offline = True
default_shell = /bin/bash
ldap_id_mapping = True
use_fully_qualified_names = True
fallback_homedir = /home/%d/%u


realmd.conf



[users]
default-home = /home/%D/%U
default-shell = /bin/bash

[active-directory]
default-client = sssd
os-name = Ubuntu
os-version = 18.04

[service]
automatic-install = no

[mydomain.com]
fully-qualified-names = yes
automatic-id-mapping = no
user-principal = yes
manage-system = yes









share|improve this question





























    0















    After a fresh install and update && upgrade, I have followed this guide to add the machine to our AD infrastructure, but after basic configuration realm join -v [domain] returns



    ! Can't contact LDAP server
    realm: No such realm found


    So I fired up a CentOS minimal VM and was able to register the machine through that. Cross-referencing the two outputs, I noticed that on Ubuntu the same realm command is querying the wrong IP when looking up the LDAP server, but I did not find any info on how to change that parameter in config files or through man realm.



    So I tried ldapsearch -h [server IP], manually specifying the server and this was returned:



    ldap_sasl_interactive_bind_s: Local error (-2)
    additional info: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No Kerberos credentials available (default cache: FILE:/tmp/krb5cc_0))


    which it should not be an issue since the same result is given by the CentOS VM, despite it joining successfully. So, I copied over from the CentOS machine the config files for krb5.conf, sssd.conf and realmd.conf (after a backup), but the same original error was given.



    I believe that the wrong LDAP DSE lookup is the issue but I cannot find the parameter to change anywhere.



    Thank you for all your help.



    The AD server runs Windows Server 2016.
    Providing .conf files below:



    krb5.conf



    [libdefaults]
    default_realm = MYDOMAIN.COM
    dns_lookup_realm = true
    dns_lookup_kdc = true
    forwardable = true
    rdns = false

    [realms]
    MYDOMAIN.COM = {
    kdc = server.mydomain.com
    admin_server = server.mydomain.com
    default_domain = mydomain.com
    }

    [domain_realm]
    .mydomain.com = MYDOMAIN.COM
    mydomain.com = MYDOMAIN.COM


    sssd.conf



    [sssd]
    services = nss, pam
    domains = mydomain.com
    config_file_version = 2


    [domain/mydomain.com]
    id_provider = ad
    access_provider = ad
    ad_domain = mydomain.com
    krb5_realm = MYDOMAIN.COM
    realmd_tags = manages-system joined-with-adcli
    cache_credentials = True
    krb5_store_password_if_offline = True
    default_shell = /bin/bash
    ldap_id_mapping = True
    use_fully_qualified_names = True
    fallback_homedir = /home/%d/%u


    realmd.conf



    [users]
    default-home = /home/%D/%U
    default-shell = /bin/bash

    [active-directory]
    default-client = sssd
    os-name = Ubuntu
    os-version = 18.04

    [service]
    automatic-install = no

    [mydomain.com]
    fully-qualified-names = yes
    automatic-id-mapping = no
    user-principal = yes
    manage-system = yes









    share|improve this question



























      0












      0








      0








      After a fresh install and update && upgrade, I have followed this guide to add the machine to our AD infrastructure, but after basic configuration realm join -v [domain] returns



      ! Can't contact LDAP server
      realm: No such realm found


      So I fired up a CentOS minimal VM and was able to register the machine through that. Cross-referencing the two outputs, I noticed that on Ubuntu the same realm command is querying the wrong IP when looking up the LDAP server, but I did not find any info on how to change that parameter in config files or through man realm.



      So I tried ldapsearch -h [server IP], manually specifying the server and this was returned:



      ldap_sasl_interactive_bind_s: Local error (-2)
      additional info: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No Kerberos credentials available (default cache: FILE:/tmp/krb5cc_0))


      which it should not be an issue since the same result is given by the CentOS VM, despite it joining successfully. So, I copied over from the CentOS machine the config files for krb5.conf, sssd.conf and realmd.conf (after a backup), but the same original error was given.



      I believe that the wrong LDAP DSE lookup is the issue but I cannot find the parameter to change anywhere.



      Thank you for all your help.



      The AD server runs Windows Server 2016.
      Providing .conf files below:



      krb5.conf



      [libdefaults]
      default_realm = MYDOMAIN.COM
      dns_lookup_realm = true
      dns_lookup_kdc = true
      forwardable = true
      rdns = false

      [realms]
      MYDOMAIN.COM = {
      kdc = server.mydomain.com
      admin_server = server.mydomain.com
      default_domain = mydomain.com
      }

      [domain_realm]
      .mydomain.com = MYDOMAIN.COM
      mydomain.com = MYDOMAIN.COM


      sssd.conf



      [sssd]
      services = nss, pam
      domains = mydomain.com
      config_file_version = 2


      [domain/mydomain.com]
      id_provider = ad
      access_provider = ad
      ad_domain = mydomain.com
      krb5_realm = MYDOMAIN.COM
      realmd_tags = manages-system joined-with-adcli
      cache_credentials = True
      krb5_store_password_if_offline = True
      default_shell = /bin/bash
      ldap_id_mapping = True
      use_fully_qualified_names = True
      fallback_homedir = /home/%d/%u


      realmd.conf



      [users]
      default-home = /home/%D/%U
      default-shell = /bin/bash

      [active-directory]
      default-client = sssd
      os-name = Ubuntu
      os-version = 18.04

      [service]
      automatic-install = no

      [mydomain.com]
      fully-qualified-names = yes
      automatic-id-mapping = no
      user-principal = yes
      manage-system = yes









      share|improve this question
















      After a fresh install and update && upgrade, I have followed this guide to add the machine to our AD infrastructure, but after basic configuration realm join -v [domain] returns



      ! Can't contact LDAP server
      realm: No such realm found


      So I fired up a CentOS minimal VM and was able to register the machine through that. Cross-referencing the two outputs, I noticed that on Ubuntu the same realm command is querying the wrong IP when looking up the LDAP server, but I did not find any info on how to change that parameter in config files or through man realm.



      So I tried ldapsearch -h [server IP], manually specifying the server and this was returned:



      ldap_sasl_interactive_bind_s: Local error (-2)
      additional info: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (No Kerberos credentials available (default cache: FILE:/tmp/krb5cc_0))


      which it should not be an issue since the same result is given by the CentOS VM, despite it joining successfully. So, I copied over from the CentOS machine the config files for krb5.conf, sssd.conf and realmd.conf (after a backup), but the same original error was given.



      I believe that the wrong LDAP DSE lookup is the issue but I cannot find the parameter to change anywhere.



      Thank you for all your help.



      The AD server runs Windows Server 2016.
      Providing .conf files below:



      krb5.conf



      [libdefaults]
      default_realm = MYDOMAIN.COM
      dns_lookup_realm = true
      dns_lookup_kdc = true
      forwardable = true
      rdns = false

      [realms]
      MYDOMAIN.COM = {
      kdc = server.mydomain.com
      admin_server = server.mydomain.com
      default_domain = mydomain.com
      }

      [domain_realm]
      .mydomain.com = MYDOMAIN.COM
      mydomain.com = MYDOMAIN.COM


      sssd.conf



      [sssd]
      services = nss, pam
      domains = mydomain.com
      config_file_version = 2


      [domain/mydomain.com]
      id_provider = ad
      access_provider = ad
      ad_domain = mydomain.com
      krb5_realm = MYDOMAIN.COM
      realmd_tags = manages-system joined-with-adcli
      cache_credentials = True
      krb5_store_password_if_offline = True
      default_shell = /bin/bash
      ldap_id_mapping = True
      use_fully_qualified_names = True
      fallback_homedir = /home/%d/%u


      realmd.conf



      [users]
      default-home = /home/%D/%U
      default-shell = /bin/bash

      [active-directory]
      default-client = sssd
      os-name = Ubuntu
      os-version = 18.04

      [service]
      automatic-install = no

      [mydomain.com]
      fully-qualified-names = yes
      automatic-id-mapping = no
      user-principal = yes
      manage-system = yes






      networking 18.04 ldap






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 15 at 12:20







      Habardeen

















      asked Jan 15 at 12:14









      HabardeenHabardeen

      13




      13






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "89"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1109923%2f18-04-joining-ad-realm-join-looking-for-the-wrong-ldap-server%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Ask Ubuntu!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1109923%2f18-04-joining-ad-realm-join-looking-for-the-wrong-ldap-server%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Category:香港粉麵

          List *all* the tuples!

          Channel [V]