>I think your problem is being caused by the OS not knowing your users >and groups, have a look here: > >https://wiki.samba.org/index.php/Configuring_Winbindd_on_a_Samba_AD_DC > >But before you do that, UPGRADE your Samba version. I said that there >have been a lot of improvements, one of them is the 'winbind' built >into the 'samba' binary has been replaced by the same separate >'winbindd' binary used on a domain member, this by its self is worth >upgrading for. > >RowlandHi, I think I successfully upgraded to the latest version. I see Winbindd being started as a part of the samba process. As the Winbindd wiki page said "To run Winbindd on a Samba Active Directory (AD) domain controller (DC), in most cases no configuration in the smb.conf file is required.", I changed nothing in the smb.conf file, exept for adding a share. Again, this share does not show the Security tab. I have not yet added a pointer record for the server, but I doubt that will be related. Do you have pointers as to where the problem might be? Cheers, BC
>Hi, > > >I think I successfully upgraded to the latest version. I see Winbindd being started as a part of the samba process. As the Winbindd wiki >page said "To run Winbindd on a Samba Active Directory (AD) domain controller (DC), in most cases no configuration in the smb.conf file >is required.", I changed nothing in the smb.conf file, exept for adding a share. > >Again, this share does not show the Security tab. > >I have not yet added a pointer record for the server, but I doubt that will be related. > >Do you have pointers as to where the problem might be? > > >Cheers, > > >BCAdding a pointer record for the server didn't help either. I am going to test another Windows PC now to see if the problem exists there as well. BC
>Adding a pointer record for the server didn't help either. I am going to test another Windows PC now to see if the problem exists there as well. > > >BCThe other Windows machine has the same issue. I have one symptom more now: when connecting to the DC, I get a "1745" error message in Windows. Will look that one up. If someone has any suggestions, please speak up. Upgrading Samba did not help, so I am looking for other alleys, Cheers, BC
On Mon, 6 Mar 2017 19:10:11 +0100 Bart Coninckx <info at bitsandtricks.com> wrote:> > Adding a pointer record for the server didn't help either. I am going > to test another Windows PC now to see if the problem exists there as > well.This is strange, don't think I have ever had this problem. Can you post the following files from the Samba AD DC: /etc/hosts /etc/hostname /etc/resolv.conf /etc/krb5.conf /etc/nsswitch.conf Can you also tell us the FQDN and ipaddress of the DC. Rowland
>Adding a pointer record for the server didn't help either. I am going to test another Windows PC now to see if the problem exists there as well. > > >BCI just realized that I omitted an important piece of information and that is that I am using a separate EXT4 volume for my shares. I just did a test and it seems that shares on the same volume as sysvol and netlogon funtion as expected but shares on the second volume have the issue. I just mounted that second volume with explicit acl and user_xattr options in fstab, but this makes no difference. BC