Author Topic: Issue joining new Zentyal to existing Zentyal DC  (Read 1345 times)

ippillihplm

  • Zen Apprentice
  • *
  • Posts: 20
  • Karma: +0/-0
    • View Profile
Issue joining new Zentyal to existing Zentyal DC
« on: December 19, 2014, 05:35:39 pm »
Hello All:

I am having an issue with getting a new Zentyal install to join an existing Zentyal DC. Both of the installs are running v4.0.5.  When monitoring the logs, I see this:

Code: [Select]
2014/12/19 11:19:34 INFO> Provision.pm:824 EBox::Samba::Provision::checkAddress - Resolving poseidon.xxx to an IP address
2014/12/19 11:19:34 INFO> Provision.pm:844 EBox::Samba::Provision::checkAddress - The DC poseidon.xxx has been resolved to xxx.xxx.xxx.xxx
2014/12/19 11:19:34 INFO> Provision.pm:847 EBox::Samba::Provision::checkAddress - Checking reverse DNS resolution of 'xxx.xxx.xxx.xxx'...
2014/12/19 11:19:35 INFO> Provision.pm:868 EBox::Samba::Provision::checkAddress - The IP address xxx.xxx.xxx.xxx has been resolved to poseidon.xxx
2014/12/19 11:19:35 INFO> Provision.pm:770 EBox::Samba::Provision::checkServerReachable - Checking if AD server 'xxx.xxx.xxx.xxx' is online...
2014/12/19 11:19:35 INFO> Provision.pm:880 EBox::Samba::Provision::checkFunctionalLevels - Checking forest and domain functional levels...
2014/12/19 11:19:35 INFO> Provision.pm:908 EBox::Samba::Provision::checkRfc2307 - Checking RFC2307 compliant schema...
2014/12/19 11:19:35 INFO> Provision.pm:789 EBox::Samba::Provision::checkLocalRealmAndDomain - Checking local domain and realm...
2014/12/19 11:19:36 INFO> Provision.pm:982 EBox::Samba::Provision::checkClockSkew - Checking clock skew with AD server...
2014/12/19 11:19:36 INFO> Provision.pm:1003 EBox::Samba::Provision::checkClockSkew - Clock skew below two minutes, should be enough.
2014/12/19 11:19:36 INFO> Provision.pm:689 EBox::Samba::Provision::checkDnsZonesInMainPartition - Checking for old DNS zones stored in main domain partit
ion...
2014/12/19 11:19:36 INFO> Provision.pm:736 EBox::Samba::Provision::checkForestDomains - Checking number of domains inside forest...
2014/12/19 11:19:36 INFO> Provision.pm:942 EBox::Samba::Provision::checkTrustDomainObjects - Checking for domain trust relationships...
2014/12/19 11:19:37 INFO> Provision.pm:1044 EBox::Samba::Provision::checkADServerSite - Checking the site where the specified server is located
2014/12/19 11:19:37 INFO> Provision.pm:1052 EBox::Samba::Provision::checkADServerSite - The specified server has been located at site named Default-First
-Site-Name
2014/12/19 11:19:37 INFO> Provision.pm:1069 EBox::Samba::Provision::checkADNebiosName - Checking domain netbios name...
2014/12/19 11:19:37 INFO> Provision.pm:1292 EBox::Samba::Provision::provisionADC - Joining to domain 'xxx' as DC
2014/12/19 11:19:39 INFO> Provision.pm:1305 EBox::Samba::Provision::provisionADC - Trying to get a kerberos ticket for principal 'xxx@xxx'
2014/12/19 11:19:40 INFO> Provision.pm:1314 EBox::Samba::Provision::provisionADC - Executing domain join
2014/12/19 11:19:41 ERROR> Sudo.pm:240 EBox::Sudo::_rootError - root command samba-tool domain join xxx DC  --username='xxx'  --workgroup=
'corp'  --password=`cat /var/lib/zentyal/tmp/yUVjmS`  --server='xxx.xxx.xxx.xxx'  --dns-backend=BIND9_DLZ  --realm='xxx'  --site='Default-First
-Site-Name'  failed.
Error output:
Command output: Usage: samba-tool domain join <dnsdomain> [DC|RODC|MEMBER|SUBDOMAIN] [options]
 
.

I have tried the command line itself that is presented.  When I run it the cmdline, it joins just fine and joins the domain as expected.  So I cannot seem to figure out why the GUI doesn't seem to join.  I have tried running the join with a VPN tunnel as these are in 2 physically different locations and they seem to have the same issue except with the proper internal IP addresses.

Any ideas what else I can try here?  Any other logs I can look into beyond the /var/log/zentyal/zentyal.log?

-Michael