> > Finally 'browseable' is redundant on a Samba AD DC, there is no > browsing on an AD DC. >Well, sometimes you just *have* to do some file serving out of an AD DC. It happened to me. In that case, if you don't have "browsable = yes" on a share, that share will not appear in the Computer Management applet in Windows and you won't be able to set its share permissions. Am I wrong?
On 11/04/16 21:29, Miguel Medalha wrote:> >> >> Finally 'browseable' is redundant on a Samba AD DC, there is no >> browsing on an AD DC. >> > > Well, sometimes you just *have* to do some file serving out of an AD > DC. It happened to me.I am not saying you cannot have shares on a Samba AD DC, what I am saying is that there is no browsing code in the 'nbt' portion of the 'samba' binary and hence they will not show up in 'network neighbourhood'> > In that case, if you don't have "browsable = yes" on a share, that > share will not appear in the Computer Management applet in Windows and > you won't be able to set its share permissions. > > Am I wrong?As far as I am aware, on an Samba AD DC, yes. Rowland
> I am not saying you cannot have shares on a Samba AD DC, what I am > saying is that there is no browsing code in the 'nbt' portion of the > 'samba' binary and hence they will not show up in 'network neighbourhood' >I was, and am not, disputing that. I was just saying that having "browsable = yes" on a share may be necessary, for different reasons. As I said before, if you don't have "browsable = yes" on a share, that share will not appear in the "Computer Management" applet in Windows and you won't be able to set its share permissions. I met this more than once, at least with Samba 4.1.x and 4.2.x. Tomorrow I can confirm if this behavior still exists with 4.4.0.
Miguel Medalha <medalist at sapo.pt> schrieb:> Well, sometimes you just *have* to do some file serving out of an AD DC. > It happened to me. > In that case, if you don't have "browsable = yes" on a share, that share > will not appear in the Computer Management applet in Windows and you > won't be able to set its share permissions.I removed the double browseable, but the situation didn't change... But I have notice something stranger: the problem just happen with two users in the "Domain Admins"-group. With another user, not in this group, new created files and directories have the right owner... Any idea? I'll try later to reconfigure the share using ACL. Thanks Luca Bertoncello (lucabert at lucabert.de)
Zitat von Luca Bertoncello <lucabert at lucabert.de>:> I removed the double browseable, but the situation didn't change... > > But I have notice something stranger: the problem just happen with two users > in the "Domain Admins"-group. > With another user, not in this group, new created files and directories have > the right owner...Well, I noticed right now something other strange, and it may be the problem... If I add the user to the group "Domain Admins" all created files and directories have wrong owner. As soon as the user is no member of "Domain Admins" anymore, the owner is correct... Could you suggest an explanation? I need two users on the AD to be Admins, but they have to have the right file's owner, too... Thanks Luca Bertoncello (lucabert at lucabert.de)