> Hello list, i did try to assign permission to folder for some users in > samba4 as BDC, for example > chown sandy Temp/ > chown: invalid user: `sandy' > > when sandy is a users create in active directory, why sayme that sandy is > invalid users???? >It sounds like you do not have your nsswitch setup to use winbind. John
Hello list, i did try to assign permission to folder for some users in samba4 as BDC, for example chown sandy Temp/ chown: invalid user: `sandy' when sandy is a users create in active directory, why sayme that sandy is invalid users????
El 02/04/12 16:52, sandy.napoles at eccmg.cupet.cu escribi?:> Hello list, i did try to assign permission to folder for some users in > samba4 as BDC, for example > chown sandy Temp/ > chown: invalid user: `sandy' > > when sandy is a users create in active directory, why sayme that sandy is > invalid users???? > >Is sandy defined in AD with Unix attributes? e.g. what is his uid/gid? Cheers, Steve
Hello list, I solved my problem. 1- run as root in samba4 server ln -s /usr/local/samba/lib/libnss_winbind.so.2 /lib/libnss_winbind.so ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2 2- Edit nsswitch.con y put only the follow line passwd: files winbind group: files winbind shadow: files 3- run this command /usr/local/samba/bin/wbinfo -p you can watch Ping to winbindd succeeded when i run chown pepe Trabajo/ everything is ok, where pepe is a users in the active directory
Hello list, here is the procedure to permit user create in active
directory login samba4 server, using pam_winbind
Installing and configuring
Ensure that you built Samba 4 with libpam0g-dev installed on your system.
If not, install the PAM development libraries and re-compile Samba 4 from
the ./configure.developer stage. Install pam_winbind.so in the usual
place:
1 ln -s /usr/local/samba/lib/pam_winbind.so /lib/security
Ckeck you have a similar entry in smb.conf:
[global]
template shell = /bin/bash
2. Restart your samba 4 server
Note: The following actions can cause you not to be able to connect to
your system if you do something wrong. You are invitated to make a backup
of your previous configuration and to have a spare connection to the
server as root to be able to restore them in case of problem.
3. Files to modify:
/etc/pam.d/common-auth
Add this line before pam_unix.so:
auth sufficient pam_winbind.so
Also add the option use_first_pass to the pam_unix.so line
/etc/pam.d/common-account
Add this line before pam_unix.so:
account sufficient pam_winbind.so
/etc/pam.d/common-session
Add these lines before any other session line:
session required pam_mkhomedir.so
session required pam_winbind.so
Testing
Check that getent passwd return a correct entry:
getent passwd
...
ssh administrator at 10.0.100.1
...
It's important that the shell must be a real shell (and not /bin/false).
Check that you can connect as a non domain user (ie. root or any other
account that used before