nbt service does not EVER register DC as a NBT_NAME_MASTER, NBT_NAME_BROWSER Tested broken on 4.0.5, 4.0.6, 4.1.0pre1-GIT-42b0b27 nmblookup -S TESTGROUP added interface eth0 ip=192.168.1.2 bcast=192.168.1.255 netmask=255.255.255.0 Got a positive name query response from 192.168.1.2 ( 192.168.1.2 ) Got a positive name query response from 192.168.1.2 ( ) 192.168.1.2 TESTGROUP<00> Looking up status of 192.168.1.2 TESTNAME <00> - M <ACTIVE> TESTNAME <03> - M <ACTIVE> TESTNAME <20> - M <ACTIVE> TESTGROUP <1c> - <GROUP> M <ACTIVE> TESTGROUP <00> - <GROUP> M <ACTIVE> __SAMBA__ <00> - <GROUP> M <ACTIVE> <PERMANENT> __SAMBA__ <20> - <GROUP> M <ACTIVE> <PERMANENT> nmblookup -M TESTGROUP added interface eth0 ip=192.168.1.2 bcast=192.168.1.255 netmask=255.255.255.0 name_query failed to find name TESTGROUP#1d
It seems possible, although not recommended, to run nmbd in standalone mode as a workaround. This requires in smb.conf: server role check:inhibit = yes server services = <exclude the nbt service> I found a reference here: http://samba.2283325.n4.nabble.com/lock-directory-wins-td4637035.html#a4637053 and Univention seems to do it this way as well.