samba - Mar 2017 - Samba shared folders and windows 7 permissions dialog.

On Sun, 26 Mar 2017 21:29:19 +0300
PF4Public via samba <samba at lists.samba.org> wrote:
> Hi, Rowland, thanks for your reply.
> 
> Neither of machines have samba users as their local users. This makes
> Windows ask for username and password upon connection, I suppose.
> However I'm not determined on what's the difference between those
> machines that show users and groups and those which don't.
> Nonetheless some of machines do display samba/ldap users, whilst
> others do not. Neither of them having samba users as local users, as
> I've already mentioned.
> 
> Also I have identified that neither of Windows XP machines show users
> and groups in permissions dialog, even though file and printer
> accessing has no problems on them.
> 
If some machines show the users, surely this means that Samba is
working and that the problem lies with the windows machines. Have they
all been updated to the same level ? If not, are the ones that show the
users, not been updated, or do they have an update that the others
don't. Are they the same type i.e. 'pro' or 'home' ?

Rowland

It is indeed an issue with Windows, rather than Samba, and I never stated
otherwise.

With respect  to Windows edition they all are "Pro" variant. I have a
feeling, that
failing workstations lack some updates because I have manually updated
successful ones
about a week ago. Comparing installed updates manually must be the last resort
as it's
rate complicated feat.

Thus I started with Samba and found some differences in how Samba treats
different
workstations, which might give me a clue on what's wrong. So my questions
hold:

Is it "0: SAMR_DOMAIN_ACCESS_ENUM_ACCOUNTS" that blocks that windows
host from enumerating
ldap users and groups? If that's true, then why is that happening to the
same user on a
different hosts? What is the origin of struct samr_OpenDomain and how does samba
derive it?


26.03.2017 21:45, Rowland Penny via samba wrote:
> On Sun, 26 Mar 2017 21:29:19 +0300
> PF4Public via samba <samba at lists.samba.org> wrote:
>
>> Hi, Rowland, thanks for your reply.
>>
>> Neither of machines have samba users as their local users. This makes
>> Windows ask for username and password upon connection, I suppose.
>> However I'm not determined on what's the difference between
those
>> machines that show users and groups and those which don't.
>> Nonetheless some of machines do display samba/ldap users, whilst
>> others do not. Neither of them having samba users as local users, as
>> I've already mentioned.
>>
>> Also I have identified that neither of Windows XP machines show users
>> and groups in permissions dialog, even though file and printer
>> accessing has no problems on them.
>>
> If some machines show the users, surely this means that Samba is
> working and that the problem lies with the windows machines. Have they
> all been updated to the same level ? If not, are the ones that show the
> users, not been updated, or do they have an update that the others
> don't. Are they the same type i.e. 'pro' or 'home' ?
>
> Rowland
>

PF4Public via samba wrote:
> It is indeed an issue with Windows, rather than Samba, and I never 
> stated otherwise.
----
    BTW, the means(or method) used to set the account enumeration
permissions on a samba server isn't a windows issue, AFAIK.... ;-)
>
> Is it "0: SAMR_DOMAIN_ACCESS_ENUM_ACCOUNTS" that blocks that
windows
> host from enumerating
> ldap users and groups? If that's true, then why is that happening to 
> the same user on a
> different hosts? What is the origin of struct samr_OpenDomain and how 
> does samba derive it?
In the "smb.conf(5)" manpage, search for:
  winbind enum