Problems setting up (fresh) Samba 4 installation
Mark Pilant
lpilant at us.ibm.com
Thu Jan 3 07:06:16 MST 2013
> did you use the the internal dns server or the bind dlz one ?
>
> Can you post the result of the dns requests ?
Here are the results of the original provisioning:
[root at foobar ~]# /usr/local/samba/bin/samba-tool domain provision
Realm: samba4.local
Domain [samba4]:
Server Role (dc, member, standalone) [dc]:
DNS backend (SAMBA_INTERNAL, BIND9_FLATFILE, BIND9_DLZ, NONE)
[SAMBA_INTERNAL]:
DNS forwarder IP address (write 'none' to disable forwarding)
[10.250.53.1]:
Administrator password:
Retype password:
Looking up IPv4 addresses
More than one IPv4 address found. Using 192.168.122.1
Looking up IPv6 addresses
No IPv6 address will be assigned
Setting up secrets.ldb
Setting up the registry
Setting up the privileges database
Setting up idmap db
Setting up SAM db
Setting up sam.ldb partitions and settings
Setting up sam.ldb rootDSE
Pre-loading the Samba 4 and AD schema
Adding DomainDN: DC=samba4,DC=local
Adding configuration container
Setting up sam.ldb schema
Setting up sam.ldb configuration data
Setting up display specifiers
Adding users container
Modifying users container
Adding computers container
Modifying computers container
Setting up sam.ldb data
Setting up well known security principals
Setting up sam.ldb users and groups
Setting up self join
Adding DNS accounts
Creating CN=MicrosoftDNS,CN=System,DC=samba4,DC=local
Creating DomainDnsZones and ForestDnsZones partitions
Populating DomainDnsZones and ForestDnsZones partitions
Setting up sam.ldb rootDSE marking as synchronized
Fixing provision GUIDs
A Kerberos configuration suitable for Samba 4 has been generated
at /usr/local/samba/private/krb5.conf
Once the above files are installed, your Samba4 server will be ready to use
Server Role: active directory domain controller
Hostname: foobar
NetBIOS Domain: SAMBA4
DNS Domain: samba4.local
DOMAIN SID: S-1-5-21-3271447806-2397867778-553691572
[root at foobar ~]#
Starting up Samba and doing the initial tests gave the following results:
[root at foobar ~]# /usr/local/samba/bin/smbclient --version
Version 4.0.0
[root at foobar ~]# /usr/local/samba/bin/smbclient -L localhost -U%
Domain=[SAMBA4] OS=[Unix] Server=[Samba 4.0.0]
Sharename Type Comment
--------- ---- -------
netlogon Disk
sysvol Disk
IPC$ IPC IPC Service (Samba 4.0.0)
Domain=[SAMBA4] OS=[Unix] Server=[Samba 4.0.0]
Server Comment
--------- -------
Workgroup Master
--------- -------
[root at foobar ~]# /usr/local/samba/bin/smbclient //localhost/netlogon
-UAdministrator%'password' -c 'ls'
Domain=[SAMBA4] OS=[Unix] Server=[Samba 4.0.0]
. D 0 Mon Dec 17 10:37:47 2012
.. D 0 Mon Dec 17 10:38:02 2012
50396 blocks of size 1048576. 38977 blocks available
[root at foobar ~]#
Doing the suggested DNS queries gave the following results:
[root at foobar ~]# host -t SRV _ldap._tcp.samba4.local.
Host _ldap._tcp.samba4.local. not found: 3(NXDOMAIN)
[root at foobar ~]# host -t SRV _kerberos._udp.samba4.local.
Host _kerberos._udp.samba4.local. not found: 3(NXDOMAIN)
[root at foobar ~]# host -t A foobar.samba4.local.
foobar.samba4.local has address 10.250.53.1
[root at foobar ~]#
One thing I did try, because of the "More than one IPv4 address found"
message was to explicitly set the host IP address on the provision command:
[root at foobar ~]# samba-tool domain provision --realm samba4.local --domain
samba4 --server-role=dc --host-ip=10.250.53.1 --adminpass='password'
Looking up IPv6 addresses
No IPv6 address will be assigned
Setting up secrets.ldb
Setting up the registry
Setting up the privileges database
Setting up idmap db
Setting up SAM db
Setting up sam.ldb partitions and settings
Setting up sam.ldb rootDSE
Pre-loading the Samba 4 and AD schema
Adding DomainDN: DC=samba4,DC=local
Adding configuration container
Setting up sam.ldb schema
Setting up sam.ldb configuration data
Setting up display specifiers
Adding users container
Modifying users container
Adding computers container
Modifying computers container
Setting up sam.ldb data
Setting up well known security principals
Setting up sam.ldb users and groups
Setting up self join
Adding DNS accounts
Creating CN=MicrosoftDNS,CN=System,DC=samba4,DC=local
Creating DomainDnsZones and ForestDnsZones partitions
Populating DomainDnsZones and ForestDnsZones partitions
Setting up sam.ldb rootDSE marking as synchronized
Fixing provision GUIDs
A Kerberos configuration suitable for Samba 4 has been generated
at /usr/local/samba/private/krb5.conf
Once the above files are installed, your Samba4 server will be ready to use
Server Role: active directory domain controller
Hostname: foobar
NetBIOS Domain: SAMBA4
DNS Domain: samba4.local
DOMAIN SID: S-1-5-21-3913209209-2509686183-88866245
[root at foobar ~]#
Although this did not change the result of the DNS queries. One thing, I
am uncertain which DNS server is being used for the above command, as there
is nothing in the command output to indicate which is being used. (As
opposed to the first attempt, where it is SAMBA_INTERNAL.)
> Are you sure that your /etc/resolv.conf is updated ?
The Samba provisioning did not touch resolv.conf. However, when I did the
network configuration on the system resolv.conf was set up as I would
expect. In other words, network connectivity is as I would expect and
using dig to do network address lookups returns the expected results.
> Also, does:
>
> bind interfaces only = yes
> interfaces = <ipv4 address> 127.0.0.1
> help?
I haven't tried setting the bind interface (in smb.conf), but I have set
the interface to have the IP address of the host (as opposed to the loop
back address).
> I've seen a number of folks have an IPv6 issue that causes the DNS
I don't think this is the case as the provisioning indicates up IPv6
addresses "will be assigned".
Anything else??? :-)
Thanks in advance.
- Mark
More information about the samba-technical
mailing list