Linux Box Blocking Network Neighborhood

Allen, Michael B (RSCH) Michael_B_Allen at
Thu Oct 12 03:15:56 GMT 2000


One of the master browsers on our corporate network failed to communicate
the entire list of hosts for the segment to the domain master browser. The
result was simply that an apparently random small number of hosts were not
visible in network neighborhood for any other segment. Computer support
tracked down the failing master browser to find it was a Linux machine
running Samba. They are convinced that this machine was at fault because
after it was unplugged from the network the missing hosts reappeared. Using
a "browse monitor" tool they were able to determine that the Linux machine
had the entire list or at least the missing hosts in it's browse list. I
believe also that the other hosts on that segment had the complete list. It
was only a miscommuniation between the Linux machine and the domain master

Does anyone know why this Samba master browser would communicate only some
of the hosts in it's browse list to the domain master browser? After
advocating Linux as I have here I would like to present computer support
with an explaination rather than let them declaire that Linux is bad for the
network. Or properly inform them that it is if not properly configured.

Also I am not sure the user even had Samba configured to be any different
than the distro defaults. If he did not put in a workgroup name how could
Samba find the domain master browser? Similarly he would have to enter a
wins server or it would fail to find the domain master browser and knock out
that entire segment from Network Neighborhood. Why did this not happen? If
he did have it configured to some degree is it possible to configure Samba
to behave this way. Or perhaps a bug?

I only recently learned of the problem so I have not had a chance to speak
with the owner of the Linux machine or look at the machines configuration. I
will be at home tomarrow however my intention is to call him, get him back
on the network momentarily so I can telnet in, and snoop around.

Actually I thought I might just run the following script. Anyone care to add
to the diagnostics I should perform?



uname -a
netstat -rn
nmblookup -A
smbd -V
cat /etc/smb.conf | awk '/^[    ]*[^#;]/ { print }'
tail -100 /var/log/samba/log.nmb
echo '------------------------------------'
tail -100 /var/log/samba/log.nmb.1


More information about the samba mailing list