search for: base_tdb

...e spnego = yes template shell = /bin/bash winbind use default domain = Yes winbind enum users = No winbind enum groups = No winbind nested groups = Yes idmap cache time = 0 idmap config * : backend = tdb idmap config * : range = 1000 - 200000000 idmap config * : base_tdb = 0 enable core files = false wins server = 10.0.0.1 guest ok = yes map to guest = Bad Password [bwprinter] printer name = bwqueue printable = yes browseable = yes guest ok = yes guest only = yes writable = yes printing = cups...

...auth = yes ntlm auth = yes client use spnego = yes template shell = /bin/bash winbind use default domain = Yes winbind enum users = No winbind enum groups = No winbind nested groups = Yes idmap cache time = 0 idmap config * : backend = tdb idmap config * : range = 1000 - 200000000 idmap config * : base_tdb = 0 enable core files = false log level = 2 Scott ________________________________ From: samba <samba-bounces at lists.samba.org> on behalf of Rowland Penny via samba <samba at lists.samba.org> Sent: Friday, January 25, 2019 10:49 PM To: samba at lists.samba.org Subject: Re: [Samba] Tr...

...t; winbind use default domain = Yes > winbind enum users = No > winbind enum groups = No > winbind nested groups = Yes > idmap cache time = 0 > idmap config * : backend = tdb > idmap config * : range = 1000 - 200000000 > idmap config * : base_tdb = 0 > enable core files = false > wins server = 10.0.0.1 > guest ok = yes > map to guest = Bad Password > > [bwprinter] > printer name = bwqueue > printable = yes > browseable = yes > guest ok = yes >...

...enum groups = No <-- Default setting winbind nested groups = Yes <-- Default setting idmap cache time = 0 <-- this turns winbind's cache off idmap config * : backend = tdb idmap config * : range = 1000 - 200000000 <-- bad range, you cannot have any local Unix users idmap config * : base_tdb = 0 <-- what is this ?? enable core files = false <-- if Samba crashes, you will not get any core dumps log level = 2 Or to put it another way, it only needs to be this: [global] security = ADS realm = <our domain name> workgroup = <our workgroup name> kerberos method = secrets...

I'm terribly sorry if this isn't the proper place/method by which to get help with troubleshooting Samba errors/issues, but it's the best one I could find. I have an instance of Samba 4.8.3 running on a Centos 7.6 VM server (kernel 3.10.0-957.1.3), along with Centrify 5.5.2-578, that will allow folks to map a shared drive from their Windows 10 machines generally fine, but quite

...enum groups = No <-- Default setting winbind nested groups = Yes <-- Default setting idmap cache time = 0 <-- this turns winbind's cache off idmap config * : backend = tdb idmap config * : range = 1000 - 200000000 <-- bad range, you cannot have any local Unix users idmap config * : base_tdb = 0 <-- what is this ?? enable core files = false <-- if Samba crashes, you will not get any core dumps log level = 2 Or to put it another way, it only needs to be this: [global] security = ADS realm = <our domain name> workgroup = <our workgroup name> kerberos method = secrets...

...e spnego = yes template shell = /bin/bash winbind use default domain = Yes winbind enum users = No winbind enum groups = No winbind nested groups = Yes idmap cache time = 0 idmap config * : backend = tdb idmap config * : range = 1000 - 200000000 idmap config * : base_tdb = 0 enable core files = false syslog = 0 log file = /var/log/samba/log.%m log level = 3 max log size = 50 [data] comment = Local data path = /opt/test/data/ valid users = userx public = no writeable = yes browseable = yes smb error: [2018/09/14 10:42:4...