After upgrading from alpha18 to beta2 ports 139 and 445 are no longer bound

[Andreas Oster]

Am 11.07.2012 12:11, schrieb Thomas Hood:
> On Tue, Jul 10, 2012 at 6:55 PM, Andreas Oster <aoster at novanetwork.de> wrote:
>> add the following to your smb.conf:
>>
>> server services = +smb -s3fs
>> dcerpc endpoint servers = +winreg +srvsvc
> 
> Thanks for the tip.
> 
> Is this sort of information to be found in a document somewhere?  I
> find it rather confusing that Samba 4 uses the same configuration file
> (smb.conf) as Samba 3, yet the file semantics are not the same. In
> particular, when I upgrade to beta2 the Ubuntu package installs
> /etc/samba/smb.conf but then Samba 4 reports errors in it.
> 
> Unknown parameter encountered: "max log size"
> Ignoring unknown parameter "max log size"
> Unknown parameter encountered: "syslog"
> Ignoring unknown parameter "syslog"
> Unknown parameter encountered: "unix password sync"
> Ignoring unknown parameter "unix password sync"
> Unknown parameter encountered: "passwd program"
> Ignoring unknown parameter "passwd program"
> Unknown parameter encountered: "pam password change"
> Ignoring unknown parameter "pam password change"
> Unknown parameter encountered: "map to guest"
> Ignoring unknown parameter "map to guest"
> Unknown parameter encountered: "usershare allow guests"
> Ignoring unknown parameter "usershare allow guests"
> Unknown parameter encountered: "guest ok"
> Ignoring unknown parameter "guest ok"
> Unknown parameter encountered: "guest ok"
> Ignoring unknown parameter "guest ok"
> 
> It looks as if the installed smb.conf has Samba 3 parameters which
> Samba 4 doesn't understand.  But what parameters _does_ Samba 4
> understand?
> 
Hello Thomas,

if you use the server only as a domain controller and do not intend to
use it as a file server then it should be OK to use ntvfs. All the
samba3 parameters you have listed are only supported when using the new
s3fs backend.

regards

Andreas