This bug appears always when the samba cannot find the other host (with samba also) through broadcast queries and must to resolve this adress through WINS. It's normal? From this bug depend other bug - 298 (cannot find DMB from LMB in other networks) Full description: ----------------- HOST1(192.168.4.1 (WINS)---|ROUTER|---HOST2(192.168.2.1) [root@host1 root]# ping 192.168.2.1 ... 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.494 ms ... [root@host2 root]# ping 192.168.4.1 ... 64 bytes from 192.168.4.1: icmp_seq=1 ttl=64 time=0.506 ms ... [root@host1 root]# nmblookup -S HOST1 ... querying HOST1 on 192.168.4.255 Got a positive name query response from 192.168.4.1 ( 192.168.4.1 ) 192.168.4.1 HOST1<00> Looking up status of 192.168.4.1 HOST1 <00> - H <ACTIVE> ... [root@host1 root]# nmblookup -S HOST2 .. name_query failed to find name HOST2 BUT WINS work correctly: [root@host1 root]# smbclient -L HOST2 ... Got a positive name query response from 127.0.0.1 ( 192.168.2.1 ) error connecting to 192.168.2.1:445 (Connection refused) Password: ... And from other host: [root@host2 root]# smbclient -L HOST1 ... Got a positive name query response from 192.168.4.1 ( 192.168.4.1 ) Password: ... Config of HOST1: ---------------- [global] netbios name = HOST1 wins support = Yes ... Config of HOST2: ---------------- [global] netbios name = HOST2 wins server = 192.168.4.1 ...
nmblookup does not use wins unless you tell it to (nmblookup -U <ip of wins server> -R -S name)
originally reported against one of the 3.0.0rc[1-4] releases. Cleaning up non-production versions.
database cleanup