[Samba] Runnung samba4 as classic domain controller, win7 thinks it is AD
mjt+samba at tls.msk.ru
Sun Dec 7 02:24:01 MST 2014
07.12.2014 11:00, Andrew Bartlett wrote:
> On Sat, 2014-12-06 at 21:17 +0300, Michael Tokarev wrote:
>> Possible, domain name "TLS" is a NetBIOS-name of the domain.
>> Verify that the name is correctly registered in WINS.
>> Now I wonder if samba4 really supports classic NT4-style domains.
> It really is still expected to, and no intentional changes have been
> made to that. I suspect a genuine netbios name resolution issue, rather
> than something bigger.
I asked around about classic NT-style domain support before upgrading
samba, and got positive replies.
Speaking of netbios name resolution - it's been years (>10) since
this setup is working, back at the time I knew various details but
not anymore. What name should be registered in wins for the domain
I examined browse.dat files on a samba3 DC and this my samba4 DC
(both are set up the same way, I just haven't upgraded samba3 yet),
and both shows the same name, like this:
"TLS" c0001000 "FS" "TLS"
"FS" 408d9b0b "tsrv samba server 4.1.11" "TLS"
Is this c0001000 enough?
Speaking of name resolution -- this is a single subnet, 192.168.177.1/26,
all machines receive configuration over dhcp, with the following info:
netbios-nodetype 2 (peer to peer)
Again, this worked for years, it only broke after I upgraded samba
from samba 3.6 to 4.1. So far, only joining domain does not work,
at least I haven't seen anything else is broken (well, except of
the fix for https://bugzilla.samba.org/show_bug.cgi?id=10297 which
broke another use-case around this, I made comments in that bug
With netbios-nodetype=2, I think it is effectively all or none --
either all registered names works or none.
More information about the samba