search for: membersrv1

...to troubleshoot and solve that problem. Any help really really appreciated. Scenario: ========= I am using Samba 4.1.12/sernet on DC1 (172.19.100.1) and DC2 (172.19.100.2) with default [netlogon] and [sysvol] share only. I installed an additional samba4 server with fileserving role which is called MEMBERSRV1 (172.19.100.3), which is serving the [profiles], [home] and [printer] stuff shares. For setting up the member server, I relied on "https://wiki.samba.org/index.php/Setup_a_Samba_AD_Member_Server#Set_up_a_basic_smb.conf". I also am using NIS extensions on my AD according the wiki tutorials...

...d be really awesome if this step could be done magically without extra intervention. 2.) Let's say I am creating the user "John Doe". During the creation process, in the [Profile] tab I can choose to connect the home share of that particular user, for example: "Connect Z:\ to \\membersrv1\home\%username%" after I click the [OK] or [Apply] button, the ADUC tool automatically is creating on-the-fly the directory "\\membersrv1\home\johndoe" which works fine. That is a neat feauture but in my opinion it has one big disadvantage ==> the directory .\johndoe on the given...

...e? (https://wiki.samba.org/index.php/Setup_a_Samba_AD_Member_Server#Setting_up_PAM_authentication) I tried that. I didn't create the symlink as shown on the tutorial (ln -s /usr/local/samba/lib/security/pam_winbind.so /lib64/security/), because I realized that I have a file called "root at membersrv1:/lib/x86_64-linux-gnu/security/pam_winbind.so" which I think comes from the Sernet Samba 4.1.12 package (please correct me if I'm wrong). Then I tried to modify the "/etc/pam.d/sshd" according the tutorial, that's how my "/etc/pam.d/sshd" looked like afterwards: ===...

...see the [home] share. I can change and apply the settings as described on the Wiki. But as soon as I click the tab, everything is greyed out, I cannot change anyting there. In my understanding that is what I would expect, because there are no rights for "MYDOM\johndoe" on the path "membersrv1:/srv/samba4_data/home". [root at membersrv1:/srv/samba4_data$ ls -ld home drwxr-xr-x 2 root root 4096 Okt 21 19:11 home [root at membersrv1:/srv/samba4_data$ getfacl home # file: home # owner: root # group: root user::rwx group::r-x other::r-x How should I be able to edit the security sett...

...t; is displayed correctly. But when I run "getent group" I don't get the group "Domain Users" although this group also has a gid assigned. The strange thing is that "getent group 'Domain Users'" or "getent group 10000" works fine though: [root at membersrv1:~$ getent group 'Domain Users' domain users:x:10000: [root at membersrv1:~$ getent group 10000 domain users:x:10000: Why does "getent group" *NOT* returning the AD domain groups, that certainly have a GID assigned as UNIX attribute? I installed a new member server with samba 4.1....

...full access (this folder, subfolder and files) "SYSTEM" have full access (this folder, subfolder and files) "Creator-Owner" have full access (subfolders and files) Afterwards, when I check the ACL settings on the linux prompt at my member server I get following output: root at membersrv1:~# getfacl /srv/samba/home # file: home # owner: root # group: root user::rwx user:root:rwx group::--- group:root:--- group:domain\040admins:rwx mask::rwx other::--- default:user::rwx default:user:root:rwx default:group::--- default:group:root:--- default:group:domain\040admins:rwx default:mask::r...