summaryrefslogtreecommitdiff
path: root/docs/smbdotconf/browse/domainmaster.xml
blob: 54f97caf3774a21fd01797db4d3b57a667490da6 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
<samba:parameter name="domain master"
				 type="boolean"
                 context="G"
                 basic="1" advanced="1" developer="1"
                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
<description>
	<para>Tell <citerefentry><refentrytitle>smbd</refentrytitle>
	<manvolnum>8</manvolnum></citerefentry> to enable WAN-wide browse list
	collation. Setting this option causes <command moreinfo="none">nmbd</command> to
	claim a special domain specific NetBIOS name that identifies 
	it as a domain master browser for its given <link linkend="WORKGROUP">
	<parameter moreinfo="none">workgroup</parameter></link>. Local master browsers 
	in the same <parameter moreinfo="none">workgroup</parameter> on broadcast-isolated 
	subnets will give this <command moreinfo="none">nmbd</command> their local browse lists, 
	and then ask <citerefentry><refentrytitle>smbd</refentrytitle>
	<manvolnum>8</manvolnum></citerefentry> for a complete copy of the browse 
	list for the whole wide area network.  Browser clients will then contact 
	their local master browser, and will receive the domain-wide browse list, 
	instead of just the list for their broadcast-isolated subnet.</para>

	<para>Note that Windows NT Primary Domain Controllers expect to be 
	able to claim this <parameter moreinfo="none">workgroup</parameter> specific special 
	NetBIOS name that identifies them as domain master browsers for 
	that <parameter moreinfo="none">workgroup</parameter> by default (i.e. there is no 
	way to prevent a Windows NT PDC from attempting to do this). This 
	means that if this parameter is set and <command moreinfo="none">nmbd</command> claims 
	the special name for a <parameter moreinfo="none">workgroup</parameter> before a Windows 
	NT PDC is able to do so then cross subnet browsing will behave 
	strangely and may fail.</para>
		
	<para>If <link linkend="DOMAINLOGONS"><command moreinfo="none">domain logons = yes</command>
	</link>, then the default behavior is to enable the <parameter moreinfo="none">domain 
	master</parameter> parameter.  If <parameter moreinfo="none">domain logons</parameter> is 
	not enabled (the default setting), then neither will <parameter moreinfo="none">domain 
	master</parameter> be enabled by default.</para>

</description>
<value type="default">auto</value>
</samba:parameter>