similar to: New AD user cannot access file share from member server

On 6/19/2017 7:51 AM, Viktor Trojanovic via samba wrote: > That's correct, I don't have "Unix Attributes" but through the advanced > view I have access to all attributes. > > The ldbsearch command is not returning anything in my case, it gives me 0 > records - no matter which user I try, even the Administrator. I checked the > command several times to make sure

On 6/19/2017 9:12 AM, Viktor Trojanovic via samba wrote: > On 19 June 2017 at 14:56, Rowland Penny via samba <samba at lists.samba.org> > wrote: > >> On Mon, 19 Jun 2017 14:46:34 +0200 >> Viktor Trojanovic <viktor at troja.ch> wrote: >> >>> On 19 June 2017 at 14:20, lingpanda101 via samba >>> <samba at lists.samba.org> wrote:

On Mon, 19 Jun 2017 14:46:34 +0200 Viktor Trojanovic <viktor at troja.ch> wrote: > On 19 June 2017 at 14:20, lingpanda101 via samba > <samba at lists.samba.org> wrote: > > > On 6/19/2017 7:51 AM, Viktor Trojanovic via samba wrote: > > > >> That's correct, I don't have "Unix Attributes" but through the > >> advanced view I have

On Mon, 19 Jun 2017 12:38:09 +0200 Viktor Trojanovic <viktor at troja.ch> wrote: > Here is the DC's smb.conf: > > > [global] > workgroup = SAMDOM > realm = SAMDOM.EXAMPLE.COM > netbios name = DC > interfaces = lo br-lxc > bind interfaces only = Yes > server role = active directory domain controller >

On Mon, 19 Jun 2017 02:24:50 +0200 Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > I run a very small Samba AD, consisting of a Samba AD DC and a Samba > AD Member Server, acting as file server. > > Today, I added a new user to the AD but I simply can't manage to get > access to the file server - only for this user, all others are > working fine. >

I missed to mention it. But I actually did try changing the CN=users to OU=ouname, and even leaving it out. I don't know why it didn't return any results before, it does now - see my reply to James. On 19 June 2017 at 14:30, Rowland Penny via samba <samba at lists.samba.org> wrote: > On Mon, 19 Jun 2017 08:20:35 -0400 > lingpanda101 via samba <samba at lists.samba.org>

Hi Viktor, I didn't go through all the conversations and I'm not sure if this will > be of any help, I just wanted to inform that I've been using mapped > drives with Windows 10 for ages and never had the problems you > described. I also never added or changed the "smb encrypt" option. My > Samba file server (AD member) was set up pretty much the way as is >

On 17/11/15 16:57, Viktor Trojanovic wrote: > Hi Mathias, > > Thanks for replying. It seems you're describing the situation on the > AD DC. Computer and user mode access to my DC works fine and without > any issues but I can't access the shares of my *member* server *in > computer mode*. In user mode, it all works just fine. > > Viktor > > On 17.11.2015

On 17/11/15 17:33, Viktor Trojanovic wrote: > [global] > > netbios name = FILESERVER > workgroup = SAMDOM > security = ADS > realm = SAMDOM.EXAMPLE.COM > dedicated keytab file = /etc/krb5.keytab > kerberos method = secrets and keytab > > username map = /etc/samba/samba_usermap > > idmap config *:backend = tdb > idmap config *:range =

Let me guess. You accessing your server like : \\servername\netlogon of \\servername\sysvol Well thats protected by windows these these days. Try with \\servername.domain.tld\netlogon or \\servername.domain.tld\sysvol Does that work? Yes, There is a whole chaper of this on the list somewhere.. Best is to read howto override this. https://adsecurity.org/?p=1405 and for you

Hi Rowland, Thanks for replying again. On 13 May 2018 at 18:12, Rowland Penny via samba <samba at lists.samba.org> wrote: > On Sun, 13 May 2018 17:39:39 +0200 > Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > > [...] > > > username map = /etc/samba/samba_usermap > > What is in the 'samba_usermap' ? > !root =

Here are my (little) view regarding shares accesses. I write that to clarify things. And it could really be of-topic as Louis seems to have gave solution. There are 2 levels of authorisation for accessing shares: the share level and FS level. For Sysvol I would keep everyone or replace it by "authenticated users" in paranoid mode as the latter refuse non-authenticated users. They are

I'm running a pure Samba AD with one Samba AD DC and one member server, both on version 4.8.1. AD is based on idmap_ldb with rfc2307 but since I'm using (only) Win10 clients, I have to assign all group and user numbers manually. This set up is not new and it's been working for years already, and still does. Yesterday, however, I noticed that I gave two users the same uidNumber by

Setup: Samba AD DC and Samba AD Member Server, Win10 clients only. Samba version 4.8.1 Has something changed recently in the way ACL's are supposed to work? My existing shares work just fine but any ALC changes I make using Windows are ignored in Samba. For example, I'm creating a new folder in Windows inside an existing share and I add user User1 or group Group1 in the security tab.

On 16.11.2015 14:44, Rowland Penny wrote: > On 16/11/15 13:25, Ole Traupe wrote: >> >> >> Am 16.11.2015 um 14:06 schrieb Viktor Trojanovic: >>> >>> >>> On 16.11.2015 13:48, Viktor Trojanovic wrote: >>>> See replies below >>>> >>>> On 16.11.2015 12:39, Rowland Penny wrote: >>>>> On 16/11/15 11:19,

On 16.11.2015 15:08, Rowland Penny wrote: > On 16/11/15 14:00, Viktor Trojanovic wrote: >> >> >> On 16.11.2015 14:44, Rowland Penny wrote: >>> On 16/11/15 13:25, Ole Traupe wrote: >>>> >>>> >>>> Am 16.11.2015 um 14:06 schrieb Viktor Trojanovic: >>>>> >>>>> >>>>> On 16.11.2015 13:48,

On 27.10.2015 11:17, Rowland Penny wrote: > On 27/10/15 09:34, Viktor Trojanovic wrote: >> >> >> On 27.10.2015 09:05, Rowland Penny wrote: >>> On 26/10/15 22:35, Viktor Trojanovic wrote: >>>> >>>> >>>> On 26.10.2015 23:03, Rowland Penny wrote: >>>>> On 26/10/15 21:38, Viktor Trojanovic wrote: >>>>>>

When I provisioned a new AD domain, I used the wrong network interface in the provisioning command. samba-tool domain provision --option="interfaces=lo eth2" --option="bind interfaces only=yes" --use-rfc2307 --use-xattrs=yes --interactive I should have used eth1 instead of eth2. The latter had no IP address attached to it so that there is no (correct) A record in the

I just did a restore of a backed up Samba DC and as feared, I'm running into issues that have kept me for hours on this already. Everything seems fine at first sight. The daemon (samba-ad-dc, 4.10, on Ubuntu Bionic) starts properly and without error messages in any log, even with increased level 3. Most of the typical testing and troubleshooting commands give the correct output.

On 27.10.2015 09:05, Rowland Penny wrote: > On 26/10/15 22:35, Viktor Trojanovic wrote: >> >> >> On 26.10.2015 23:03, Rowland Penny wrote: >>> On 26/10/15 21:38, Viktor Trojanovic wrote: >>>> I joined a Samba AD member server (file server) to a Samba AD DC. >>>> This seems to have worked. However, if I try to access the file >>>>