summaryrefslogtreecommitdiff
path: root/docs/docbook/smbdotconf/misc/remotebrowsesync.xml
blob: 8b0d863ed7c57ec92192bcc6d1166fcbb56c663b (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
<samba:parameter xmlns:samba="http://samba.org/common">
		<term><anchor id="REMOTEBROWSESYNC"/>remote browse sync (G)</term>
		<listitem><para>This option allows you to setup <ulink url="nmbd.8.html">nmbd(8)</ulink> to periodically request 
		synchronization of browse lists with the master browser of a Samba 
		server that is on a remote segment. This option will allow you to 
		gain browse lists for multiple workgroups across routed networks. This 
		is done in a manner that does not work with any non-Samba servers.</para>

		<para>This is useful if you want your Samba server and all local 
		clients to appear in a remote workgroup for which the normal browse 
		propagation rules don't work. The remote workgroup can be anywhere 
		that you can send IP packets to.</para>

		<para>For example:</para>
		
		<para><command moreinfo="none">remote browse sync = 192.168.2.255 192.168.4.255
		</command></para>

		<para>the above line would cause <command moreinfo="none">nmbd</command> to request 
		the master browser on the specified subnets or addresses to 
		synchronize their browse lists with the local server.</para>

		<para>The IP addresses you choose would normally be the broadcast 
		addresses of the remote networks, but can also be the IP addresses 
		of known browse masters if your network config is that stable. If 
		a machine IP address is given Samba makes NO attempt to validate 
		that the remote machine is available, is listening, nor that it 
		is in fact the browse master on its segment.</para>

		<para>Default: <command moreinfo="none">remote browse sync = &lt;empty string&gt;
		</command></para>
		</listitem>
		</samba:parameter>