Table of Contents
Advertisement
Chapter 14. Samba
Tip
Lowering the
browsers on the same subnet. The higher the value, the higher the priority. The
highest a Windows server can operate at is 32. This is a good way of tuning
multiple local master browsers.
There are instances when a Windows NT machine on the subnet could be the local master
browser. The following is an example
serving in any browsing capacity:
[global]
domain master = no
local master = no
preferred master = no
os level = 0
Warning
Having multiple local master browsers result in each server competing for
browsing election requests. Make sure there is only one local master browser per
subnet.
6.2. Domain Browsing
By default, a Windows NT PDC for a domain is also the domain master browser for that domain.
A Samba server must be set up as a domain master server in this type of situation. Network
browsing may fail if the Samba server is running WINS along with other domain controllers in
operation.
For subnets that do not include the Windows NT PDC, a Samba server can be implemented as
a local master browser. Configuring the
all) in a domain controller environment is the same as workgroup configuration.
6.3. WINS (Windows Internetworking Name Server)
Either a Samba server or a Windows NT server can function as a WINS server. When a WINS
server is used with NetBIOS enabled, UDP unicasts can be routed which allows name
resolution across networks. Without a WINS server, the UDP broadcast is limited to the local
subnet and therefore cannot be routed to other subnets, workgroups, or domains. If WINS
replication is necessary, do not use Samba as your primary WINS server, as Samba does not
266
directive results in Samba conflicting with other master
os level
configuration in which the Samba server is not
smb.conf
smb.conf
for a local master browser (or no browsing at
Advertisement
Table of Contents
