diff options
Diffstat (limited to 'docs/htmldocs/improved-browsing.html')
| -rw-r--r-- | docs/htmldocs/improved-browsing.html | 468 |
1 files changed, 134 insertions, 334 deletions
diff --git a/docs/htmldocs/improved-browsing.html b/docs/htmldocs/improved-browsing.html index 3817bbece8..4e9d7f639e 100644 --- a/docs/htmldocs/improved-browsing.html +++ b/docs/htmldocs/improved-browsing.html @@ -5,19 +5,20 @@ >Improved browsing in samba</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK REL="UP" -TITLE="Advanced Configuration" -HREF="optional.html"><LINK +TITLE="General installation" +HREF="introduction.html"><LINK REL="PREVIOUS" -TITLE="Integrating MS Windows networks with Samba" -HREF="integrate-ms-networks.html"><LINK +TITLE="How to Install and Test SAMBA" +HREF="install.html"><LINK REL="NEXT" -TITLE="Securing Samba" -HREF="securing-samba.html"></HEAD +TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide" +HREF="browsing-quick.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -45,7 +46,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="integrate-ms-networks.html" +HREF="install.html" ACCESSKEY="P" >Prev</A ></TD @@ -59,7 +60,7 @@ WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A -HREF="securing-samba.html" +HREF="browsing-quick.html" ACCESSKEY="N" >Next</A ></TD @@ -72,23 +73,16 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="IMPROVED-BROWSING" -></A ->Chapter 23. Improved browsing in samba</H1 +NAME="IMPROVED-BROWSING">Chapter 2. Improved browsing in samba</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3804" ->23.1. Overview of browsing</A -></H1 +NAME="AEN229">2.1. Overview of browsing</H1 ><P >SMB networking provides a mechanism by which clients can access a list -of machines in a network, a so-called <B -CLASS="COMMAND" ->browse list</B ->. This list +of machines in a network, a so-called "browse list". This list contains machines that are ready to offer file and/or print services to other machines within the network. Thus it does not include machines which aren't currently able to do server tasks. The browse @@ -96,13 +90,8 @@ list is heavily used by all SMB clients. Configuration of SMB browsing has been problematic for some Samba users, hence this document.</P ><P ->MS Windows 2000 and later, as with Samba 3 and later, can be -configured to not use NetBIOS over TCP/IP. When configured this way -it is imperative that name resolution (using DNS/LDAP/ADS) be correctly -configured and operative. Browsing will NOT work if name resolution -from SMB machine names to IP addresses does not function correctly.</P -><P ->Where NetBIOS over TCP/IP is enabled use of a WINS server is highly +>Browsing will NOT work if name resolution from NetBIOS names to IP +addresses does not function correctly. Use of a WINS server is highly recommended to aid the resolution of NetBIOS (SMB) names to IP addresses. WINS allows remote segment clients to obtain NetBIOS name_type information that can NOT be provided by any other means of name resolution.</P @@ -112,20 +101,14 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3810" ->23.2. Browsing support in samba</A -></H1 -><P ->Samba facilitates browsing. The browsing is supported by <SPAN -CLASS="APPLICATION" ->nmbd</SPAN -> -and is also controlled by options in the <TT -CLASS="FILENAME" ->smb.conf</TT -> file. -Samba can act as a local browse master for a workgroup and the ability -for samba to support domain logons and scripts is now available.</P +NAME="AEN233">2.2. Browsing support in samba</H1 +><P +>Samba now fully supports browsing. The browsing is supported by nmbd +and is also controlled by options in the smb.conf file (see smb.conf(5)).</P +><P +>Samba can act as a local browse master for a workgroup and the ability +for samba to support domain logons and scripts is now available. See +DOMAIN.txt for more information on domain logons.</P ><P >Samba can also act as a domain master browser for a workgroup. This means that it will collate lists from local browse masters into a @@ -138,123 +121,64 @@ workgroup that has the same name as an NT Domain: on each wide area network, you must only ever have one domain master browser per workgroup, regardless of whether it is NT, Samba or any other type of domain master that is providing this service.</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 ->Nmbd can be configured as a WINS server, but it is not -necessary to specifically use samba as your WINS server. MS Windows -NT4, Server or Advanced Server 2000 or 2003 can be configured as -your WINS server. In a mixed NT/2000/2003 server and samba environment on -a Wide Area Network, it is recommended that you use the Microsoft -WINS server capabilities. In a samba-only environment, it is -recommended that you use one and only one Samba server as your WINS server.</P -></TD -></TR -></TABLE -></DIV +>[Note that nmbd can be configured as a WINS server, but it is not +necessary to specifically use samba as your WINS server. NTAS can +be configured as your WINS server. In a mixed NT server and +samba environment on a Wide Area Network, it is recommended that +you use the NT server's WINS server capabilities. In a samba-only +environment, it is recommended that you use one and only one nmbd +as your WINS server].</P ><P >To get browsing to work you need to run nmbd as usual, but will need -to use the <B -CLASS="COMMAND" ->workgroup</B -> option in <TT -CLASS="FILENAME" ->smb.conf</TT -> -to control what workgroup Samba becomes a part of.</P +to use the "workgroup" option in smb.conf to control what workgroup +Samba becomes a part of.</P ><P >Samba also has a useful option for a Samba server to offer itself for browsing on another subnet. It is recommended that this option is only used for 'unusual' purposes: announcements over the internet, for -example. See <B -CLASS="COMMAND" ->remote announce</B -> in the -<TT -CLASS="FILENAME" ->smb.conf</TT -> man page. </P +example. See "remote announce" in the smb.conf man page. </P ></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3825" ->23.3. Problem resolution</A -></H1 +NAME="AEN242">2.3. Problem resolution</H1 ><P >If something doesn't work then hopefully the log.nmb file will help you track down the problem. Try a debug level of 2 or 3 for finding problems. Also note that the current browse list usually gets stored -in text form in a file called <TT -CLASS="FILENAME" ->browse.dat</TT ->.</P +in text form in a file called browse.dat.</P ><P >Note that if it doesn't work for you, then you should still be able to -type the server name as <TT -CLASS="FILENAME" ->\\SERVER</TT -> in filemanager then -hit enter and filemanager should display the list of available shares.</P +type the server name as \\SERVER in filemanager then hit enter and +filemanager should display the list of available shares.</P ><P >Some people find browsing fails because they don't have the global -<B -CLASS="COMMAND" ->guest account</B -> set to a valid account. Remember that the -IPC$ connection that lists the shares is done as guest, and thus you must +"guest account" set to a valid account. Remember that the IPC$ +connection that lists the shares is done as guest, and thus you must have a valid guest account.</P ><P -><SPAN -CLASS="emphasis" -><I -CLASS="EMPHASIS" ->MS Windows 2000 and upwards (as with Samba) can be configured to disallow -anonymous (ie: Guest account) access to the IPC$ share. In that case, the -MS Windows 2000/XP/2003 machine acting as an SMB/CIFS client will use the -name of the currently logged in user to query the IPC$ share. MS Windows -9X clients are not able to do this and thus will NOT be able to browse -server resources.</I -></SPAN -></P +>Also, a lot of people are getting bitten by the problem of too many +parameters on the command line of nmbd in inetd.conf. This trick is to +not use spaces between the option and the parameter (eg: -d2 instead +of -d 2), and to not use the -B and -N options. New versions of nmbd +are now far more likely to correctly find your broadcast and network +address, so in most cases these aren't needed.</P ><P >The other big problem people have is that their broadcast address, netmask or IP address is wrong (specified with the "interfaces" option -in <TT -CLASS="FILENAME" ->smb.conf</TT ->)</P +in smb.conf)</P ></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3837" ->23.4. Browsing across subnets</A -></H1 +NAME="AEN249">2.4. Browsing across subnets</H1 ><P ->Since the release of Samba 1.9.17(alpha1) Samba has been +>With the release of Samba 1.9.17(alpha1 and above) Samba has been updated to enable it to support the replication of browse lists across subnet boundaries. New code and options have been added to achieve this. This section describes how to set this feature up @@ -275,23 +199,19 @@ another subnet without using a WINS server.</P be they Windows 95, Windows NT, or Samba servers must have the IP address of a WINS server given to them by a DHCP server, or by manual configuration (for Win95 and WinNT, this is in the TCP/IP Properties, under Network -settings) for Samba this is in the <TT -CLASS="FILENAME" ->smb.conf</TT -> file.</P +settings) for Samba this is in the smb.conf file.</P ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN3843" ->23.4.1. How does cross subnet browsing work ?</A -></H2 +NAME="AEN254">2.4.1. How does cross subnet browsing work ?</H2 ><P >Cross subnet browsing is a complicated dance, containing multiple moving parts. It has taken Microsoft several years to get the code that achieves this correct, and Samba lags behind in some areas. -Samba is capable of cross subnet browsing when configured correctly.</P +However, with the 1.9.17 release, Samba is capable of cross subnet +browsing when configured correctly.</P ><P >Consider a network set up as follows :</P ><P @@ -372,7 +292,7 @@ machine is seen across any of the subnets.</P master browser it looks for a Domain master browser to synchronize its browse list with. It does this by querying the WINS server (N2_D) for the IP address associated with the NetBIOS name -WORKGROUP>1B<. This name was registerd by the Domain master +WORKGROUP>1B<. This name was registerd by the Domain master browser (N1_C) with the WINS server as soon as it was booted.</P ><P >Once N2_B knows the address of the Domain master browser it @@ -495,16 +415,11 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3878" ->23.5. Setting up a WINS server</A -></H1 +NAME="AEN289">2.5. Setting up a WINS server</H1 ><P >Either a Samba machine or a Windows NT Server machine may be set up as a WINS server. To set a Samba machine to be a WINS server you must -add the following option to the <TT -CLASS="FILENAME" ->smb.conf</TT -> file on the selected machine : +add the following option to the smb.conf file on the selected machine : in the [globals] section add the line </P ><P ><B @@ -512,22 +427,22 @@ CLASS="COMMAND" > wins support = yes</B ></P ><P ->Versions of Samba prior to 1.9.17 had this parameter default to +>Versions of Samba previous to 1.9.17 had this parameter default to yes. If you have any older versions of Samba on your network it is -strongly suggested you upgrade to a recent version, or at the very +strongly suggested you upgrade to 1.9.17 or above, or at the very least set the parameter to 'no' on all these machines.</P ><P ->Machines with <B +>Machines with "<B CLASS="COMMAND" >wins support = yes</B -> will keep a list of +>" will keep a list of all NetBIOS names registered with them, acting as a DNS for NetBIOS names.</P ><P >You should set up only ONE wins server. Do NOT set the -<B +"<B CLASS="COMMAND" >wins support = yes</B -> option on more than one Samba +>" option on more than one Samba server.</P ><P >To set up a Windows NT Server as a WINS server you need to set up @@ -538,11 +453,8 @@ refuse to document these replication protocols Samba cannot currently participate in these replications. It is possible in the future that a Samba->Samba WINS replication protocol may be defined, in which case more than one Samba machine could be set up as a WINS server -but currently only one Samba server should have the -<B -CLASS="COMMAND" ->wins support = yes</B -> parameter set.</P +but currently only one Samba server should have the "wins support = yes" +parameter set.</P ><P >After the WINS server has been configured you must ensure that all machines participating on the network are configured with the address @@ -551,32 +463,26 @@ the Samba machine IP address in the "Primary WINS Server" field of the "Control Panel->Network->Protocols->TCP->WINS Server" dialogs in Windows 95 or Windows NT. To tell a Samba server the IP address of the WINS server add the following line to the [global] section of -all <TT -CLASS="FILENAME" ->smb.conf</TT -> files :</P +all smb.conf files :</P ><P ><B CLASS="COMMAND" ->wins server = >name or IP address<</B +>wins server = >name or IP address<</B ></P ><P ->where >name or IP address< is either the DNS name of the WINS server +>where >name or IP address< is either the DNS name of the WINS server machine or its IP address.</P ><P ->Note that this line MUST NOT BE SET in the <TT -CLASS="FILENAME" ->smb.conf</TT -> file of the Samba +>Note that this line MUST NOT BE SET in the smb.conf file of the Samba server acting as the WINS server itself. If you set both the -<B +"<B CLASS="COMMAND" >wins support = yes</B -> option and the -<B +>" option and the +"<B CLASS="COMMAND" ->wins server = <name></B -> option then +>wins server = >name<</B +>" option then nmbd will fail to start.</P ><P >There are two possible scenarios for setting up cross subnet browsing. @@ -590,9 +496,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3901" ->23.6. Setting up Browsing in a WORKGROUP</A -></H1 +NAME="AEN308">2.6. Setting up Browsing in a WORKGROUP</H1 ><P >To set up cross subnet browsing on a network containing machines in up to be in a WORKGROUP, not an NT Domain you need to set up one @@ -609,10 +513,7 @@ cross subnet browsing possible for a workgroup.</P >In an WORKGROUP environment the domain master browser must be a Samba server, and there must only be one domain master browser per workgroup name. To set up a Samba server as a domain master browser, -set the following option in the [global] section of the <TT -CLASS="FILENAME" ->smb.conf</TT -> file :</P +set the following option in the [global] section of the smb.conf file :</P ><P ><B CLASS="COMMAND" @@ -621,17 +522,14 @@ CLASS="COMMAND" ><P >The domain master browser should also preferrably be the local master browser for its own subnet. In order to achieve this set the following -options in the [global] section of the <TT -CLASS="FILENAME" ->smb.conf</TT -> file :</P +options in the [global] section of the smb.conf file :</P ><P ><PRE CLASS="PROGRAMLISTING" ->domain master = yes -local master = yes -preferred master = yes -os level = 65</PRE +> domain master = yes + local master = yes + preferred master = yes + os level = 65</PRE ></P ><P >The domain master browser may be the same machine as the WINS @@ -639,60 +537,40 @@ server, if you require.</P ><P >Next, you should ensure that each of the subnets contains a machine that can act as a local master browser for the -workgroup. Any MS Windows NT/2K/XP/2003 machine should be -able to do this, as will Windows 9x machines (although these -tend to get rebooted more often, so it's not such a good idea -to use these). To make a Samba server a local master browser -set the following options in the [global] section of the -<TT -CLASS="FILENAME" ->smb.conf</TT -> file :</P +workgroup. Any NT machine should be able to do this, as will +Windows 95 machines (although these tend to get rebooted more +often, so it's not such a good idea to use these). To make a +Samba server a local master browser set the following +options in the [global] section of the smb.conf file :</P ><P ><PRE CLASS="PROGRAMLISTING" ->domain master = no -local master = yes -preferred master = yes -os level = 65</PRE +> domain master = no + local master = yes + preferred master = yes + os level = 65</PRE ></P ><P >Do not do this for more than one Samba server on each subnet, or they will war with each other over which is to be the local master browser.</P ><P ->The <B -CLASS="COMMAND" ->local master</B -> parameter allows Samba to act as a -local master browser. The <B -CLASS="COMMAND" ->preferred master</B -> causes nmbd -to force a browser election on startup and the <B -CLASS="COMMAND" ->os level</B -> -parameter sets Samba high enough so that it should win any browser elections.</P +>The "local master" parameter allows Samba to act as a local master +browser. The "preferred master" causes nmbd to force a browser +election on startup and the "os level" parameter sets Samba high +enough so that it should win any browser elections.</P ><P >If you have an NT machine on the subnet that you wish to be the local master browser then you can disable Samba from becoming a local master browser by setting the following -options in the <B -CLASS="COMMAND" ->[global]</B -> section of the -<TT -CLASS="FILENAME" ->smb.conf</TT -> file :</P +options in the [global] section of the smb.conf file :</P ><P ><PRE CLASS="PROGRAMLISTING" ->domain master = no -local master = no -preferred master = no -os level = 0</PRE +> domain master = no + local master = no + preferred master = no + os level = 0</PRE ></P ></DIV ><DIV @@ -700,66 +578,41 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3927" ->23.7. Setting up Browsing in a DOMAIN</A -></H1 +NAME="AEN326">2.7. Setting up Browsing in a DOMAIN</H1 ><P >If you are adding Samba servers to a Windows NT Domain then you must not set up a Samba server as a domain master browser. By default, a Windows NT Primary Domain Controller for a Domain name is also the Domain master browser for that name, and many things will break if a Samba server registers the Domain master -browser NetBIOS name (<VAR -CLASS="REPLACEABLE" ->DOMAIN</VAR -><1B>) -with WINS instead of the PDC.</P +browser NetBIOS name (DOMAIN>1B<) with WINS instead of the PDC.</P ><P >For subnets other than the one containing the Windows NT PDC you may set up Samba servers as local master browsers as described. To make a Samba server a local master browser set -the following options in the <B -CLASS="COMMAND" ->[global]</B -> section -of the <TT -CLASS="FILENAME" ->smb.conf</TT -> file :</P +the following options in the [global] section of the smb.conf +file :</P ><P ><PRE CLASS="PROGRAMLISTING" ->domain master = no -local master = yes -preferred master = yes -os level = 65</PRE +> domain master = no + local master = yes + preferred master = yes + os level = 65</PRE ></P ><P >If you wish to have a Samba server fight the election with machines -on the same subnet you may set the <B -CLASS="COMMAND" ->os level</B -> parameter -to lower levels. By doing this you can tune the order of machines that +on the same subnet you may set the "os level" parameter to lower +levels. By doing this you can tune the order of machines that will become local master browsers if they are running. For -more details on this see the section <A -HREF="improved-browsing.html#BROWSE-FORCE-MASTER" ->Forcing samba to be the master browser</A -> +more details on this see the section "FORCING SAMBA TO BE THE MASTER" below.</P ><P >If you have Windows NT machines that are members of the domain on all subnets, and you are sure they will always be running then you can disable Samba from taking part in browser elections and ever becoming a local master browser by setting following options -in the <B -CLASS="COMMAND" ->[global]</B -> section of the <TT -CLASS="FILENAME" ->smb.conf</TT -> -file :</P +in the [global] section of the smb.conf file :</P ><P ><B CLASS="COMMAND" @@ -774,64 +627,35 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="BROWSE-FORCE-MASTER" ->23.8. Forcing samba to be the master</A -></H1 +NAME="AEN336">2.8. Forcing samba to be the master</H1 ><P ->Who becomes the <B -CLASS="COMMAND" ->master browser</B -> is determined by an election -process using broadcasts. Each election packet contains a number of parameters +>Who becomes the "master browser" is determined by an election process +using broadcasts. Each election packet contains a number of parameters which determine what precedence (bias) a host should have in the election. By default Samba uses a very low precedence and thus loses elections to just about anyone else.</P ><P ->If you want Samba to win elections then just set the <B -CLASS="COMMAND" ->os level</B -> global -option in <TT -CLASS="FILENAME" ->smb.conf</TT -> to a higher number. It defaults to 0. Using 34 +>If you want Samba to win elections then just set the "os level" global +option in smb.conf to a higher number. It defaults to 0. Using 34 would make it win all elections over every other system (except other samba systems!)</P ><P ->A <B -CLASS="COMMAND" ->os level</B -> of 2 would make it beat WfWg and Win95, but not MS Windows -NT/2K Server. A MS Windows NT/2K Server domain controller uses level 32.</P +>A "os level" of 2 would make it beat WfWg and Win95, but not NTAS. A +NTAS domain controller uses level 32.</P ><P >The maximum os level is 255</P ><P >If you want samba to force an election on startup, then set the -<B -CLASS="COMMAND" ->preferred master</B -> global option in <TT -CLASS="FILENAME" ->smb.conf</TT -> to "yes". Samba will +"preferred master" global option in smb.conf to "yes". Samba will then have a slight advantage over other potential master browsers that are not preferred master browsers. Use this parameter with care, as if you have two hosts (whether they are windows 95 or NT or -samba) on the same local subnet both set with <B -CLASS="COMMAND" ->preferred master</B -> to +samba) on the same local subnet both set with "preferred master" to "yes", then periodically and continually they will force an election in order to become the local master browser.</P ><P ->If you want samba to be a <B -CLASS="COMMAND" ->domain master browser</B ->, then it is -recommended that you also set <B -CLASS="COMMAND" ->preferred master</B -> to "yes", because +>If you want samba to be a "domain master browser", then it is +recommended that you also set "preferred master" to "yes", because samba will not become a domain master browser for the whole of your LAN or WAN if it is not also a local master browser on its own broadcast isolated subnet.</P @@ -849,20 +673,12 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3962" ->23.9. Making samba the domain master</A -></H1 +NAME="AEN345">2.9. Making samba the domain master</H1 ><P >The domain master is responsible for collating the browse lists of multiple subnets so that browsing can occur between subnets. You can -make samba act as the domain master by setting <B -CLASS="COMMAND" ->domain master = yes</B -> -in <TT -CLASS="FILENAME" ->smb.conf</TT ->. By default it will not be a domain master.</P +make samba act as the domain master by setting "domain master = yes" +in smb.conf. By default it will not be a domain master.</P ><P >Note that you should NOT set Samba to be the domain master for a workgroup that has the same name as an NT Domain.</P @@ -873,14 +689,8 @@ master browsers on other subnets and then contact them to synchronise browse lists.</P ><P >If you want samba to be the domain master then I suggest you also set -the <B -CLASS="COMMAND" ->os level</B -> high enough to make sure it wins elections, and set -<B -CLASS="COMMAND" ->preferred master</B -> to "yes", to get samba to force an election on +the "os level" high enough to make sure it wins elections, and set +"preferred master" to "yes", to get samba to force an election on startup.</P ><P >Note that all your servers (including samba) and clients should be @@ -934,9 +744,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3984" ->23.10. Note about broadcast addresses</A -></H1 +NAME="AEN363">2.10. Note about broadcast addresses</H1 ><P >If your network uses a "0" based broadcast address (for example if it ends in a 0) then you will strike problems. Windows for Workgroups @@ -948,19 +756,11 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN3987" ->23.11. Multiple interfaces</A -></H1 +NAME="AEN366">2.11. Multiple interfaces</H1 ><P >Samba now supports machines with multiple network interfaces. If you -have multiple interfaces then you will need to use the <B -CLASS="COMMAND" ->interfaces</B -> -option in <TT -CLASS="FILENAME" ->smb.conf</TT -> to configure them. </P +have multiple interfaces then you will need to use the "interfaces" +option in smb.conf to configure them. See smb.conf(5) for details.</P ></DIV ></DIV ><DIV @@ -979,7 +779,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="integrate-ms-networks.html" +HREF="install.html" ACCESSKEY="P" >Prev</A ></TD @@ -997,7 +797,7 @@ WIDTH="33%" ALIGN="right" VALIGN="top" ><A -HREF="securing-samba.html" +HREF="browsing-quick.html" ACCESSKEY="N" >Next</A ></TD @@ -1007,13 +807,13 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Integrating MS Windows networks with Samba</TD +>How to Install and Test SAMBA</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A -HREF="optional.html" +HREF="introduction.html" ACCESSKEY="U" >Up</A ></TD @@ -1021,7 +821,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" ->Securing Samba</TD +>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TD ></TR ></TABLE ></DIV |