search for: mydomainuser

Thanks Rowland. 'getent passwd mydomainuser' does return the correct (new, sssd) UID e.g. 1514701182 In my /etc/nsswitch.conf I have: passwd: files sss group: files sss The problem is that when I create a file from a client machine into a samba share on this server, e.g. creating the file \\servername\sharename\newfile.txt, th...

Dear Samba Users, I set a samba share (4.8.1) on a linux (centos 7) as server member ; authentication is done against a AD win 2012 R2 server through winbind. I thought authentication was using kerberos, but I checked log and found : Auth: [SMB2,(null)] user [MYDOMAIN]\[mydomainuser] at [mar., 11 juin 2019 10:21:42.000927 -03] with [NTLMv2] status [NT_STATUS_OK] workstation [CANONDCE0BD] Below, part of my smb.cnf : security = ads realm = MYDOMAIN workgroup = MYDOMAIN kerberos method = secrets and keytab server signing = mandatory client signing = mandatory How can I tel...

...d_mapping = False" in sssd.conf you'll get the same uid on both (that's how I use it anyway). See the manpage of sssd-ad for more information on the ldap_id_mapping param. I hope this helps, Regards, Roel Jonathan Hunter writes: > Thanks Rowland. > > 'getent passwd mydomainuser' does return the correct (new, sssd) UID > e.g. 1514701182 > > In my /etc/nsswitch.conf I have: > passwd: files sss > group: files sss > > The problem is that when I create a file from a client machine into a > samba share on this server, e.g. creating the file...

...the contrary, comment the idmap_ldb:use rfc2307. > See the manpage of sssd-ad for more information on the ldap_id_mapping > param. > > I hope this helps, > > Regards, Roel > > > Jonathan Hunter writes: > >> Thanks Rowland. >> >> 'getent passwd mydomainuser' does return the correct (new, sssd) UID >> e.g. 1514701182 >> >> In my /etc/nsswitch.conf I have: >> passwd: files sss >> group: files sss >> >> The problem is that when I create a file from a client machine into a >> samba share on this...

Dear Samba Users, I set 2 samba shares : 1. with the name [groups] /pathtomyshare/groups 2. for each domain users [homes] /home In Windows, I can see with the windows explorer my shares : groups (\\myserver) (V:) mydomainuser (\\myserver\homes) (U:) Why for [groups] is only indicated \\myserver and for [homes] is indicated \\myserver\homes ? Is there a way to change it ? I would only show \\myserver for the both shares? Best Regards, Edouard

Hi, Some advice, if I may.. I have two Samba4 domain controllers, that I recently switched to using sssd (against these same DCs) for UNIX user authentication - this part works perfectly. However, I am using one of these as a Samba file server also. When I create a file via a SMB share, the UNIX UID the file is owned by is the old 'winbind' UID (e.g. 3000007) rather than the new

...samba share (4.8.1) on a linux (centos 7) as server member ; >> authentication is done against a AD win 2012 R2 server through winbind. >> >> I thought authentication was using kerberos, but I checked log and found >> : >> >> Auth: [SMB2,(null)] user [MYDOMAIN]\[mydomainuser] at [mar., 11 juin >> 2019 >> 10:21:42.000927 -03] with [NTLMv2] status [NT_STATUS_OK] workstation >> [CANONDCE0BD] >> >> Below, part of my smb.cnf : >> >> security = ads >> >> realm = MYDOMAIN >> workgroup = MYDOMAIN > Why is your work...

...sers, >> >> I set 2 samba shares : >> 1. with the name [groups] >> /pathtomyshare/groups >> >> 2. for each domain users [homes] >> /home >> >> In Windows, I can see with the windows explorer my shares : >> groups (\\myserver) (V:) >> mydomainuser (\\myserver\homes) (U:) >> >> Why for [groups] is only indicated \\myserver and for [homes] is >> indicated \\myserver\homes ? >> >> Is there a way to change it ? I would only show \\myserver for the >> both shares? >> >> Best Regards, >> >...

I've added it in the way as described in 2. smbpasswd -r XXX -j TELIT -U mydomainuser and I got the message successfully joined domain telit (or something similar) XXX - here this is the same server, which I use with security = server and this is the PDC of the win2k domain I don't know what kind of account has the machine in the win2k domain - as I said I don't have any...

