From b074c129220a5ae3e6fcc5b3ea262d8f988c6d9f Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Thu, 9 Jul 1998 07:44:07 +0000 Subject: Fixed typos and reformatted doco. (This used to be commit 4a0cda25fd96e81da2502c3e0efd83d9a4c0ced6) --- docs/textdocs/BROWSING-Config.txt | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'docs/textdocs/BROWSING-Config.txt') diff --git a/docs/textdocs/BROWSING-Config.txt b/docs/textdocs/BROWSING-Config.txt index 33c56e0897..6afd958f77 100644 --- a/docs/textdocs/BROWSING-Config.txt +++ b/docs/textdocs/BROWSING-Config.txt @@ -41,13 +41,13 @@ If only one WINS server is used then the use of the "remote announce" and the Samba WINS does not support MS-WINS replication. This means that when setting up Samba as a WINS server there must only be one nmbd configured as a WINS server -on the network. Some sites have used multiple Samba WINS servers for redundency +on the network. Some sites have used multiple Samba WINS servers for redundancy (one server per subnet) and then used "remote browse sync" and "remote announce" -to affect browse list collation across all segments. Note that this means clients -will only resolve local names, and must be configured to use DNS to resolve names -on other subnets in order to resolve the IP addresses of the servers they can see -on other subnets. This setup is not recommended, but is mentioned as a practical -consideration (ie. an 'if all else fails' scenario). +to affect browse list collation across all segments. Note that this means +clients will only resolve local names, and must be configured to use DNS to +resolve names on other subnets in order to resolve the IP addresses of the +servers they can see on other subnets. This setup is not recommended, but is +mentioned as a practical consideration (ie: an 'if all else fails' scenario). Lastly, take note that browse lists are a collection of unreliable broadcast messages that are repeated at intervals of not more than 15 minutes. This means -- cgit