After upgrading from alpha18 to beta2 ports 139 and 445 are no longer bound
abartlet at samba.org
Wed Jul 11 04:19:45 MDT 2012
On Wed, 2012-07-11 at 12:11 +0200, Thomas Hood wrote:
> 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?
> 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.
Yes, we have not fully merged the parameter tables. We know that we
still need to do it.
> It looks as if the installed smb.conf has Samba 3 parameters which
> Samba 4 doesn't understand. But what parameters _does_ Samba 4
Essentially, the samba4 AD components (including the ntvfs file server)
honour the parameters listed with
samba-tool testparm -v
The smbd file server, which is now the default in the DC honours
parameters listed with
The idea is to merge these lists, so at least superficially the two
parsers behave identically, but it is a tedious task not yet finished.
My guess is that the lack of the smbd file server is a packaging error
(perhaps complicated by it forcing a conflict with the samba 3.6
Andrew Bartlett http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
More information about the samba-technical