similar to: Samba AD member - how to force sync AD attributes?

Displaying 20 results from an estimated 20000 matches similar to: "Samba AD member - how to force sync AD attributes?"

2017 Jun 19
4
New AD user cannot access file share from member server
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:
2017 Jun 19
2
New AD user cannot access file share from member server
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
2017 Jun 19
4
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
2017 Jun 19
2
New AD user cannot access file share from member server
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>
2017 Jun 19
3
New AD user cannot access file share from member server
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 >
2019 Nov 17
2
I can't get Win10 clients to sync time with the DC
On 16.11.2019 23:37, Sonic wrote: > On Sat, Nov 16, 2019 at 10:34 AM Viktor Trojanovic <viktor at troja.ch> wrote: >> I think you may be confusing privileged with unprivileged containers, >> what you describe is perfectly possible with a privileged container but >> would be a bit more complicated to set up with an unprivileged one >> (since the user id's in the
2019 Nov 16
2
I can't get Win10 clients to sync time with the DC
On 16.11.2019 15:17, Sonic wrote: > On Thu, Nov 14, 2019 at 1:56 PM Viktor Trojanovic via samba > <samba at lists.samba.org> wrote: >> I'm running a Samba AD DC v4.9.9 with Windows 10 clients connected to it >> and just noticed that the clients are not synchronizing time with the >> server. I'm not sure why not. >> >> My setup is a bit special in
2019 Feb 10
3
AD Backup Best Practice
On Sun, 10 Feb 2019 at 20:23, Rowland Penny via samba <samba at lists.samba.org> wrote: > On Sun, 10 Feb 2019 20:11:02 +0100 > Viktor Trojanovic <viktor at troja.ch> wrote: > > > On Sun, 10 Feb 2019 at 19:52, Rowland Penny via samba > > <samba at lists.samba.org> wrote: > > > > > On Sun, 10 Feb 2019 19:33:17 +0100 > > > Viktor
2019 Feb 10
2
AD Backup Best Practice
On Sun, 10 Feb 2019 at 19:52, Rowland Penny via samba <samba at lists.samba.org> wrote: > On Sun, 10 Feb 2019 19:33:17 +0100 > Viktor Trojanovic <viktor at troja.ch> wrote: > > > On Sun, 10 Feb 2019 at 17:42, Rowland Penny via samba > > <samba at lists.samba.org> wrote: > > > > > > > > > > > The problem is that a Samba AD DC
2017 Jun 19
1
New AD user cannot access file share from member server
On Mon, 19 Jun 2017 13:51:31 +0200 Viktor Trojanovic <viktor at troja.ch> wrote: > That's correct, I don't have "Unix Attributes" but through the > advanced view I have access to all attributes. the 'Unix Attributes' tab just makes it easier ;-) > > The ldbsearch command is not returning anything in my case, it gives > me 0 records - no matter
2017 Jun 19
4
New AD user cannot access file share from member server
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. My AD is rfc2307 based, so I manually have to add UID's. I did so for the new user, the ID is within range and not in use. I double
2016 Jan 13
1
Samba AD with Microsoft Account
No, that's not normal behavior, and I assume that's what's responsible for those other issues you're experiencing. I suggest you analyze your Samba installation thorougly using the information in the Wiki (there is a lot and in 90% problems can be solved or at least clearly identified with it). If it's just a lab setup, you might consider provisioning a new AD entirely. If you
2017 Jun 19
1
New AD user cannot access file share from member server
On Mon, 19 Jun 2017 15:08:45 +0200 Viktor Trojanovic <viktor at troja.ch> wrote: > Not sure if it matters but here is the AD object of a user with no > issues: > > [root at GJSERVER ~]# ldbsearch -H /var/lib/samba/private/sam.ldb -b > 'ou=office,dc=samdom,dc=example,dc=ch' -s sub > "(&(objectclass=person)(samaccountname=jd))" > # record 1 > dn:
2018 Dec 26
3
After upgrade to 4.9.4, internal DNS no longer working
On Wed, 26 Dec 2018 14:40:10 +0100 Viktor Trojanovic <viktor at troja.ch> wrote: > Hi Rowland, > > Thanks for taking an interest. > > On Wed, 26 Dec 2018 at 14:27, Rowland Penny via samba > <samba at lists.samba.org> wrote: > > > On Wed, 26 Dec 2018 11:43:37 +0100 > > Viktor Trojanovic <viktor at troja.ch> wrote: > > > > > I
2019 Mar 31
3
Van Belle Repo - 4.10 for Bionic
On Sun, 31 Mar 2019 14:29:32 +0200 Viktor Trojanovic <viktor at troja.ch> wrote: > On Sun, 31 Mar 2019 at 14:22, Rowland Penny via samba > <samba at lists.samba.org> wrote: > > > > On Sun, 31 Mar 2019 13:55:18 +0200 > > Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > > > > > On Sat, 30 Mar 2019 at 17:45, L.P.H. van Belle
2018 Dec 26
2
After upgrade to 4.9.4, internal DNS no longer working
On Wed, 26 Dec 2018 11:43:37 +0100 Viktor Trojanovic <viktor at troja.ch> wrote: > I could really use some support with this. I understand it's always > possible to just restore from a backup but the more interesting > question is if something can be done with the data at hand. > Basically, I'm trying to understand how it's possible that a dbcheck > shows no
2018 Dec 23
2
After upgrade to 4.9.4, internal DNS no longer working
On Sun, 23 Dec 2018 10:38:05 +0100 Viktor Trojanovic <viktor at troja.ch> wrote: > I'm not aware of a new folder being created. I can confirm that > /var/lib/samba/private/sam.ldb is the only file with that name on my > system. How could I check if Samba indeed looks up this file and is > not looking for it somewhere else? > > Some additional information that might be
2015 Nov 16
1
Win Clients and DNS
Othere thing. IF you domain name is like domain.tld By default, Windows does not send updates to top-level domains. If thats the case you should change it to a single-lable dns. https://support.microsoft.com/en-us/kb/300684 Greetz, Louis > -----Oorspronkelijk bericht----- > Van: Viktor Trojanovic [mailto:viktor at troja.ch] > Verzonden: maandag 16 november 2015 15:45 > Aan:
2015 Nov 17
3
Permission Issues with GPO
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
2015 Nov 16
1
Win Clients and DNS
Ok, > I am getting the DNS register warning message on > *all* win clients, not just that one. Good info, so, this confirms its not a bug but an incorrect setting. Type ipconfig /all on a pc. Post the output, i suspect, incorrect dnsdomain or dns search domain. Also. Check if the PTR records are set to the correct server ips. This does not change on its own. Ldbsearch from below