Workgroup Browsing - Red Hat ENTERPRISE LINUX 4.5.0 Reference Manual

Table of Contents

Advertisement

as servers and if opened, the server's shares and printers that are available are displayed.
Network browsing capabilities require NetBIOS over TCP/IP. NetBIOS-based networking uses
broadcast (UDP) messaging to accomplish browse list management. Without NetBIOS and
WINS as the primary method for TCP/IP hostname resolution, other methods such as static files
(
) or DNS, must be used.
/etc/hosts
A domain master browser collates the browse lists from local master browsers on all subnets so
that browsing can occur between workgroups and subnets. Also, the domain master browser
should preferably be the local master browser for its own subnet.

6.1. Workgroup Browsing

For each workgroup, there must be one and only one domain master browser. You can have
one local master browser per subnet without a domain master browser, but this results in
isolated workgroups unable to see each other. To resolve NetBIOS names in cross-subnet
workgroups, WINS is required.
Note
The Domain Master Browser can be the same machine as the WINS server.
There can only be one domain master browser per workgroup name. Here is an example of the
file in which the Samba server is a domain master browser:
smb.conf
[global]
domain master = Yes
local master = Yes
preferred master = Yes
os level = 35
Next is an example of the
[global]
domain master = no
local master = Yes
preferred master = Yes
os level = 35
The
directive operates as a priority system for master browsers in a subnet. Setting
os level
different values ensures master browsers do not conflict with each other for authority.
file in which the Samba server is a local master browser:
smb.conf
Workgroup Browsing
265

Advertisement

Table of Contents
loading

Table of Contents