On Sunday, 17 December 2017 22:48:03 ACDT Carlos E. R. wrote: [...]
Telcontar:~ # aa-logprof Reading log entries from /var/log/audit/audit.log. Updating AppArmor profiles in /etc/apparmor.d. Enforce-mode changes:
Profile: /usr/sbin/nmbd Capability: net_admin Severity: 8
[1 - capability net_admin,] (A)llow / [(D)eny] / (I)gnore / Audi(t) / Abo(r)t / (F)inish Adding capability net_admin, to profile.
But still, no change from virtualized W10 guest.
With Windows 7 there was a registry entry required to get it to enable older LanManager protocol/s and work correctly with Samba 3. With Windows 10 I'm pretty sure that's no longer supported - Win10 expects to see an AD DC for name resolution. Samba 4 can be setup to mimic an AD controller but it's a lot of work (needs a full openLDAP backend configured) and I've never bothered to work through it. I run Samba at home as a pre-AD PDC and Windows 7 clients join that domain OK (with the registry hack) but no go with Win 10 (yeah, domain logons are overkill for a home network, but it was a learning exercise). I'm pretty sure that it does relate to how later versions of Windows handle name resolution and service discovery - they rely pretty heavily on LDAP for that. WINS was still supported on Win 7, but I'm pretty sure it's gone for Win 10. At work, we run Windows DC's, so learning Samba 4 AD/LDAP has never really been a priority for me. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au CCNA #CSCO12880208 ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org