[Samba] After joining domain, Samba uses the workgroup name, not the FQDN when running the net ads command

Rowland penny rpenny at samba.org
Mon Dec 7 18:23:42 UTC 2015

On 07/12/15 18:04, Jonathan S. Fisher wrote:
> Hey Rowland, be kind and avoid passive aggressive comments. I'm just 
> looking to try and get this to work, thanks. If I knew everything 
> already, I wouldn't be here asking questions and trying to solve my 
> own problem. I appreciate your help so far, but if you don't have 
> anything nice say, please just ignore this thread.

If I upset you, I apologise, but I was posting what I was thinking, you 
are trying to get Samba working with a strange setup and you do not seem 
to want to take advice. Get it working in a known way and then adapt it 
to your network.

> So:
> jonathan.fisher at freeradius:~$ sudo hostname -y
> hostname: Local domain name not set
> jonathan.fisher at freeradius:~$ sudo hostname -d
> windows.corp.springventuregroup.com 
> <http://windows.corp.springventuregroup.com>
> jonathan.fisher at freeradius:~$ sudo hostname -f
> freeradius.windows.corp.springventuregroup.com 
> <http://freeradius.windows.corp.springventuregroup.com>
> Unfortunately, since this box is an LXC container, I can't run the 
> syctl command:
> jonathan.fisher at freeradius:~$ sysctl -w 
> kernel.domainname="windows.corp.XXX.com <http://windows.corp.XXX.com>"
> sysctl: permission denied on key 'kernel.domainname'

And this is (as far as I can remember) the first time you have mentioned 
that you are using an LXC container, could this have something to do 
with your problem? Is there any way you could setup a client on bare 
metal and once you have got this working, base your LXC setup on this.

Normally getting a Unix client to work with an AD DC is fairly easy, as 
long as you are aware of the pitfalls.


> We're good here:
> jonathan.fisher at freeradius:~$ cat /etc/hostname
> freeradiusjonathan.fisher at freeradius:~$
> So I added
> dns proxy = true
> No dice, same output as before.
> Made this change:
> jonathan.fisher at freeradius:~$ cat /etc/resolv.conf
> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by 
> resolvconf(8)
> domain windows.corp.springventuregroup.com 
> <http://windows.corp.springventuregroup.com>
> search windows.corp.pringventuregroupcom
> nameserver
> nameserver
> Also the same output, but this message popped up after restarting samba:
> jonathan.fisher at freeradius:~$ sudo service sernet-samba-winbindd 
> restart && sudo service sernet-samba-nmbd restart && sudo service 
> sernet-samba-smbd restart
> sudo: unable to resolve host freeradius
> Shutting down SAMBA winbindd :  *
> Starting SAMBA winbindd :  *
> sudo: unable to resolve host freeradius
> Shutting down SAMBA nmbd :  *
> Starting SAMBA nmbd :  *
> sudo: unable to resolve host freeradius
> Shutting down SAMBA smbd :  *
> Starting SAMBA smbd :  *
> No idea if that's relevant...
> So I undid the resolv.conf change, and here's the output of testparam:
> jonathan.fisher at freeradius:~$ testparm -v | grep net
> Load smb config files from /etc/samba/smb.conf
> rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
> Loaded services file OK.
> Press enter to see a dump of your service definitions
> netbios name = FREERADIUS
> netbios aliases =
> netbios scope =
> disable netbios = No
> dcerpc endpoint servers = epmapper, wkssvc, rpcecho, samr, netlogon, 
> lsarpc, spoolss, drsuapi, dssetup, unixinfo, browser, eventlog6, 
> backupkey, dnsserver
> Sigh... thanks. I'm appreciate your patience and your help.

More information about the samba mailing list