Adding Samba4 DC to existing Samba4 Domain

fishknuckles jsblists at gmail.com
Fri May 11 09:46:28 MDT 2012


I'm having issues joining a new samba4 DC (alpha20) to an existing samba4 DC
(alpha12).

I basically haven't gotten anywhere.  The install is complete on the new
box, and Krb works fine.  

[root at pdc01 samba]# kinit -V bob
Password for bob at DOMAIN.FOO.COM: 
Authenticated to Kerberos v5

But when I run the samba-tool domain join, I get the following:


[root at pdc01 samba]# /usr/local/samba/bin/samba-tool domain join
domain.foo.com DC -Ubob --realm=domain.foo.com
Finding a writeable DC for domain 'domain.foo.com'
Found DC pdc.domain.foo.com
Password for [FOO\bob]:
workgroup is FOO
realm is domain.foo.com
checking sAMAccountName
Adding CN=PDC01,OU=Domain Controllers,DC=domain,DC=foo,DC=com
Adding
CN=PDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=foo,DC=com
Adding CN=NTDS
Settings,CN=PDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=foo,DC=com
Adding SPNs to CN=PDC01,OU=Domain Controllers,DC=domain,DC=foo,DC=com
Setting account password for PDC01$
Enabling account
Calling bare provision
Join failed - cleaning up
checking sAMAccountName
Deleted CN=PDC01,OU=Domain Controllers,DC=domain,DC=foo,DC=com
Deleted CN=NTDS
Settings,CN=PDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=foo,DC=com
Deleted
CN=PDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=foo,DC=com
ERROR(exceptions.NameError): uncaught exception - global name 'all' is not
defined
  File
"/usr/local/samba/lib64/python2.4/site-packages/samba/netcmd/__init__.py",
line 160, in _run
    return self.run(*args, **kwargs)
  File
"/usr/local/samba/lib64/python2.4/site-packages/samba/netcmd/domain.py",
line 179, in run
    machinepass=machinepass)
  File "/usr/local/samba/lib64/python2.4/site-packages/samba/join.py", line
964, in join_DC
    ctx.do_join()
  File "/usr/local/samba/lib64/python2.4/site-packages/samba/join.py", line
870, in do_join
    ctx.join_provision()
  File "/usr/local/samba/lib64/python2.4/site-packages/samba/join.py", line
598, in join_provision
    dns_backend="NONE")
  File
"/usr/local/samba/lib64/python2.4/site-packages/samba/provision/__init__.py",
line 1688, in provision
    sitename=sitename, rootdn=rootdn)
  File
"/usr/local/samba/lib64/python2.4/site-packages/samba/provision/__init__.py",
line 503, in guess_names
    if not valid_netbios_name(netbiosname):
  File "/usr/local/samba/lib64/python2.4/site-packages/samba/__init__.py",
line 310, in valid_netbios_name
    return all([is_valid_netbios_char(x) for x in name])

I'm assuming all the python errors are a result of the failure to join the
domain, and not the actual root-cause.  Are there any logs I can look at
that would maybe give me some insight here?  I tried just creating a basic
smb.conf to specify a log file, but that doesn't seem to work.  Also, the
existing PDC doesn't really show any useful errors in its own logs.  It
doesn't seem like I have much to go on.

I'm doing this as part of a migration from old hardware to new hardware.  It
seems like the best way to accomplish this is to join the new box to the
existing domain as a DC, let the databases sync up, and then promote the new
DC to be the PDC.  If there's a better way to accomplish this, please let me
know.

Thank you.

--
View this message in context: http://samba.2283325.n4.nabble.com/Adding-Samba4-DC-to-existing-Samba4-Domain-tp4626792.html
Sent from the Samba - samba-technical mailing list archive at Nabble.com.


More information about the samba-technical mailing list