diff options
Diffstat (limited to 'docs/htmldocs/browsing-quick.html')
| -rw-r--r-- | docs/htmldocs/browsing-quick.html | 210 |
1 files changed, 170 insertions, 40 deletions
diff --git a/docs/htmldocs/browsing-quick.html b/docs/htmldocs/browsing-quick.html index 18be543aa4..9519e8808e 100644 --- a/docs/htmldocs/browsing-quick.html +++ b/docs/htmldocs/browsing-quick.html @@ -81,15 +81,39 @@ be taken as the fast track guide to implementing browsing across subnets and / or across workgroups (or domains). WINS is the best tool for resolution of NetBIOS names to IP addesses. WINS is NOT involved in browse list handling except by way of name to address mapping.</P +><DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif" +HSPACE="5" +ALT="Note"></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" ><P ->Note: MS Windows 2000 and later can be configured to operate with NO NetBIOS +>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.</P +></TD +></TR +></TABLE +></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN130" +NAME="AEN174" >2.1. Discussion</A ></H1 ><P @@ -101,29 +125,63 @@ messaging to affect browse list management. When running NetBIOS over TCP/IP this uses UDP based messaging. UDP messages can be broadcast or unicast.</P ><P >Normally, only unicast UDP messaging can be forwarded by routers. The -"remote announce" parameter to smb.conf helps to project browse announcements -to remote network segments via unicast UDP. Similarly, the "remote browse sync" -parameter of smb.conf implements browse list collation using unicast UDP.</P +<B +CLASS="COMMAND" +>remote announce</B +> +parameter to smb.conf helps to project browse announcements +to remote network segments via unicast UDP. Similarly, the +<B +CLASS="COMMAND" +>remote browse sync</B +> parameter of <TT +CLASS="FILENAME" +>smb.conf</TT +> +implements browse list collation using unicast UDP.</P ><P >Secondly, in those networks where Samba is the only SMB server technology wherever possible nmbd should be configured on one (1) machine as the WINS server. This makes it easy to manage the browsing environment. If each network segment is configured with it's own Samba WINS server, then the only way to -get cross segment browsing to work is by using the "remote announce" and -the "remote browse sync" parameters to your smb.conf file.</P +get cross segment browsing to work is by using the +<B +CLASS="COMMAND" +>remote announce</B +> and the <B +CLASS="COMMAND" +>remote browse sync</B +> +parameters to your <TT +CLASS="FILENAME" +>smb.conf</TT +> file.</P ><P >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.</P -><P ->As of Samba-3 WINS replication is being worked on. The bulk of the code has +the use of the <B +CLASS="COMMAND" +>remote announce</B +> and the +<B +CLASS="COMMAND" +>remote browse sync</B +> parameters should NOT be necessary.</P +><P +>As of Samba 3 WINS replication is being worked on. The bulk of the code has been committed, but it still needs maturation.</P ><P >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 +servers for redundancy (one server per subnet) and then used +<B +CLASS="COMMAND" +>remote browse sync</B +> and <B +CLASS="COMMAND" +>remote announce</B +> +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 @@ -140,7 +198,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN139" +NAME="AEN193" >2.2. How browsing functions and how to deploy stable and dependable browsing using Samba</A ></H1 @@ -157,7 +215,11 @@ well as name lookups are done by UDP broadcast. This isolates name resolution to the local subnet, unless LMHOSTS is used to list all names and IP addresses. In such situations Samba provides a means by which the samba server name may be forcibly injected into the browse -list of a remote MS Windows network (using the "remote announce" parameter).</P +list of a remote MS Windows network (using the +<B +CLASS="COMMAND" +>remote announce</B +> parameter).</P ><P >Where a WINS server is used, the MS Windows client will use UDP unicast to register with the WINS server. Such packets can be routed @@ -185,14 +247,23 @@ will annoy users because they will have to put up with protracted inability to use the network services.</P ><P >Samba supports a feature that allows forced synchonisation -of browse lists across routed networks using the "remote -browse sync" parameter in the smb.conf file. This causes Samba -to contact the local master browser on a remote network and +of browse lists across routed networks using the <B +CLASS="COMMAND" +>remote +browse sync</B +> parameter in the <TT +CLASS="FILENAME" +>smb.conf</TT +> file. +This causes Samba to contact the local master browser on a remote network and to request browse list synchronisation. This effectively bridges two networks that are separated by routers. The two remote networks may use either broadcast based name resolution or WINS -based name resolution, but it should be noted that the "remote -browse sync" parameter provides browse list synchronisation - and +based name resolution, but it should be noted that the <B +CLASS="COMMAND" +>remote +browse sync</B +> parameter provides browse list synchronisation - and that is distinct from name to address resolution, in other words, for cross subnet browsing to function correctly it is essential that a name to address resolution mechanism be provided. @@ -207,21 +278,40 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN149" ->2.3. Use of the "Remote Announce" parameter</A +NAME="AEN207" +>2.3. Use of the <B +CLASS="COMMAND" +>Remote Announce</B +> parameter</A ></H1 ><P ->The "remote announce" parameter of smb.conf can be used to forcibly ensure +>The <B +CLASS="COMMAND" +>remote announce</B +> parameter of +<TT +CLASS="FILENAME" +>smb.conf</TT +> can be used to forcibly ensure that all the NetBIOS names on a network get announced to a remote network. -The syntax of the "remote announce" parameter is: +The syntax of the <B +CLASS="COMMAND" +>remote announce</B +> parameter is: <PRE CLASS="PROGRAMLISTING" -> remote announce = a.b.c.d [e.f.g.h] ...</PRE +> remote announce = <VAR +CLASS="REPLACEABLE" +>a.b.c.d [e.f.g.h]</VAR +> ...</PRE > _or_ <PRE CLASS="PROGRAMLISTING" -> remote announce = a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP] ...</PRE +> remote announce = <VAR +CLASS="REPLACEABLE" +>a.b.c.d/WORKGROUP [e.f.g.h/WORKGROUP]</VAR +> ...</PRE > where: @@ -231,7 +321,14 @@ where: CLASS="VARIABLELIST" ><DL ><DT ->a.b.c.d and e.f.g.h</DT +><VAR +CLASS="REPLACEABLE" +>a.b.c.d</VAR +> and +<VAR +CLASS="REPLACEABLE" +>e.f.g.h</VAR +></DT ><DD ><P >is either the LMB (Local Master Browser) IP address @@ -246,7 +343,10 @@ undesirable but may be necessary if we do NOT know the IP address of the remote LMB.</P ></DD ><DT ->WORKGROUP</DT +><VAR +CLASS="REPLACEABLE" +>WORKGROUP</VAR +></DT ><DD ><P >is optional and can be either our own workgroup @@ -265,30 +365,49 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN163" ->2.4. Use of the "Remote Browse Sync" parameter</A +NAME="AEN230" +>2.4. Use of the <B +CLASS="COMMAND" +>Remote Browse Sync</B +> parameter</A ></H1 ><P ->The "remote browse sync" parameter of smb.conf is used to announce to +>The <B +CLASS="COMMAND" +>remote browse sync</B +> parameter of +<TT +CLASS="FILENAME" +>smb.conf</TT +> is used to announce to another LMB that it must synchronise it's NetBIOS name list with our Samba LMB. It works ONLY if the Samba server that has this option is simultaneously the LMB on it's network segment.</P ><P ->The syntax of the "remote browse sync" parameter is: +>The syntax of the <B +CLASS="COMMAND" +>remote browse sync</B +> parameter is: <PRE CLASS="PROGRAMLISTING" ->remote browse sync = a.b.c.d</PRE +>remote browse sync = <VAR +CLASS="REPLACEABLE" +>a.b.c.d</VAR +></PRE > -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.</P +where <VAR +CLASS="REPLACEABLE" +>a.b.c.d</VAR +> is either the IP address of the remote LMB or else is the network broadcast address of the remote segment.</P ></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN168" +NAME="AEN241" >2.5. Use of WINS</A ></H1 ><P @@ -312,7 +431,11 @@ of all names that have registered the NetLogon service name_type. This saves broadcast traffic and greatly expedites logon processing. Since broadcast name resolution can not be used across network segments this type of information can only be provided via WINS _or_ via statically configured -"lmhosts" files that must reside on all clients in the absence of WINS.</P +<TT +CLASS="FILENAME" +>lmhosts</TT +> files that must reside on all clients in the +absence of WINS.</P ><P >WINS also serves the purpose of forcing browse list synchronisation by all LMB's. LMB's must synchronise their browse list with the DMB (domain master @@ -330,8 +453,15 @@ machines that have not registered with a WINS server will fail name to address lookup attempts by other clients and will therefore cause workstation access errors.</P ><P ->To configure Samba as a WINS server just add "wins support = yes" to the -smb.conf file [globals] section.</P +>To configure Samba as a WINS server just add +<B +CLASS="COMMAND" +>wins support = yes</B +> to the <TT +CLASS="FILENAME" +>smb.conf</TT +> +file [globals] section.</P ><P >To configure Samba to register with a WINS server just add "wins server = a.b.c.d" to your smb.conf file [globals] section.</P @@ -351,7 +481,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN179" +NAME="AEN255" >2.6. Do NOT use more than one (1) protocol on MS Windows machines</A ></H1 ><P @@ -394,7 +524,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN187" +NAME="AEN263" >2.7. Name Resolution Order</A ></H1 ><P |