Bug 16178 - query_name_response: Multiple (2) responses received for a query
Summary: query_name_response: Multiple (2) responses received for a query
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Other (show other bugs)
Version: 4.22.7
Hardware: All All
: P5 minor (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-07-12 06:51 UTC by Adam Baxter
Modified: 2026-07-13 06:39 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Baxter 2026-07-12 06:51:40 UTC
I am seeing messages like

Sun Jul 12 06:40:02 2026 daemon.err nmbd[22500]: [2026/07/12 06:40:02.025810,  0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Sun Jul 12 06:40:02 2026 daemon.err nmbd[22500]:   query_name_response: Multiple (2) responses received for a query on subnet 10.0.0.1 for name WORKGROUP<1d>.
Sun Jul 12 06:40:02 2026 daemon.err nmbd[22500]:   This response was from IP 10.0.0.3, reporting an IP address of 10.0.0.3

Apologies if I have misunderstood this bit, but does https://git.samba.org/samba.git/?p=samba.git;a=blob;f=source3/nmbd/nmbd_namequery.c;h=ae50a232987fc2073e6d1c07b6a3b0625b8496e2;hb=HEAD#l109 mean that it will always be reported, even with no debug level set? (DBGLEVEL(0))

I am not sure how to capture these in Wireshark. 

I can reliably reproduce the error (warning?) on 10.0.0.1, which is my OpenWrt router, by restarting Samba (which I presume restarts nmbd)

If I capture packets on 10.0.0.3, I only see two incoming UDP packets from 10.0.0.1, but no response from 10.0.0.3

To sum up:
* How do I silence these errors?
* How do I debug the cause of these errors, including packet captures?
Comment 1 Adam Baxter 2026-07-12 07:07:29 UTC
I think I have solved it for myself but my questions about log levels and packet captures remain.


Despite having bind interfaces only and interfaces set in my config, a br-* interface or the docker0 interface from Docker was causing multiple replies.

Setting 

interfaces = 10.0.0.3/23
bind interfaces only = yes

rather than interfaces = eno3

seems to have solved it.

However, I still don't think the error message is useful or correct - https://bugzilla.samba.org/show_bug.cgi?id=2439 noticed this many years ago.
Comment 2 Adam Baxter 2026-07-12 07:15:31 UTC
Forgot I can't edit comments, sorry - this is NOT fixed although I will keep debugging on my end.
Comment 3 Rowland Penny 2026-07-13 06:39:38 UTC
(In reply to Adam Baxter from comment #0)

You appear to have two entities claiming the NetBIOS master browser role, so you are getting the warning, this is not an error in the Samba code, it is an error in your set up.

Do you need to use SMBv1 ?
If not, then the easiest way to stop these messages is to turn off nmbd.