Displaying 3 results from an estimated 3 matches for "samba08".
Did you mean:
samba01
2017 Jun 26
2
two domain members, different groupIDs
...ould be a breakage for me.
> Using chown will fix things.
Adjusted settings on one server after stopping samba
After a start (testparm OK) the output is still the same.
Do I have to delete some local file or so to reforce new GIDs/UIDs?
I now have:
[global]
realm = ABC.XYZ
server string = samba08
workgroup = XYZ
os level = 65
preferred master = No
logon home =
logon path =
disable spoolss = Yes
load printers = No
printcap name = /dev/null
dedicated keytab file = /etc/krb5.keytab
kerberos method = secrets and keytab
map to guest = Bad User
map untrusted to domain = Yes
security...
2017 Jun 26
0
two domain members, different groupIDs
...>
> Adjusted settings on one server after stopping samba
> After a start (testparm OK) the output is still the same.
>
> Do I have to delete some local file or so to reforce new GIDs/UIDs?
>
> I now have:
>
>
> [global]
> realm = ABC.XYZ
> server string = samba08
> workgroup = XYZ
> os level = 65
> preferred master = No
> logon home =
> logon path =
> disable spoolss = Yes
> load printers = No
> printcap name = /dev/null
> dedicated keytab file = /etc/krb5.keytab
> kerberos method = secrets and keytab
> map to gue...
2017 Jun 22
2
two domain members, different groupIDs
Am 2017-06-22 um 10:44 schrieb Rowland Penny via samba:
>> Can I fix that without breaking things?
>
> If your users have files stored on the domain members, probably not.
I understand that this just creates the need to run some
chown/chgrp-commands after correcting smb.conf and restarting samba?
> Your 'idmap config' block on ALL Unix domain members needs to be
>