Updating projdoc from HEAD brach.

(This used to be commit d4545b9154162a0a340ef52bfe8443b86dae9e56)

1 files changed, 52 insertions, 28 deletions

diff --git a/docs/docbook/projdoc/Browsing-Quickguide.sgml b/docs/docbook/projdoc/Browsing-Quickguide.sgml
index 8ecc795966..0a5cf72038 100644
--- a/docs/docbook/projdoc/Browsing-Quickguide.sgml
+++ b/docs/docbook/projdoc/Browsing-Quickguide.sgml
@@ -1,9 +1,10 @@
 <chapter id="Browsing-Quick">
 <chapterinfo>
 	<author>
-		<firstname>John</firstname><surname>Terpstra</surname>
+		<firstname>John H</firstname><surname>Terpstra</surname>
 	</author>
 	<pubdate>July 5, 1998</pubdate>
+	<pubdate>Updated: March 15, 2003</pubdate>
 </chapterinfo>
 
 <title>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</title>
@@ -16,16 +17,22 @@ of NetBIOS names to IP addesses. WINS is NOT involved in browse list handling
 except by way of name to address mapping.
 </para>
 
+<para>
+Note: MS Windows 2000 and later can be configured to operate with NO NetBIOS 
+over TCP/IP. Samba-3 and later also supports this mode of operation.
+</para>
+
+
 <sect1>
 <title>Discussion</title>
 
 <para>
 Firstly, all MS Windows networking is based on SMB (Server Message
-Block) based messaging. SMB messaging is implemented using NetBIOS. Samba
-implements NetBIOS by encapsulating it over TCP/IP. MS Windows products can
-do likewise. NetBIOS based networking uses broadcast messaging to affect
-browse list management. When running NetBIOS over TCP/IP this uses UDP
-based messaging. UDP messages can be broadcast or unicast.
+Block) based messaging. SMB messaging may be implemented using NetBIOS or 
+without NetBIOS. Samba implements NetBIOS by encapsulating it over TCP/IP.
+MS Windows products can do likewise. NetBIOS based networking uses broadcast
+messaging to affect browse list management. When running NetBIOS over
+TCP/IP this uses UDP based messaging. UDP messages can be broadcast or unicast.
 </para>
 
 <para>
@@ -45,20 +52,27 @@ the "remote browse sync" parameters to your smb.conf file.
 </para>
 
 <para>
-If only one WINS server is used then the use of the "remote announce" and the
-"remote browse sync" parameters should NOT be necessary.
+If only one WINS server is used for an entire multi-segment network then
+the use of the "remote announce" and the "remote browse sync" parameters
+should NOT be necessary.
+</para>
+
+<para>
+As of Samba-3 WINS replication is being worked on. The bulk of the code has
+been committed, but it still needs maturation.
 </para>
 
 <para>
-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 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).
+Right now 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 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).
 </para>
 
 <para>
@@ -126,8 +140,9 @@ simultaneously the LMB on it's network segment.
 
 <para>
 The syntax of the "remote browse  sync" parameter is:
+
 <programlisting>
-	remote browse sync = a.b.c.d
+remote browse sync = a.b.c.d
 </programlisting>
 
 where a.b.c.d is either the IP address of the remote LMB or else is the network broadcast address of the remote segment.
@@ -197,8 +212,9 @@ To configure Samba to register with a WINS server just add
 </para>
 
 <para>
-<emphasis>DO NOT EVER</emphasis> use both "wins support = yes" together with "wins server = a.b.c.d"
-particularly not using it's own IP address.
+<emphasis>DO NOT EVER</emphasis> use both "wins support = yes" together
+with "wins server = a.b.c.d" particularly not using it's own IP address.
+Specifying both will cause nmbd to refuse to start!
 </para>
 
 </sect1>
@@ -212,7 +228,7 @@ one protocol on an MS Windows machine.
 </para>
 
 <para>
-Every NetBIOS machine take part in a process of electing the LMB (and DMB)
+Every NetBIOS machine takes part in a process of electing the LMB (and DMB)
 every 15 minutes. A set of election criteria is used to determine the order
 of precidence for winning this election process. A machine running Samba or
 Windows NT will be biased so that the most suitable machine will predictably
@@ -231,6 +247,15 @@ as an LMB and thus browse list operation on all TCP/IP only machines will
 fail.
 </para>
 
+<para><emphasis>
+Windows 95, 98, 98se, Me are referred to generically as Windows 9x.
+The Windows NT4, 2000, XP and 2003 use common protocols. These are roughly
+referred to as the WinNT family, but it should be recognised that 2000 and
+XP/2003 introduce new protocol extensions that cause them to behave 
+differently from MS Windows NT4. Generally, where a server does NOT support
+the newer or extended protocol, these will fall back to the NT4 protocols.
+</emphasis></para>
+
 <para>
 The safest rule of all to follow it this - USE ONLY ONE PROTOCOL!
 </para>
@@ -243,36 +268,35 @@ The safest rule of all to follow it this - USE ONLY ONE PROTOCOL!
 <para>
 Resolution of NetBIOS names to IP addresses can take place using a number
 of methods. The only ones that can provide NetBIOS name_type information
-are:
+are:</para>
+
 <simplelist>
 <member>WINS: the best tool!</member>
 <member>LMHOSTS: is static and hard to maintain.</member>
 <member>Broadcast: uses UDP and can not resolve names across remote segments.</member>
 </simplelist>
-</para>
 
 <para>
-Alternative means of name resolution includes:
+Alternative means of name resolution includes:</para>
 <simplelist>
 <member>/etc/hosts: is static, hard to maintain, and lacks name_type info</member>
 <member>DNS: is a good choice but lacks essential name_type info.</member>
 </simplelist>
-</para>
 
 <para>
 Many sites want to restrict DNS lookups and want to avoid broadcast name
 resolution traffic. The "name resolve order" parameter is of great help here.
 The syntax of the "name resolve order" parameter is:
 <programlisting>
-	name resolve order = wins lmhosts bcast host
+name resolve order = wins lmhosts bcast host
 </programlisting>
 _or_
 <programlisting>
-	name resolve order = wins lmhosts  	(eliminates bcast and host)
+name resolve order = wins lmhosts  	(eliminates bcast and host)
 </programlisting>
 The default is:
 <programlisting>
-	name  resolve order = host lmhost wins bcast
+name  resolve order = host lmhost wins bcast
 </programlisting>.
 where "host" refers the the native methods used by the Unix system
 to implement the gethostbyname() function call. This is normally