From 0e7afd7d64b04781802501ef01f1ab9cbdf4b93b Mon Sep 17 00:00:00 2001 From: Michael Adam Date: Mon, 18 Mar 2013 02:47:46 +0100 Subject: [PATCH] WHATSNEW: clarify how being a domain member server is supported in Samba 4.0 Signed-off-by: Michael Adam --- WHATSNEW.txt | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) diff --git a/WHATSNEW.txt b/WHATSNEW.txt index d623330f50e..30cc8860ecd 100644 --- a/WHATSNEW.txt +++ b/WHATSNEW.txt @@ -401,6 +401,18 @@ For pure file server work, the binaries users would expect from that series (smbd, nmbd, winbindd, smbpasswd) continue to be available. +Domain Member Support +===================== + +Domain member support in the 'samba' binary is in its infancy, and +is not comparable to the support found in 'winbindd'. As such, on +Samba domain member servers, the binaries 'smbd', 'nmbd' and 'winbindd' +are to be used, as known from Samba 3 domain member server setups. +The only exceptions from this rule are the cases which explicitly +require the 'samba' binary, namely running the ntvfs file server, +the CIFS proxy or OpenChange on a domain member. + + DNS === @@ -450,11 +462,6 @@ Known Issues headers at compile time) is known to cause errors when dealing with non-ASCII characters. -- Domain member support in the 'samba' binary is in its infancy, and - is not comparable to the support found in winbindd. As such, do not - use the 'samba' binary (provided for the AD server) on a member - server. - - There is no NetBIOS browsing support (network neighbourhood) available for the AD domain controller. (Support in nmbd and smbd for classic domains and member/standalone servers is unchanged). -- 2.11.4.GIT