Hi all,
I finally upgrded Samba to 2.0.6 last night. After doing so, I have
observed some strange behaviour.
First of all, although domain master, local master and preferred master
are all set to true, the server running samba fails to become the local
master browser on one subnet (succeeds on another subnet though). The
messages from the log file are as follows:
[2000/03/16 22:08:50, 0]
nmbd/nmbd_nameregister.c:register_name_response(112)
register_name_response: server at IP 192.168.1.130 rejected our name
registration of RIDLEY<1d> with error code 6.
[2000/03/16 22:08:50, 0]
nmbd/nmbd_become_lmb.c:become_local_master_fail2(427)
become_local_master_fail2: failed to register name RIDLEY<1d> on subnet
192.168.1.1. Failed to become a local master browser.
[2000/03/16 22:08:50, 0]
nmbd/nmbd_namelistdb.c:standard_fail_register(295)
standard_fail_register: Failed to register/refresh name RIDLEY<1d> on
subnet 192.168.1.1
One particular host seems to reject the attempt to become the local
master, although it suceeds with 2.0.5a with the same config file. The
host that returns error code 6 is a WinNT 4 box.
The second problem that occurs is to do with the interfaces line. If I
have 127.0.0.1 appearing in the interfaces line, then all broadcast
packets sent by nmbd to register the host (these are broadcast packets)
have the source address set to 127.0.0.1!!!! Obviously, sending packets
with 127.0.0.1 isn't going to be too meaningful, and my packet filter
blocks them anyway.
Is it still important to place 127.0.0.1 in the interfaces line if you use
bind interfaces only = true (the man page says that a few things, such as
swat and I think smbstatus or smbclient may not work correctly if you
don't include the 127.0.0.1 address)?
Thanks in advance
Glen Gibb
IT Co-ordinator
Ridley College
