similar to: Debian11 Samba backport and bind9

Hi Stefan, I have exact that running: Samba 4.17.4 and bind 9.18 from the bullseye-backports. I my case "samba_dnsupdate --verbose --all-names" runs without any errors. As like 9.16 I use the "dlz_bind9_18.so" entry in named.conf. If you need further information to compare just ask. Regards Ingo https://github.com/WAdama Rowland Penny via samba schrieb am 16.01.2023 um

On 16/01/2023 16:56, Stefan Kania via samba wrote: > Hi to all, > Is there a known problem when using Debian 11 together with the samba > packages from the backports (4.17.4) and the bind9 from the backports > (9.18). With me it comes on each further Domaincontroller to errors with > the "samba_dnsupdate --verbose --all-names". > > If I install Bind9 in version

Am 16.01.23 um 18:31 schrieb Rowland Penny via samba: > > > On 16/01/2023 16:56, Stefan Kania via samba wrote: >> Hi to all, >> Is there a known problem when using Debian 11 together with the samba >> packages from the backports (4.17.4) and the bind9 from the backports >> (9.18). With me it comes on each further Domaincontroller to errors >> with the

On 16/01/2023 18:27, Stefan Kania via samba wrote: > > > Am 16.01.23 um 18:31 schrieb Rowland Penny via samba: >> >> >> On 16/01/2023 16:56, Stefan Kania via samba wrote: >>> Hi to all, >>> Is there a known problem when using Debian 11 together with the samba >>> packages from the backports (4.17.4) and the bind9 from the backports

On 16/01/2023 18:56, Rowland Penny via samba wrote: > > > On 16/01/2023 18:27, Stefan Kania via samba wrote: >> >> >> Am 16.01.23 um 18:31 schrieb Rowland Penny via samba: >>> >>> >>> On 16/01/2023 16:56, Stefan Kania via samba wrote: >>>> Hi to all, >>>> Is there a known problem when using Debian 11 together with the

Am 16.01.23 um 20:35 schrieb Ingo Asche via samba: > Hi Stefan, > > I have exact that running: Samba 4.17.4 and bind 9.18 from the > bullseye-backports. > > I my case "samba_dnsupdate --verbose --all-names" runs without any errors. > On the first DC it's running like I expacted, but on the second one I'm having the provlem. > As like 9.16 I use the

That's exactly what I'm saying. I can add output from all three DC's if necessary. Regards Ingo https://github.com/WAdama Rowland Penny via samba schrieb am 16.01.2023 um 22:02: > > > On 16/01/2023 20:52, Stefan Kania via samba wrote: >> As I said, both DC are installed via Vagrent, starting the setup with >> 9.18 I have the problem, starting with 9.16

Ah, ok, just saw it. Sorry, I missed that. I can only add then, all three DC's in my little net are installed with bind 9.18 and working all the same without errors. Regards Ingo https://github.com/WAdama Stefan Kania via samba schrieb am 16.01.2023 um 20:47: > > > Am 16.01.23 um 20:35 schrieb Ingo Asche via samba: >> Hi Stefan, >> >> I have exact that running:

As I said, both DC are installed via Vagrent, starting the setup with 9.18 I have the problem, starting with 9.16 everything is running. The configuration is always the same. Am 16.01.23 um 21:36 schrieb Rowland Penny via samba: > > > On 16/01/2023 19:55, Ingo Asche via samba wrote: >> Ah, ok, just saw it. Sorry, I missed that. >> >> I can only add then, all three

On 16/01/2023 19:55, Ingo Asche via samba wrote: > Ah, ok, just saw it. Sorry, I missed that. > > I can only add then, all three DC's in my little net are installed with > bind 9.18 and working all the same without errors. That would tend to dispel my worries, so it is possible that it is some misconfiguration on Stefan's machine. I know I once joined a DC and forgot the

On 16/01/2023 20:52, Stefan Kania via samba wrote: > As I said, both DC are installed via Vagrent, starting the setup with > 9.18 I have the problem, starting with 9.16 everything is running. The > configuration is always the same. > > I am getting confused now (not that it takes much) Are you saying that none of your 4.17.x DC's work with Bind 9.18 ? Ingo seems to be

when we try to join we get the following error message: Failed to join domain: failed to lookup DC info for domain #our-domain' over rpc:NT_STATUS_INVALID_NETWORK_RESPONSE looking up the dc and all SRV-Records is working. A "kinit administrator" is working to. Stefan Am 27.11.19 um 16:37 schrieb Rowland penny via samba: > On 27/11/2019 14:37, Stefan Kania via samba wrote:

Looks about right. That said, you don't need 'client min protocol' on the DC. You need the client max protocol on the domain member and server min protocol on the DC to overlap. Andrew Bartlett On Wed, 2019-11-27 at 17:04 +0100, Stefan Kania via samba wrote: > Error verifying signature: parse error > --------------ms060308020506090108040201 > Content-Type: text/plain;

Hi, I'm having the following setup: 3 offices, with at least 2 DCs per office. Every DC is running on ubuntu 14.04 with either samba 4.3.9 or 4.3.11. I'm not the one that build these DCs but from documentation and what I'm told, nothing fancy was done on them, just joined the domain, added users/fileservers and group policy replication as described here:

Hi, I had such a Problem with an old SLES 11 and Samba 3.6. I needed to enable SMB1 on the DC. Samba 4.11 disables SMB1 Boy default. Regards Andreas Von meinem iPhone gesendet > Am 27.11.2019 um 16:43 schrieb Stefan Kania via samba <samba at lists.samba.org>: > > ?when we try to join we get the following error message: > > Failed to join domain: failed to lookup DC info

Hi Stefan, On Thu, 26 Jan 2023 16:35:59 +0100, Stefan Kania via samba <samba at lists.samba.org> wrote: > I'm having a CTDB-Cluster with two nodes (both Ubuntu wit > Sernet-packages 4.17.4). Now I want to replace one of the nodes. The > first step was to bring a new node to the CTDB-Cluster. This time a > Debian 11 but with the same sernet-packages (4.17.4). Adding the

Yes I've red this section and the docu is saying no FL above 2008. Might be caused by incompleted docu? So far I understand if we don't use >4.19 we will not be able to use FL 2016 which is necessary since our DC WIN22 is configured as FL2016? On 18.10.23 19:10, Stefan Kania via samba wrote: > If you take a look at: > >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 19.01.16 um 19:38 schrieb Rowland penny: > On 19/01/16 17:24, Stefan Kania wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> "samba-tool user setpassword" works fine, but I don't want all >> "normal" Users to connect to the Domaincontroller to change >> their password. >

Hello, we MUST join a 3.6 Samba into a Samba-Ad with 4.11, which options do I have to set? on the DCs to join the samba 3.6. Pleas no answer "update to 4.x" it's NOT possible at the moment ? thanks Stefan

Hi Louis, it's an old ubuntu 12.04 with samba 3.6.25. It's a fileserver with DRBD and we have to join the server until a new one is ready to use. Stefan Am 27.11.19 um 14:30 schrieb L.P.H. van Belle via samba: > If i may ask, which os and version of the samba 3.6? > > >> -----Oorspronkelijk bericht----- >> Van: samba [mailto:samba-bounces at lists.samba.org]