Displaying 20 results from an estimated 2000 matches similar to: "Debian11 Samba backport and bind9"
2023 Jan 16
1
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
2023 Jan 16
1
Debian11 Samba backport and bind9
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
2023 Jan 16
1
Debian11 Samba backport and bind9
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
2023 Jan 16
1
Debian11 Samba backport and bind9
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
2023 Jan 16
1
Debian11 Samba backport and bind9
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
2023 Jan 16
1
Debian11 Samba backport and bind9
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
2023 Jan 16
1
Debian11 Samba backport and bind9
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
2023 Jan 16
1
Debian11 Samba backport and bind9
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:
2023 Jan 16
1
Debian11 Samba backport and bind9
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
2023 Jan 16
1
Debian11 Samba backport and bind9
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
2023 Jan 16
1
Debian11 Samba backport and bind9
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
2019 Nov 27
3
join samba 3.6 to ad with samba.411
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:
2019 Nov 27
1
join samba 3.6 to ad with samba.411
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;
2020 May 15
2
Migrate DCs on ubuntu 14.04 to ubuntu 18.04
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:
2023 Jan 26
1
ctdb samba and winbind event problem
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
2019 Nov 27
2
join samba 3.6 to ad with samba.411
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
2023 Oct 18
1
Linux/Windows Domain Controller
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:
>
>
2019 Nov 27
2
join samba 3.6 to ad with samba.411
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]
2020 Feb 11
1
sambaXP 2020
Hi,
The 19th International User and Developer Conference sambaXP
(https://sambaxp.org/) will take place from 26th - 28th of May 2020 in
G?ttingen, Germany.
If you would like to give a presentation, you can submit your
paper here:
https://sambaxp.org/#c11
Call for paper ends on February 29th.
New for this year's event: the Microsoft SMB3 Interoperability Lab (IO
Lab) from May 24th-29th,
2024 Feb 04
1
GPO Entries missing
Hi all
I just installed the the ADMX-fils for the Linux-GPOs. IBut when I look
at the Group Policy Editor below "samba" I only see "Unix Setting ->
Scripts". "smb.conf", "Messages", "sudo-files" are missing. If I take a
look at the admx-file itself all the options are in the file.
I uses Sernet Samba 4.18.4 on Debian 12
I already did a