...samba share (4.8.1) on a linux (centos 7) as server member ; >> authentication is done against a AD win 2012 R2 server through winbind. >> >> I thought authentication was using kerberos, but I checked log and found >> : >> >> Auth: [SMB2,(null)] user [MYDOMAIN]\[mydomainuser] at [mar., 11 juin >> 2019 >> 10:21:42.000927 -03] with [NTLMv2] status [NT_STATUS_OK] workstation >> [CANONDCE0BD] >> >> Below, part of my smb.cnf : >> >> security = ads >> >> realm = MYDOMAIN >> workgroup = MYDOMAIN > Why is your work...

Hi Edouard, > I set a samba share (4.8.1) on a linux (centos 7) as server member ; > authentication is done against a AD win 2012 R2 server through winbind. > > I thought authentication was using kerberos, but I checked log and found : > > Auth: [SMB2,(null)] user [MYDOMAIN]\[mydomainuser] at [mar., 11 juin 2019 > 10:21:42.000927 -03] with [NTLMv2] status [NT_STATUS_OK] workstation > [CANONDCE0BD] CANONDCE0BD -> isn't that a copier doing scan2folder? If it is the case, please know that most of copier cannot do Kerberos auth properly. Actually you can already be happy...

...a shares : >>> 1. with the name [groups] >>> /pathtomyshare/groups >>> >>> 2. for each domain users [homes] >>> /home >>> >>> In Windows, I can see with the windows explorer my shares : >>> groups (\\myserver) (V:) >>> mydomainuser (\\myserver\homes) (U:) >>> >>> Why for [groups] is only indicated \\myserver and for [homes] is >>> indicated \\myserver\homes ? >>> >>> Is there a way to change it ? I would only show \\myserver for the >>> both shares? I can only think tha...

...any windows client as it asks for username and password (the share is set to public = no). Smbstatus shows user nobody is trying to connect. Now the strange thing: smbclient works perfectly. I set up a share on my computer with access only to my domain user. Doing a 'smbclient //mypc/share -U mydomainuser' works perfectly. I don't know what could possibly be wrong, but I guess that's something to do with PAM. I configured samba with the options --with-pam --with-smbmount --with-acl-support --with-winbind --with-quotas I set up /etc/pam.d/passwd as follows: auth required /li...

...any windows client as it asks for username and password (the share is set to public = no). Smbstatus shows user nobody is trying to connect. Now the strange thing: smbclient works perfectly. I set up a share on my computer with access only to my domain user. Doing a 'smbclient //mypc/share -U mydomainuser' works perfectly. I don't know what could possibly be wrong, but I guess that's something to do with PAM. I configured samba with the options --with-pam --with-smbmount --with-acl-support --with-winbind --with-quotas I set up /etc/pam.d/passwd as follows: auth required /li...

...any windows client as it asks for username and password (the share is set to public = no). Smbstatus shows user nobody is trying to connect. Now the strange thing: smbclient works perfectly. I set up a share on my computer with access only to my domain user. Doing a 'smbclient //mypc/share -U mydomainuser' works perfectly. I don't know what could possibly be wrong, but I guess that's something to do with PAM. I configured samba with the options --with-pam --with-smbmount --with-acl-support --with-winbind --with-quotas I set up /etc/pam.d/passwd as follows: auth required /li...

...any windows client as it asks for username and password (the share is set to public = no). Smbstatus shows user nobody is trying to connect. Now the strange thing: smbclient works perfectly. I set up a share on my computer with access only to my domain user. Doing a 'smbclient //mypc/share -U mydomainuser' works perfectly. I don't know what could possibly be wrong, but I guess that's something to do with PAM. I configured samba with the options --with-pam --with-smbmount --with-acl-support --with-winbind --with-quotas I set up /etc/pam.d/passwd as follows: auth required /li...

...any windows client as it asks for username and password (the share is set to public = no). Smbstatus shows user nobody is trying to connect. Now the strange thing: smbclient works perfectly. I set up a share on my computer with access only to my domain user. Doing a 'smbclient //mypc/share -U mydomainuser' works perfectly. I don't know what could possibly be wrong, but I guess that's something to do with PAM. I configured samba with the options --with-pam --with-smbmount --with-acl-support --with-winbind --with-quotas I set up /etc/pam.d/passwd as follows: auth required /li...