Hello. I'm using Samba 3.0.25a on FreeBSD-6.0. Samba is configured to be a PDC. Samba can't find its hostname via nmblookup: $ nmblookup -B 192.168.1.255 frontier querying frontier on 192.168.1.255 name_query failed to find name frontier If I query Samba via unicast, it answers OK: $ nmblookup -U frontier frontier querying frontier on 192.168.1.31 192.168.1.31 frontier<00> Also, Samba cannot find domain's master, but I suspect it can't become the master because of this nmblookup failure. I've experienced the similar issue with other Samba-3.0.26a too. I've gone through Samba troubleshooting, but I didn't find anything. What could cause this issue? Thanks in advance, Silver -- View this message in context: http://www.nabble.com/Samba-can%27t-find-its-hostname-via-broadcast-tf4633404.html#a13230734 Sent from the Samba - General mailing list archive at Nabble.com.
Atrox wrote:> > Hello. > > I'm using Samba 3.0.25a on FreeBSD-6.0. Samba is configured to be a PDC. > > Samba can't find its hostname via nmblookup: > $ nmblookup -B 192.168.1.255 frontier > querying frontier on 192.168.1.255 > name_query failed to find name frontier > > If I query Samba via unicast, it answers OK: > $ nmblookup -U frontier frontier > querying frontier on 192.168.1.31 > 192.168.1.31 frontier<00> > > Also, Samba cannot find domain's master, but I suspect it can't become the > master because of this nmblookup failure. I've experienced the similar > issue with other Samba-3.0.26a too. I've gone through Samba > troubleshooting, but I didn't find anything. What could cause this issue? > > Thanks in advance, > Silver >Nothing on this? While googling I've seen questions about this issue asked several years ago, but not lately. And I haven't found any exhaustive answer to this :( More about the issue - if I nmblookup domain, I get quite a lot of answers, but not from the server itself (192.168.1.31): $ nmblookup mydomain querying mydomain on 192.168.1.255 192.168.1.200 mydomain<00> 192.168.1.145 mydomain<00> 192.168.1.147 mydomain<00> 192.168.1.131 mydomain<00> 192.168.1.130 mydomain<00> 192.168.1.138 mydomain<00> 192.168.1.140 mydomain<00> 192.168.1.149 mydomain<00> 192.168.1.143 mydomain<00> 192.168.1.139 mydomain<00> 192.168.1.141 mydomain<00> 192.168.1.110 mydomain<00> 192.168.1.100 mydomain<00> 192.168.1.118 mydomain<00> 192.168.1.111 mydomain<00> 192.168.1.106 mydomain<00> 192.168.1.108 mydomain<00> 192.168.1.126 mydomain<00> 192.168.1.105 mydomain<00> The firewall is not the issue as I see from tcpdump that broadcast queries to port 137 reach the server. -- Silver -- View this message in context: http://www.nabble.com/Samba-can%27t-find-its-hostname-via-broadcast-tf4633404.html#a13250356 Sent from the Samba - General mailing list archive at Nabble.com.
Michael Lueck
2007-Oct-17 17:16 UTC
[Samba] Re: Samba can't find its hostname via broadcast
Atrox wrote:> Samba can't find its hostname via nmblookup: > $ nmblookup -B 192.168.1.255 frontier > querying frontier on 192.168.1.255 > name_query failed to find name frontierHave you ever had another (multiple) IP addresses on this particular installation? Long long ago I ran into issues with a test box that had been known by several IP addresses over the course of time. nmbd got confused and did not know the IP address of the server itself. I flushed the wins cache on the PDC and all was well. That is... stopped samba deleted /var/run/samba/wins.tdb started samba In my case, it tried the oldest two IP addresses the server had been known as, just not the current IP address. Flushing WINS resulted in WINS being rediscovered, and thus the current IP address of the server was detected, and "samba could find itself again!" -- Michael Lueck Lueck Data Systems http://www.lueckdatasystems.com/