rh61, 2.2.14.
The problem is in 2.0.6 also.
1st samba is wins server.
2nd samba uses the 1st samba as wins server.
All is ok, but if I use
interfaces = eth0 127.0.0.1
bind interfaces only = yes
(is there anything wrong in the above lines?)
in the 2nd samba, then I get the following in the log.nmb of the 2nd
samba:
[2000/03/29 15:45:30, 1] nmbd/nmbd.c:main(743)
Netbios nameserver version 2.0.7-pre2 started.
Copyright Andrew Tridgell 1994-1998
[2000/03/29 15:45:30, 0] libsmb/nmblib.c:send_udp(755)
Packet send failed to wins.server.ip(137) ERRNO=Invalid argument
[2000/03/29 15:45:30, 0] nmbd/nmbd_packets.c:send_netbios_packet(172)
send_netbios_packet: send_packet() to IP wins.server.ip port 137
failed
[2000/03/29 15:45:30, 0]
nmbd/nmbd_nameregister.c:multihomed_register_name(311)
multihomed_register_name: Failed to send packet trying to register
name I5<20> IP 127.0.0.1
[2000/03/29 15:45:30, 0] libsmb/nmblib.c:send_udp(755)
Packet send failed to wins.server.ip(137) ERRNO=Invalid argument
[2000/03/29 15:45:30, 0] nmbd/nmbd_packets.c:send_netbios_packet(172)
send_netbios_packet: send_packet() to IP wins.server.ip port 137
failed
[2000/03/29 15:45:30, 0]
nmbd/nmbd_nameregister.c:multihomed_register_name(311)
multihomed_register_name: Failed to send packet trying to register
name I5<03> IP 127.0.0.1
[2000/03/29 15:45:30, 0] libsmb/nmblib.c:send_udp(755)
Packet send failed to wins.server.ip(137) ERRNO=Invalid argument
[2000/03/29 15:45:30, 0] nmbd/nmbd_packets.c:send_netbios_packet(172)
send_netbios_packet: send_packet() to IP wins.server.ip port 137
failed
[2000/03/29 15:45:30, 0]
nmbd/nmbd_nameregister.c:multihomed_register_name(311)
multihomed_register_name: Failed to send packet trying to register
name I5<00> IP 127.0.0.1
[2000/03/29 15:45:30, 0] libsmb/nmblib.c:send_udp(755)
Packet send failed to wins.server.ip(137) ERRNO=Invalid argument
[2000/03/29 15:45:30, 0] nmbd/nmbd_packets.c:send_netbios_packet(172)
send_netbios_packet: send_packet() to IP wins.server.ip port 137
failed
[2000/03/29 15:45:30, 0]
nmbd/nmbd_nameregister.c:multihomed_register_name(311)
multihomed_register_name: Failed to send packet trying to register
name WORKGROUP<00> IP 127.0.0.1
[2000/03/29 15:45:30, 0] libsmb/nmblib.c:send_udp(755)
Packet send failed to wins.server.ip(137) ERRNO=Invalid argument
[2000/03/29 15:45:30, 0] nmbd/nmbd_packets.c:send_netbios_packet(172)
send_netbios_packet: send_packet() to IP wins.server.ip port 137
failed
[2000/03/29 15:45:30, 0]
nmbd/nmbd_nameregister.c:multihomed_register_name(311)
multihomed_register_name: Failed to send packet trying to register
name WORKGROUP<1e> IP 127.0.0.1
[2000/03/29 16:00:14, 0]
nmbd/nmbd_become_lmb.c:become_local_master_stage2(405)
*****
Samba name server I5 is now a local master browser for workgroup
WORKGROUP on subnet 127.0.0.1
*****
So that the 2nd samba tells others that it's master browser:
$ nmblookup -S i5
querying i5 on 10.0.0.255
10.0.0.117 i5<00>
Looking up status of 10.0.0.117
received 7 names
I5 <00> - M <ACTIVE>
I5 <03> - M <ACTIVE>
I5 <20> - M <ACTIVE>
..__MSBROWSE__. <01> - <GROUP> M <ACTIVE>
WORKGROUP <00> - <GROUP> M <ACTIVE>
WORKGROUP <1d> - M <ACTIVE>
WORKGROUP <1e> - <GROUP> M <ACTIVE>
num_good_sends=0 num_good_receives=0
but, at the same time it thinks i4 is the real master browser (which is
true)
$ smbclient -L i5
...
...
Workgroup Master
--------- -------
WORKGROUP I4
$
--
giulioo@pobox.com