Re: Strange problem with winbind on linux domain member (works for 2 minutes...)

Am 06.02.2026 um 10:08 schrieb Rowland Penny via samba:
> On Thu, 5 Feb 2026 18:04:54 +0100
> Jakob Curdes via samba <[email protected]> wrote:
>
>
>> No, this is just a dedicated Sambe fileserver that is not doing
>> anything else. We have two dedicated samba4 DCs (Ubuntu24), and apart
>> from this problem everything runs fine.
>>
>> Times are in sync, timezones are identical etc. What could the error
>> message point to?
>>
>> Feb 05 13:35:01 *** winbindd[3131]: [2026/02/05 13:35:01.392619, 0]
>> source3/winbindd/winbindd_samr.c:71(open_internal_samr_conn)
>>    Feb 05 13:35:01 *** winbindd[3131]:   open_internal_samr_conn:
>> Could not connect to samr pipe: NT_STATUS_CONNECTION_DISCONNECTED
> It is fairly obvious what is happening, winbindd is trying to connect
> to a pipe and getting disconnected, the 'why' is the question, try
> raising the log level and see if anything pops out in the  logs.
Ok, will do so and report.
>
>> I cleaned up all .tdb and .ldb files in /var/lib/samba and
>> /var/cache/samba before joining the domain, could I have missed
>> something to clean up?
> Have you considered using Debian 13 with Samba from backports, this
> will get you 4.23.5 , 4.19.5 is EOL as far as Samba is concerned.
Not yet. Specifically for this server it is not so easy as it is a large 
system and hard to have several instances.

But I could do sort of a "mockup" without the actual data and see how it 
behaves if we do not find the root cause.

Thank you and best regards, Jakob



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba