similar to: Strange problem with samba-tool dns query ...

On Fri, 2024-04-05 at 08:04 +0100, Rowland Penny via samba wrote: > On Fri, 05 Apr 2024 08:06:10 +0200 > PaLi via samba <samba at lists.samba.org> wrote: > > > Hello > > > > I have a strange problem on a brand new installation of samba AD > > (samba-4.19.5 on Fedora 39). > > > > Domain controller is dc01.some.domain.org > > Secondary

On Fri, 05 Apr 2024 15:38:23 +0200 pavel.lisy at gmail.com wrote: > On Fri, 2024-04-05 at 08:04 +0100, Rowland Penny via samba wrote: > > On Fri, 05 Apr 2024 08:06:10 +0200 > > PaLi via samba <samba at lists.samba.org> wrote: > > > > > Hello > > > > > > I have a strange problem on a brand new installation of samba AD > > >

On Fri, 05 Apr 2024 08:06:10 +0200 PaLi via samba <samba at lists.samba.org> wrote: > Hello > > I have a strange problem on a brand new installation of samba AD > (samba-4.19.5 on Fedora 39). > > Domain controller is dc01.some.domain.org > Secondary (replicated) controller is dc02.some.domain.org > > After clean installation all basic tests seams to be ok.

On Fri, 2024-04-05 at 15:00 +0100, Rowland Penny via samba wrote: > On Fri, 05 Apr 2024 15:38:23 +0200 > pavel.lisy at gmail.com?wrote: > > > On Fri, 2024-04-05 at 08:04 +0100, Rowland Penny via samba wrote: > > > On Fri, 05 Apr 2024 08:06:10 +0200 > > > PaLi via samba <samba at lists.samba.org> wrote: > > > > > > > Hello > > >

Hi! I have a question about order in dcs is /etc/resolv.conf , my configuration: DC01: /etc/resolv.conf IP DC02 IP DC01 DC02 /etc/resolv.conf IP DC01 IP DC02 https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory#DNS_Configuration_on_Domain_Controllers --- However this setting causes the error: samba_dnsupdate --verbose --all-names dns_tkey_negotiategss:

On Sat, 8 Jun 2024 17:05:25 +0200 Ronny Preiss via samba <samba at lists.samba.org> wrote: > Hi, > > I have two problems with my 2 Samba AD-DC. I don't know if the two > problems are related. > Both domain controllers show the same error pattern for problem 1.The > second problem only occurs with the second domain controller. > The domain itself seems to work and

Am 26.09.18 um 20:42 schrieb Rowland Penny via samba: > On Thu, 27 Sep 2018 06:29:26 +1200 > Andrew Bartlett <abartlet at samba.org> wrote: > >> On Wed, 2018-09-26 at 14:47 +0100, Rowland Penny via samba wrote: >>> On Wed, 26 Sep 2018 15:28:42 +0200 >>> Daniel Jordan <d.jordan at gfd.de> wrote: >>> >>>> >>>> dc01:~#

Hi, I have two problems with my 2 Samba AD-DC. I don't know if the two problems are related. Both domain controllers show the same error pattern for problem 1.The second problem only occurs with the second domain controller. The domain itself seems to work and be in order. Does someone know where this comes from and how to solve it? ## Issue 1 ## By doing my random log checking, I saw the

Hello, I inherited an Active directory in Windows in Spanish, after a lot of work I was able to do the first synchronization to a DC in Samba. Now I am at the stage that I want to remove Windows, but previously I want to remove Windows. I am trying to add another DC in Samba to advance and I am presented with the following problem. I feel lost with these errors. root at DC01:~# samba-tool fsmo

Is it possible to specify a list of DCs for Samba to use, rather than have it look them up dynamically via DNS? I have an issue with Kerberos, Samba, and SSSD where my machines stop authenticating after a period of time – preAuthentication errors, etc. I suspect it's because of a "DC mismatch" between the three. Because we have numerous DCs all over the world, I specifically

Hi Epsilon, I think the issue here is with localization support in Samba. You "Default-First-Site" in Spanish MS-AD is translated (as it is in French AD), and it seems that it looks for the following site name during the join: CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=conylec,DC=local while it should be trying to create the entry in the following site name:

Hi all, I have just added a DC to our existing AD. Join did work without any error messages but now I have recognized that only inbound replication from old DCs is working outbound list is empty. Samba version is: Version 4.2.0pre1-GIT-cff0f8e here is the output of samba-tool drs showrepl: DSA Options: 0x00000001 DSA object GUID: 94534f65-5d06-41f5-844d-a58a0bc03c93 DSA invocationId:

To get the question of why new servers, this one I'm using has hardware whose remaining life is measured in days. The elastic bands and sticky tape it is held together with won't hold for much longer. I'm using it to build and test a new environment, but then I need to migrate that onto something with a little more vitality before bringing it into production (in the next 56 hours). As

You believe that SSSD is bypassing Samba entirely and going direct to Kerberos? That’s possible. At the moment, to the best of my understanding, Samba is only being used to join the domain. There are no file/printer/etc. shares happening; this is just basic domain join/membership and keytab generation and after that it’s done. The question was still specific to Samba itself: can I specify the DCs

Thank you everyone for your help. I corrected my resolv.conf files as Peter Milesson suggested and then had to take a number of extra steps so now things are looking a little better. In case it helps anyone else in the future, here's what I found (plus I am now having problems resolving internal addresses). As far as I can see, the setup on both servers is identical (except they use their own

I have created a DC01 & DC02 with Louis's (generation one) scripts. I have noticed, during some testing that 'pam-auth-update' shows PAM profiles Kerberos, Unix & Winbind listed on DC01. The DC02 only lists Kerberos & Unix and Winbind is missing. I thought that the two DC's were suppose to be identical? If DC01 goes "down" DC02 cannot carry a winbind

I found adcli a little too late; I plan to use it in the future but for the time being I just deployed 16 VMs using Samba so we’re going to keep that for now! Also, the rest of what I wrote can be disregarded – I figured out exactly why my hosts were failing to authenticate after a period of time. It’s too stupid to admit publicly. On 8/23/16, 3:50 PM, "samba on behalf of Kris Lou via

On Thu, 2018-09-27 at 09:04 +0100, Rowland Penny via samba wrote: > On Thu, 27 Sep 2018 07:46:40 +0200 > Daniel Jordan <d.jordan at gfd.de> wrote: > > > > > > Hello  Andrew and Rowland, > > > > here's the ldbsearch output from both domain controllers: > > > > > > dc01:~# ldbsearch -H /var/lib/samba/private/sam.ldb  > >

On Wed, 2018-09-26 at 14:47 +0100, Rowland Penny via samba wrote: > On Wed, 26 Sep 2018 15:28:42 +0200 > Daniel Jordan <d.jordan at gfd.de> wrote: > > > > > > > dc01:~# ldbsearch -H /var/lib/samba/private/sam.ldb  > > '(objectClass=domain)' objectSid > > # record 1 > > dn: DC=xx,DC=xx,DC=xx > > objectSid:

We are using Samba-4.1.11. I can run gpupdate /force without error on my machine. H:\>type \\dc01.mediture.dom\SysVol\mediture.dom\Policies\{77F82F0F-AE2B-42F3-B173-D42F4BEEC0BA}\gpt.ini [General] Version=65551 displayName=New Group Policy Object H:\>type \\dc02.mediture.dom\SysVol\mediture.dom\Policies\{77F82F0F-AE2B-42F3-B173-D42F4BEEC0BA}\gpt.ini [General] Version=65551 displayName=New