Hi, I am getting this log entry in the nmb.log file. Any ideas why I am getting it? query_name_response: Multiple (2) responses received for a query on subnet 9.36. 220.43 for name WHITE<1d>. This response was from IP 9.36.223.255 Thanks Chip
Ralph Blach wrote:> > Hi, > > I am getting this log entry in the nmb.log file. > > Any ideas why I am getting it? > > query_name_response: Multiple (2) responses received for a query on > subnet 9.36. > 220.43 for name WHITE<1d>. This response was from IP 9.36.223.255 >Looks like you may have two domain master browsers for the WHITE domain. Looks like a problem (try and check the IP addresses of the first and second responses involved). Hope this helps, Jeremy Allison, Samba Team. -- -------------------------------------------------------- Buying an operating system without source is like buying a self-assembly Space Shuttle with no instructions. --------------------------------------------------------
--On Tuesday, February 24, 1998, 6:57 AM +1100 "Jeremy Allison"
<jallison@whistle.com> wrote:
} Looks like you may have two domain master
} browsers for the WHITE domain. Looks like
} a problem (try and check the IP addresses
} of the first and second responses involved).
}
} Hope this helps,
}
} Jeremy Allison,
} Samba Team.
I submitted a similar problem about a week ago, and haven't seen it in
the list. Note that the address that's claimed as the origin is the
net broadcast address.
} > query_name_response: Multiple (2) responses received for a query on
} > subnet 9.36.
} > 220.43 for name WHITE<1d>. This response was from IP 9.36.223.255
^^^
We're seeing the same behavior here:
query_name_response: Multiple (2) responses received for a query on subnet
192.52.153.11 for name TIOGA<1d>. This response was from IP
192.52.153.255
There's a problem with the message - "192.52.153.11" isn't a
subnet.
In fact it's the host on which nmbd is running!
Our net broadcast address is 192.52.153.255.
How high does the nmbd debuglevel have to be set to see where the
responses are coming from?
Jim
--
Jim Watt jimw@PE-Nelson.COM
Perkin-Elmer Corporation Voice (desk): +1 408 577 2228
PE-Nelson Division Fax: +1 408 894 9307
3833 North First Street Voice (main): +1 408 577 2200
San Jose CA 95134-1701
--On Monday, February 23, 1998, 5:54 PM -0800 "Jeremy Allison"
<jallison@whistle.com> wrote:
} That means it really does have a source address of
} the broadcast address. You may need a network sniffer
} to track this one down.
Ugh! *Nothing* should be doing that!
} I'm not sure this is exactly the same network problem as
} the previous one as I don't think his response is from the
} subnet broadcast address.
I think it was...I didn't save the entire note, so I don't
know what the netmask looked like. But...
} Ralph Blach wrote:
} > query_name_response: Multiple (2) responses received for a query on
} > subnet 9.36.220.43 for name WHITE<1d>. This response was from
} > IP 9.36.223.255
^^^ <-----Hmmmmm......
I checked the digest archive - that's all the info there was in
the note.
Jim
--
Jim Watt jimw@PE-Nelson.COM
Perkin-Elmer Corporation Voice (desk): +1 408 577 2228
PE-Nelson Division Fax: +1 408 894 9307
3833 North First Street Voice (main): +1 408 577 2200
San Jose CA 95134-1701
Here is more information on the problem. the .255 address really is the broadcast address of the network. I also have two Identically compiled Sambas on the same network, and only one is getting this error. Here is the interface line for the samba getting the problem interfaces = 9.36.220.43/255.255.252.0 7.1.1.70/255.255.255.0 Now the second network is a private network which does NOT get routed to the outside world. Thanks Chip
Ralph Blach wrote:> > Here is more information on the problem. the .255 address really is > the broadcast address of the network. > I also have two Identically compiled Sambas on the same network, and > only one is getting this error. >Well the code that prints out that error message is getting the IP address directly from the recvfrom() call in util.c that gets the incoming udp packet. Do you have a network sniffer that can see if the source address really is getting set to the local broadcast address (and also this would allow you to get the MAC address of the sender to track it down) ? Jeremy Allison, Samba Team. -- -------------------------------------------------------- Buying an operating system without source is like buying a self-assembly Space Shuttle with no instructions. --------------------------------------------------------
On samba@samba.anu.edu.au, samba@samba.anu.edu.au wrote:> Subject: Re: nmb log file entry > Message-ID: <34F1CEB7.446B9B3D@whistle.com> > > Ralph Blach wrote: > > > > Hi, > > > > I am getting this log entry in the nmb.log file. > > > > Any ideas why I am getting it? > > > > query_name_response: Multiple (2) responses received for a query on > > subnet 9.36. > > 220.43 for name WHITE<1d>. This response was from IP 9.36.223.255 > > > > Looks like you may have two domain master > browsers for the WHITE domain. Looks like > a problem (try and check the IP addresses > of the first and second responses involved).I noticed this problem on a Solaris machine which had a network interface (le0:1) as well as a physical (le0), where both IP addresses were in the same subnet. No matter how I tried to configure samba, the only way I could stop this was to take down the second IP address. Is there any way to stop broadcast reception on an interface either in the Solaris or the Samba config? Hope this is of use, Matt. -- Matt JD Aldridge - NEXOR Technical Analyst Email: mailto:m.aldridge@nexor.co.uk Phone: +44 (0)115 952 0572 (has voicemail)
--On Wednesday, February 25, 1998, 5:48 AM +1100 "Jeremy Allison" <jallison@whistle.com> wrote: } Jeremy Allison wrote: } > } > Well the code that prints out that error message is getting } > the IP address directly from the recvfrom() call in util.c } > that gets the incoming udp packet. Do you have a network } > sniffer that can see if the source address really is getting } > set to the local broadcast address (and also this would allow } > you to get the MAC address of the sender to track it down) ? } > } } Well, raining on my own parade here I have (finally) realized } that the code in nmbd_namequery.c that prints out second message } IP source address is wrong :-(. It will always print out the } IP address the query was sent to - which of course is the } subnet broadcast address. Argggghhhhh. OK, with that fix in, we're seeing: query_name_response: Multiple (2) responses received for a query on subnet 192.52.153.11 for name TIOGA<1d>. This response was from IP 192.52.153.117 That actually makes sense...sort of. That address is a PPP connection, and the device it's coming from has been told that our Samba WINS server is the domain's NetBIOS nameserver. Now that I know what's doing that, I'll have a chat with the vendor of that beast! Jim -- Jim Watt jimw@PE-Nelson.COM Perkin-Elmer Corporation Voice (desk): +1 408 577 2228 PE-Nelson Division Fax: +1 408 894 9307 3833 North First Street Voice (main): +1 408 577 2200 San Jose CA 95134-1701