Bug 16230 - idmap: get_kdc_ip_string: get_kdc_list fail NT_STATUS_NO_LOGON_SERVERS after connection to KDC drops
Summary: idmap: get_kdc_ip_string: get_kdc_list fail NT_STATUS_NO_LOGON_SERVERS after ...
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Winbind (show other bugs)
Version: 4.24.6
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL: https://lists.samba.org/archive/samba...
Keywords:
Depends on:
Blocks:
 
Reported: 2026-09-01 05:37 UTC by Michael Tokarev
Modified: 2026-09-02 10:18 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Tokarev 2026-09-01 05:37:19 UTC
As pointed out several times, there's a logic error in winbind when handling disconnect of a connection to the nearby kdc.  The most recent report with debugging is this: https://lists.samba.org/archive/samba/2026-March/252709.html .

Basically, after receiving disconnect from LDAP, winbind declares that this kdc is dead, and tries the next one, instead of retrying the one which got disconnected.  But in case there's just one DC on the site, it finds the same DC, which is already marked dead, and, instead of trying other sites, it declares there's no logon servers.  The message referenced above has complete analysis.

This is happening for quite some time, at least since samba 4.18, and up to current 4.25-rc.

Besides this logic error, I really wonder why winbind keeps persistent connection to the DCs.  No windows machine does this.  Can't it drop the connection when idle, or use some other way (UDP?) to do the same, in order to free the resources?  On one of our bigger domanis, their admins complains to us about every samba server keeping persistent connection.

Thanks,

/mjt