similar to: Member server: Failed to join domain: failed to find DC for

On Sat, 8 Jun 2024 17:41:57 +0100 Luis Peromarta via samba <samba at lists.samba.org> wrote: > All, > > Doing some testing with 4.20.1 on a member server. I have no > explanation for this. > > ?Member? member is just a test machine, I joined to domain *with* net > ads join, no issues. A few minutes later ... > > root at member:/etc/samba# net ads leave domain

LP On Jun 8, 2024 at 17:56 +0100, samba at lists.samba.org <samba at lists.samba.org>, wrote: > > I have never run those commands like that, I normally run 'net ads join > -Uadministrator' or 'net ads leave -Uadministrator', I have never > specified the domain. I did specify domain out of frustration I think. More test as per your inputs: (net ads join fails)

On Sat, 8 Jun 2024 18:07:55 +0100 Luis Peromarta <lperoma at icloud.com> wrote: > > LP > On Jun 8, 2024 at 17:56 +0100, samba at lists.samba.org > <samba at lists.samba.org>, wrote: > > > > I have never run those commands like that, I normally run 'net ads > > join -Uadministrator' or 'net ads leave -Uadministrator', I have > >

Agree. But I don?t think it is. See: root at member:/# cat /etc/hostname member root at member:/# cat /etc/hosts 127.0.0.1 localhost 192.168.3.1 member.mad.mater.int member root at member:/# cat /etc/resolv.conf search mad.mater.int nameserver 192.168.0.12 -> DC1 nameserver 192.168.0.13 -> DC2 nameserver 192.168.0.14 -> DC3 nameserver 192.168.0.62 -> DC4 root at member:/# cat

On Sun, 9 Jun 2024 10:20:46 +0100 Luis Peromarta <lperoma at icloud.com> wrote: > Agree. > > But I don?t think it is. See: > > root at member:/# cat /etc/hostname > member > > root at member:/# cat /etc/hosts > 127.0.0.1 localhost > 192.168.3.1 member.mad.mater.int member > > root at member:/# cat /etc/resolv.conf > search mad.mater.int >

I have restored the container from an early snapshot. This has all bits installed, but no config and not joined. I needed -U with a username. By the way my network is a /22 root at member:~# samba-tool dns zonelist awing.mad.mater.int --reverse -U?MAD\luis" WARNING: Using passwords on command line is insecure. Installing the setproctitle python module will hide these from shortly after

Mmm? strange ? Or is this what you were expecting ? root at member:/# net rpc rights list privileges SeDiskOperatorPrivilege -Uadministrator Password for [MAD\administrator]: Could not connect to server 127.0.0.1 The username or password was not correct. Connection failed: NT_STATUS_LOGON_FAILURE root at member:/# net rpc rights list privileges SeDiskOperatorPrivilege -Uadministrator Password

On Sun, 9 Jun 2024 13:29:15 +0100 Luis Peromarta via samba <samba at lists.samba.org> wrote: > Hi there, > > I wonder if this is relevant on Active Directory or maybe is a thing > of older NT4 style domains. > > https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs#Granting_the_SeDiskOperatorPrivilege_Privilege > > I have tried setting up a member

On 14/04/2023 13:40, Luis Peromarta via samba wrote: > Not that I have any problem (that I am aware) but the output of the host command only shows (showed) 2 out of??3 DCs in my network. > > I have created the missing one. All other entries in the DNS tree shows all 3 DCs for each service. The only missing was this one. > > host -t SRV _ldap._tcp.pdc._msdcs.mad.mater.int >

On 14/04/2023 14:05, Luis Peromarta via samba wrote: > In my particular case, I was missing a record. It?s been recreated and all looks and feels fine. > > LP > On 14 Apr 2023 at 14:47 +0200, samba at lists.samba.org, wrote: >> >> Just remove the wrong records with samba-tool. You posted this: host -t SRV _ldap._tcp.pdc._msdcs.mad.mater.int

LP On Nov 7, 2023 at 18:06 +0100, Andrey Repin via samba <samba at lists.samba.org>, wrote: > > > AD DC configuration: > > # Global parameters > [global] > auto services = homes > client ldap sasl wrapping = sign > dns forwarder = 192.168.1.12 > dos charset = CP866 > logging = systemd > log level = 1 > netbios name = DC2 > panic action =

All, In the past few days I have been experimenting with the mappings in Samba servers. Today is the DC day. Procedure: In my setup, I provisioned with rfc2307 schema. In fairness everyone should, as it?s free, and you can later use it or not. 'idmap_ldb:use rfc2307 = yes' is in the smb.conf , it?s there by default when the domain is provisioned with rfc2307 - this reads gidNumbers and

On Sun, 9 Jun 2024 18:52:39 +0100 Luis Peromarta via samba <samba at lists.samba.org> wrote: > Update: > > I have revoked the privilege to BUILIN\Administratos. As before, no > root mapping. > > root at member:/# net rpc rights revoke "BUILTIN\Administrators" > SeDiskOperatorPrivilege -U "MAD\luis" Password for [MAD\luis]: > Successfully revoked

Update: I have revoked the privilege to BUILIN\Administratos. As before, no root mapping. root at member:/# net rpc rights revoke "BUILTIN\Administrators" SeDiskOperatorPrivilege -U "MAD\luis" Password for [MAD\luis]: Successfully revoked rights. root at member:/# net rpc rights list privileges SeDiskOperatorPrivilege -Uluis Password for [MAD\luis]: SeDiskOperatorPrivilege:

On Sun, 9 Jun 2024 16:53:30 +0100 Luis Peromarta via samba <samba at lists.samba.org> wrote: > Mmm? strange ? Or is this what you were expecting ? No > > root at member:/# net rpc rights list privileges SeDiskOperatorPrivilege > -Uadministrator Password for [MAD\administrator]: > Could not connect to server 127.0.0.1 > The username or password was not correct. >

On 14/04/2023 12:13, Lorenzo Milesi via samba wrote: > >> That all smells quite similar to what I were seeing >> here before, and what someone else were seeing too, >> all with 4.17[.4]. This famouse WERR_FILE_NOT_FOUND >> error too. > > We upgraded one more domain, and in the hope to avoid this error, we remained on 4.16. So we deployed a new 4.16.9 DC, joined,

On Mon, 10 Jun 2024 08:33:13 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Sun, 9 Jun 2024 18:52:39 +0100 > Luis Peromarta via samba <samba at lists.samba.org> wrote: > > > Update: > > > > I have revoked the privilege to BUILIN\Administratos. As before, no > > root mapping. > > > > root at member:/# net rpc rights

On Mon, 10 Jun 2024 13:38:21 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Mon, 10 Jun 2024 08:33:13 +0100 > Rowland Penny via samba <samba at lists.samba.org> wrote: > > > On Sun, 9 Jun 2024 18:52:39 +0100 > > Luis Peromarta via samba <samba at lists.samba.org> wrote: > > > > > Update: > > > > > > I

Hi, I have one Samba4 server running as Active Directory Domain Controller. It's working like a charm. So I needed to add another server to be a Member Server (File Server). The server is running samba-4.0.9. Configured and compiled ok: ./configure --prefix=/usr/local/samba --sysconfdir=/etc --localstatedir=/var --mandir=/usr/man --bindir=/usr/bin --sbindir=/usr/sbin --libdir=/lib

Are your clients talking to the DCs re. Time at all ? This is an example in one of my DCs: Run tcpdump on your DC: root at dwing:~# tcpdump??port 123 -v tcpdump: listening on enp1s0, link-type EN10MB (Ethernet), snapshot length 262144 bytes 10:20:41.655081 IP (tos 0x0, ttl 128, id 32113, offset 0, flags [none], proto UDP (17), length 96) ?? ?192.168.3.52.ntp > dwing.mad.mater.int.ntp: NTPv3,