Bug 16153 - dsgetdcname() may not detect an active directory domain if the netbios domain name is given and nmbd nor the nbt service is available
Summary: dsgetdcname() may not detect an active directory domain if the netbios domain...
Status: RESOLVED FIXED
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Tools (show other bugs)
Version: 4.24.4
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Samba release manager
QA Contact: Samba QA Contact
URL: https://gitlab.com/samba-team/samba/-...
Keywords:
Depends on:
Blocks: 12902
  Show dependency tree / graph
 
Reported: 2026-07-02 08:26 UTC by Stefan Metzmacher
Modified: 2026-08-13 14:31 UTC (History)
1 user (show)

See Also:


Attachments
Patch for v4-24-test (2.71 KB, text/plain)
2026-07-28 16:43 UTC, Stefan Metzmacher
asn: review+
Details
Patch for v4-23-test (2.71 KB, text/plain)
2026-07-28 16:43 UTC, Stefan Metzmacher
asn: review+
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Metzmacher 2026-07-02 08:26:51 UTC
Modern setups may not start nmbd, that means doing an netbios ping in order
to detect a ad domain doesn't work, so we better try cldap first as it's 2026
and most domains should be AD.
Comment 1 Samba QA Contact 2026-07-02 09:34:03 UTC
This bug was referenced in samba master:

8bd496bf937d3a38482943e973a196f2c1f902a9
Comment 2 Stefan Metzmacher 2026-07-28 16:43:35 UTC
Created attachment 19142 [details]
Patch for v4-24-test
Comment 3 Stefan Metzmacher 2026-07-28 16:43:56 UTC
Created attachment 19143 [details]
Patch for v4-23-test
Comment 4 Samba QA Contact 2026-08-03 19:23:12 UTC
This bug was referenced in samba v4-23-test:

d1515c4b116f83a13f6ae6f6a745abab6c9bca6b
Comment 5 Samba QA Contact 2026-08-03 19:36:49 UTC
This bug was referenced in samba v4-23-stable (Release samba-4.23.11):

d1515c4b116f83a13f6ae6f6a745abab6c9bca6b
Comment 6 Samba QA Contact 2026-08-11 19:20:28 UTC
This bug was referenced in samba v4-24-test:

692e4184ac40b37191f8809763de213fa3663897
Comment 7 Samba QA Contact 2026-08-13 14:31:31 UTC
This bug was referenced in samba v4-24-stable (Release samba-4.24.6):

692e4184ac40b37191f8809763de213fa3663897