Ignore:
Timestamp:
Sep 30, 2008, 7:14:08 AM (17 years ago)
Author:
Paul Smedley
Message:

Update source to 3.0.32

File:
1 edited

Legend:

Unmodified
Added
Removed

  • branches/samba-3.0/docs/htmldocs/Samba3-HOWTO/NetworkBrowsing.html

    r134 r158  
    1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 10. Network Browsing</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><link rel="start" href="index.html" title="The Official Samba 3.2.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="ChangeNotes.html" title="Chapter 9. Important and Critical Change Notes for the Samba 3.x Series"><link rel="next" href="passdb.html" title="Chapter 11. Account Information Databases"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 10. Network Browsing</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ChangeNotes.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="passdb.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="NetworkBrowsing"></a>Chapter 10. Network Browsing</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:[email protected]">[email protected]</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:[email protected]">[email protected]</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jonathan</span> <span class="surname">Johnson</span></h3><div class="affiliation"><span class="orgname">Sutinen Consulting, Inc.<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:[email protected]">[email protected]</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">July 5, 1998</p></div><div><p class="pubdate">Updated: September 20, 2006</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="NetworkBrowsing.html#id367309">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="NetworkBrowsing.html#id367475">What Is Browsing?</a></span></dt><dt><span class="sect1"><a href="NetworkBrowsing.html#netdiscuss">Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id367888">NetBIOS over TCP/IP</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id368472">TCP/IP without NetBIOS</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#adsdnstech">DNS and Active Directory</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id368969">How Browsing Functions</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#DMB">Configuring Workgroup Browsing</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id369843">Domain Browsing Configuration</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#browse-force-master">Forcing Samba to Be the Master</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id370405">Making Samba the Domain Master</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id370625">Note about Broadcast Addresses</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id370644">Multiple Interfaces</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id370820">Use of the Remote Announce Parameter</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id370948">Use of the Remote Browse Sync Parameter</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id371035">WINS: The Windows Internetworking Name Server</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id371282">WINS Server Configuration</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id371576">WINS Replication</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id371626">Static WINS Entries</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id371843">Helpful Hints</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id371853">Windows Networking Protocols</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id371983">Name Resolution Order</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id372177">Technical Overview of Browsing</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id372256">Browsing Support in Samba</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id372438">Problem Resolution</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id372672">Cross-Subnet Browsing</a></span></dt></dl></dd><dt><span class="sect1"><a href="NetworkBrowsing.html#id373613">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="NetworkBrowsing.html#id373637">Flushing the Samba NetBIOS Name Cache</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id373702">Server Resources Cannot Be Listed</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id373747">I Get an "<span class="errorname">Unable to browse the network</span>" Error</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id373792">Browsing of Shares and Directories is Very Slow</a></span></dt><dt><span class="sect2"><a href="NetworkBrowsing.html#id373973">Invalid Cached Share References Affects Network Browsing</a></span></dt></dl></dd></dl></div><p>
    2 <a class="indexterm" name="id367228"></a>
    3 <a class="indexterm" name="id367234"></a>
    4 <a class="indexterm" name="id367241"></a>
    5 <a class="indexterm" name="id367248"></a>
     1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 10. Network Browsing</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><link rel="start" href="index.html" title="The Official Samba 3.2.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="ChangeNotes.html" title="Chapter 9. Important and Critical Change Notes for the Samba 3.x Series"><link rel="next" href="passdb.html" title="Chapter 11. Account Information Databases"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 10. Network Browsing</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ChangeNotes.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="passdb.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="NetworkBrowsing"></a>Chapter 10. Network Browsing</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:[email protected]">[email protected]</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:[email protected]">[email protected]</a>&gt;</code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jonathan</span> <span class="surname">Johnson</span></h3><div class="affiliation"><span class="orgname">Sutinen Consulting, Inc.<br></span><div class="address"><p><code class="email">&lt;<a class="email" href="mailto:[email protected]">[email protected]</a>&gt;</code></p></div></div></div></div><div><p class="pubdate">July 5, 1998</p></div><div><p class="pubdate">Updated: September 20, 2006</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="NetworkBrowsing.html#id3">Invalid Cached Share References Affects Network Browsing</a></span></dt></dl></dd></dl></div><p>
     2<a class="indexterm" name="id3"></a>
     3<a class="indexterm" name="id3"></a>
     4<a class="indexterm" name="id3"></a>
     5<a class="indexterm" name="id3"></a>
    66This chapter contains detailed information as well as a fast-track guide to
    77implementing browsing across subnets and/or across workgroups (or domains).
    … …  
    99not involved in browse list handling except by way of name-to-address resolution.
    1010</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    11 <a class="indexterm" name="id367262"></a>
     11<a class="indexterm" name="id3"></a>
    1212What is WINS?
    1313</p><p>
    … …  
    1515Dynamic-DNS service for NetBIOS networking names.
    1616</p></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    17 <a class="indexterm" name="id367278"></a>
    18 <a class="indexterm" name="id367285"></a>
    19 <a class="indexterm" name="id367292"></a>
    20 <a class="indexterm" name="id367298"></a>
     17<a class="indexterm" name="id3"></a>
     18<a class="indexterm" name="id3"></a>
     19<a class="indexterm" name="id3"></a>
     20<a class="indexterm" name="id3"></a>
    2121MS Windows 2000 and later versions can be configured to operate with no NetBIOS
    2222over TCP/IP. Samba-3 and later versions also support this mode of operation.
    … …  
    2424means for resolution of MS Windows machine names is via DNS and Active Directory.
    2525The following information assumes that your site is running NetBIOS over TCP/IP.
    26 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id367309"></a>Features and Benefits</h2></div></div></div><p>
     26</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3"></a>Features and Benefits</h2></div></div></div><p>
    2727Charles Dickens once referred to the past in these words: &#8220;<span class="quote"><span class="emphasis"><em>It was the best of times,
    2828it was the worst of times.</em></span></span>&#8221; The more we look back, the more we long for what was and
    2929hope it never returns.
    3030</p><p>
    31 <a class="indexterm" name="id367326"></a>
    32 <a class="indexterm" name="id367333"></a>
    33 <a class="indexterm" name="id367340"></a>
     31<a class="indexterm" name="id3"></a>
     32<a class="indexterm" name="id3"></a>
     33<a class="indexterm" name="id3"></a>
    3434For many MS Windows network administrators, that statement sums up their feelings about
    3535NetBIOS networking precisely. For those who mastered NetBIOS networking, its fickle
    … …  
    4444features that make it such a persistent weed.
    4545</p><p>
    46 <a class="indexterm" name="id367363"></a>
    47 <a class="indexterm" name="id367372"></a>
    48 <a class="indexterm" name="id367379"></a>
    49 <a class="indexterm" name="id367386"></a>
    50 <a class="indexterm" name="id367393"></a>
     46<a class="indexterm" name="id3"></a>
     47<a class="indexterm" name="id3"></a>
     48<a class="indexterm" name="id3"></a>
     49<a class="indexterm" name="id3"></a>
     50<a class="indexterm" name="id3"></a>
    5151In this chapter we explore vital aspects of Server Message Block (SMB) networking with
    5252a particular focus on SMB as implemented through running NetBIOS (Network Basic
    … …  
    5555remember to use nothing but TCP/IP on all our MS Windows network clients.
    5656</p><p>
    57 <a class="indexterm" name="id367406"></a>
    58 <a class="indexterm" name="id367413"></a>
     57<a class="indexterm" name="id3"></a>
     58<a class="indexterm" name="id3"></a>
    5959Samba provides the ability to implement a WINS (Windows Internetworking Name Server)
    6060and implements extensions to Microsoft's implementation of WINS. These extensions
    6161help Samba to effect stable WINS operations beyond the normal scope of MS WINS.
    6262</p><p>
    63 <a class="indexterm" name="id367425"></a>
    64 <a class="indexterm" name="id367432"></a>
    65 <a class="indexterm" name="id367439"></a>
     63<a class="indexterm" name="id3"></a>
     64<a class="indexterm" name="id3"></a>
     65<a class="indexterm" name="id3"></a>
    6666WINS is exclusively a service that applies only to those systems
    6767that run NetBIOS over TCP/IP. MS Windows 200x/XP have the capacity to operate with
    6868support for NetBIOS disabled, in which case WINS is of no relevance. Samba supports this also.
    6969</p><p>
    70 <a class="indexterm" name="id367451"></a>
    71 <a class="indexterm" name="id367458"></a>
    72 <a class="indexterm" name="id367464"></a>
     70<a class="indexterm" name="id3"></a>
     71<a class="indexterm" name="id3"></a>
     72<a class="indexterm" name="id3"></a>
    7373For those networks on which NetBIOS has been disabled (i.e., WINS is not required),
    7474the use of DNS is necessary for hostname resolution.
    75 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id367475"></a>What Is Browsing?</h2></div></div></div><p>
    76 <a class="indexterm" name="id367482"></a>
    77 <a class="indexterm" name="id367489"></a>
    78 <a class="indexterm" name="id367496"></a>
    79 <a class="indexterm" name="id367503"></a>
     75</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3"></a>What Is Browsing?</h2></div></div></div><p>
     76<a class="indexterm" name="id3"></a>
     77<a class="indexterm" name="id3"></a>
     78<a class="indexterm" name="id3"></a>
     79<a class="indexterm" name="id3"></a>
    8080To most people, browsing means they can see the MS Windows and Samba servers
    8181in the Network Neighborhood, and when the computer icon for a particular server is
    … …  
    8585The technologies (or methods) employed in making all of this work include:
    8686</p><div class="itemizedlist"><ul type="disc"><li><p>MS Windows machines register their presence to the network.</p></li><li><p>Machines announce themselves to other machines on the network.</p></li><li><p>One or more machines on the network collate the local announcements.</p></li><li><p>The client machine finds the machine that has the collated list of machines.</p></li><li><p>The client machine is able to resolve the machine names to IP addresses.</p></li><li><p>The client machine is able to connect to a target machine.</p></li></ul></div><p>
    87 <a class="indexterm" name="id367553"></a>
    88 <a class="indexterm" name="id367560"></a>
    89 <a class="indexterm" name="id367566"></a>
     87<a class="indexterm" name="id3"></a>
     88<a class="indexterm" name="id3"></a>
     89<a class="indexterm" name="id3"></a>
    9090The Samba application that controls browse list management and name resolution is
    9191called <code class="filename">nmbd</code>. The configuration parameters involved in nmbd's operation are:
    … …  
    100100parameters is set, <code class="filename">nmbd</code> will still do its job.
    101101</p><p>
    102 <a class="indexterm" name="id367790"></a>
    103 <a class="indexterm" name="id367797"></a>
    104 <a class="indexterm" name="id367804"></a>
    105 <a class="indexterm" name="id367810"></a>
    106 <a class="indexterm" name="id367817"></a>
     102<a class="indexterm" name="id3"></a>
     103<a class="indexterm" name="id3"></a>
     104<a class="indexterm" name="id3"></a>
     105<a class="indexterm" name="id3"></a>
     106<a class="indexterm" name="id3"></a>
    107107For Samba, the WINS Server and WINS Support are mutually exclusive options. When <code class="literal">nmbd</code> is
    108108started it will fail to execute if both options are set in the <code class="filename">smb.conf</code> file. The <code class="literal">nmbd</code>
    … …  
    110110server also.
    111111</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="netdiscuss"></a>Discussion</h2></div></div></div><p>
    112 <a class="indexterm" name="id367857"></a>
    113 <a class="indexterm" name="id367864"></a>
    114 <a class="indexterm" name="id367871"></a>
    115 <a class="indexterm" name="id367878"></a>
     112<a class="indexterm" name="id3"></a>
     113<a class="indexterm" name="id3"></a>
     114<a class="indexterm" name="id3"></a>
     115<a class="indexterm" name="id3"></a>
    116116All MS Windows networking uses SMB-based messaging.  SMB messaging may be implemented with or without NetBIOS.
    117117MS Windows 200x supports NetBIOS over TCP/IP for backwards compatibility. Microsoft appears intent on phasing
    118118out NetBIOS support.
    119 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id367888"></a>NetBIOS over TCP/IP</h3></div></div></div><p>
    120 <a class="indexterm" name="id367895"></a>
    121 <a class="indexterm" name="id367902"></a>
    122 <a class="indexterm" name="id367909"></a>
    123 <a class="indexterm" name="id367916"></a>
     119</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>NetBIOS over TCP/IP</h3></div></div></div><p>
     120<a class="indexterm" name="id3"></a>
     121<a class="indexterm" name="id3"></a>
     122<a class="indexterm" name="id3"></a>
     123<a class="indexterm" name="id3"></a>
    124124Samba implements NetBIOS, as does MS Windows NT/200x/XP, by encapsulating it over TCP/IP.
    125125NetBIOS-based networking uses broadcast messaging to effect browse list management. When running NetBIOS over
    126126TCP/IP, this uses UDP-based messaging.  UDP messages can be broadcast or unicast.
    127127</p><p>
    128 <a class="indexterm" name="id367928"></a>
     128<a class="indexterm" name="id3"></a>
    129129Normally, only unicast UDP messaging can be forwarded by routers. The <a class="link" href="smb.conf.5.html#REMOTEANNOUNCE">remote announce</a>
    130130parameter to smb.conf helps to project browse announcements to remote network segments via unicast UDP.
    … …  
    134134The methods used by MS Windows to perform name lookup requests (name resolution) is determined by a
    135135configuration parameter called the NetBIOS node-type. There are four basic NetBIOS node types:
    136 </p><a class="indexterm" name="id367970"></a><a class="indexterm" name="id367977"></a><a class="indexterm" name="id367984"></a><a class="indexterm" name="id367991"></a><a class="indexterm" name="id367998"></a><a class="indexterm" name="id368004"></a><a class="indexterm" name="id368011"></a><a class="indexterm" name="id368018"></a><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>b-node (type 0x01):</em></span> The Windows client will use only
     136</p><a class="indexterm" name="id3"></a><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>b-node (type 0x01):</em></span> The Windows client will use only
    137137        NetBIOS broadcast requests using UDP broadcast.</p></li><li><p><span class="emphasis"><em>p-node (type 0x02):</em></span> The Windows client will use point-to-point
    138138        (NetBIOS unicast) requests using UDP unicast directed to a WINS server.</p></li><li><p><span class="emphasis"><em>m-node (type 0x04):</em></span> The Windows client will first use
    … …  
    141141        (NetBIOS unicast) requests using UDP unicast directed to a WINS server, then it will use
    142142        NetBIOS broadcast requests using UDP broadcast.</p></li></ul></div><p>
    143 <a class="indexterm" name="id368062"></a>
    144 <a class="indexterm" name="id368069"></a>
    145 <a class="indexterm" name="id368075"></a>
    146 <a class="indexterm" name="id368082"></a>
    147 <a class="indexterm" name="id368089"></a>
    148 <a class="indexterm" name="id368096"></a>
     143<a class="indexterm" name="id3"></a>
     144<a class="indexterm" name="id3"></a>
     145<a class="indexterm" name="id3"></a>
     146<a class="indexterm" name="id3"></a>
     147<a class="indexterm" name="id3"></a>
     148<a class="indexterm" name="id3"></a>
    149149The default Windows network client (or server) network configuration enables NetBIOS over TCP/IP
    150150and b-node configuration. The use of WINS makes most sense with h-node (hybrid mode) operation so that
    151151in the event of a WINS breakdown or non-availability, the client can use broadcast-based name resolution.
    152152</p><p>
    153 <a class="indexterm" name="id368109"></a>
    154 <a class="indexterm" name="id368118"></a>
    155 <a class="indexterm" name="id368124"></a>
    156 <a class="indexterm" name="id368131"></a>
    157 <a class="indexterm" name="id368138"></a>
    158 <a class="indexterm" name="id368144"></a>
    159 <a class="indexterm" name="id368151"></a>
     153<a class="indexterm" name="id3"></a>
     154<a class="indexterm" name="id3"></a>
     155<a class="indexterm" name="id3"></a>
     156<a class="indexterm" name="id3"></a>
     157<a class="indexterm" name="id3"></a>
     158<a class="indexterm" name="id3"></a>
     159<a class="indexterm" name="id3"></a>
    160160In those networks where Samba is the only SMB server technology, wherever possible <code class="filename">nmbd</code>
    161161should be configured on one machine as the WINS server. This makes it easy to manage the browsing environment.
    … …  
    163163browsing to work is by using the <a class="link" href="smb.conf.5.html#REMOTEANNOUNCE">remote announce</a> and the <a class="link" href="smb.conf.5.html#REMOTEBROWSESYNC">remote browse sync</a> parameters to your <code class="filename">smb.conf</code> file.
    164164</p><p>
    165 <a class="indexterm" name="id368197"></a>
     165<a class="indexterm" name="id3"></a>
    166166If only one WINS server is used for an entire multisegment network, then
    167167the use of the <a class="link" href="smb.conf.5.html#REMOTEANNOUNCE">remote announce</a> and the
    168168<a class="link" href="smb.conf.5.html#REMOTEBROWSESYNC">remote browse sync</a> parameters should not be necessary.
    169169</p><p>
    170 <a class="indexterm" name="id368230"></a>
     170<a class="indexterm" name="id3"></a>
    171171As of Samba-3, WINS replication is being worked on. The bulk of the code has been committed, but it still
    172172needs maturation. This is not a supported feature of the Samba-3.0.20 release. Hopefully, this will become a
    … …  
    174174not been of sufficient significance to inspire someone to pay a developer to complete it.
    175175</p><p>
    176 <a class="indexterm" name="id368245"></a>
    177 <a class="indexterm" name="id368252"></a>
    178 <a class="indexterm" name="id368259"></a>
    179 <a class="indexterm" name="id368266"></a>
    180 <a class="indexterm" name="id368272"></a>
    181 <a class="indexterm" name="id368279"></a>
    182 <a class="indexterm" name="id368286"></a>
    183 <a class="indexterm" name="id368293"></a>
     176<a class="indexterm" name="id3"></a>
     177<a class="indexterm" name="id3"></a>
     178<a class="indexterm" name="id3"></a>
     179<a class="indexterm" name="id3"></a>
     180<a class="indexterm" name="id3"></a>
     181<a class="indexterm" name="id3"></a>
     182<a class="indexterm" name="id3"></a>
     183<a class="indexterm" name="id3"></a>
    184184Right now Samba WINS does not support MS-WINS replication. This means that when setting up Samba as a WINS
    185185server, there must only be one <code class="filename">nmbd</code> configured as a WINS server on the network. Some
    … …  
    195195clients are designed to use WINS.
    196196</p><p>
    197 <a class="indexterm" name="id368342"></a>
    198 <a class="indexterm" name="id368349"></a>
    199 <a class="indexterm" name="id368356"></a>
     197<a class="indexterm" name="id3"></a>
     198<a class="indexterm" name="id3"></a>
     199<a class="indexterm" name="id3"></a>
    200200Lastly, take note that browse lists are a collection of unreliable broadcast
    201201messages that are repeated at intervals of not more than 15 minutes. This means
    … …  
    203203minutes to stabilize, particularly across network segments.
    204204</p><p>
    205 <a class="indexterm" name="id368368"></a>
     205<a class="indexterm" name="id3"></a>
    206206When an MS Windows 200x/XP system attempts to resolve a host name to an IP address, it follows a defined path:
    207207</p><div class="orderedlist"><ol type="1"><li><p>
    … …  
    218218        Looks up entries in LMHOSTS, located in <code class="filename">%SystemRoot%\System32\Drivers\etc</code>.
    219219        </p></li></ol></div><p>
    220 <a class="indexterm" name="id368433"></a>
    221 <a class="indexterm" name="id368440"></a>
    222 <a class="indexterm" name="id368446"></a>
    223 <a class="indexterm" name="id368453"></a>
     220<a class="indexterm" name="id3"></a>
     221<a class="indexterm" name="id3"></a>
     222<a class="indexterm" name="id3"></a>
     223<a class="indexterm" name="id3"></a>
    224224Given the nature of how the NetBIOS over TCP/IP protocol is implemented, only WINS is capable of resolving
    225225with any reliability name lookups for service-oriented names such as TEMPTATION&lt;1C&gt;  a NetBIOS
    … …  
    228228service-oriented DNS entries. This type of facility is not implemented and is not supported for the NetBIOS
    229229over TCP/IP protocol namespace.
    230 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id368472"></a>TCP/IP without NetBIOS</h3></div></div></div><p>
    231 <a class="indexterm" name="id368479"></a>
    232 <a class="indexterm" name="id368485"></a>
    233 <a class="indexterm" name="id368492"></a>
     230</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>TCP/IP without NetBIOS</h3></div></div></div><p>
     231<a class="indexterm" name="id3"></a>
     232<a class="indexterm" name="id3"></a>
     233<a class="indexterm" name="id3"></a>
    234234All TCP/IP-enabled systems use various forms of hostname resolution. The primary
    235235methods for TCP/IP hostname resolution involve either a static file (<code class="filename">/etc/hosts</code>)
    … …  
    238238TCP/IP-enabled systems. Only a few embedded TCP/IP systems do not support DNS.
    239239</p><p>
    240 <a class="indexterm" name="id368511"></a>
    241 <a class="indexterm" name="id368518"></a>
    242 <a class="indexterm" name="id368524"></a>
    243 <a class="indexterm" name="id368531"></a>
     240<a class="indexterm" name="id3"></a>
     241<a class="indexterm" name="id3"></a>
     242<a class="indexterm" name="id3"></a>
     243<a class="indexterm" name="id3"></a>
    244244Windows 200x/XP can register its hostname with a Dynamic DNS server (DDNS). It is possible to force register with a
    245245dynamic DNS server in Windows 200x/XP using <code class="literal">ipconfig /registerdns</code>.
    246246</p><p>
    247 <a class="indexterm" name="id368551"></a>
    248 <a class="indexterm" name="id368557"></a>
    249 <a class="indexterm" name="id368564"></a>
     247<a class="indexterm" name="id3"></a>
     248<a class="indexterm" name="id3"></a>
     249<a class="indexterm" name="id3"></a>
    250250With Active Directory, a correctly functioning DNS server is absolutely essential. In the absence of a working
    251251DNS server that has been correctly configured, MS Windows clients and servers will be unable to locate each
    252252other, so network services consequently will be severely impaired.
    253253</p><p>
    254 <a class="indexterm" name="id368576"></a>
    255 <a class="indexterm" name="id368583"></a>
    256 <a class="indexterm" name="id368590"></a>
    257 <a class="indexterm" name="id368597"></a>
    258 <a class="indexterm" name="id368604"></a>
    259 <a class="indexterm" name="id368610"></a>
     254<a class="indexterm" name="id3"></a>
     255<a class="indexterm" name="id3"></a>
     256<a class="indexterm" name="id3"></a>
     257<a class="indexterm" name="id3"></a>
     258<a class="indexterm" name="id3"></a>
     259<a class="indexterm" name="id3"></a>
    260260Use of raw SMB over TCP/IP (No NetBIOS layer) can be done only with Active Directory domains. Samba is not an
    261261Active Directory domain controller: ergo, it is not possible to run Samba as a domain controller and at the same
    … …  
    266266by the ADS environment.
    267267</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="adsdnstech"></a>DNS and Active Directory</h3></div></div></div><p>
    268 <a class="indexterm" name="id368639"></a>
    269 <a class="indexterm" name="id368648"></a>
    270 <a class="indexterm" name="id368655"></a>
    271 <a class="indexterm" name="id368661"></a>
    272 <a class="indexterm" name="id368668"></a>
     268<a class="indexterm" name="id3"></a>
     269<a class="indexterm" name="id3"></a>
     270<a class="indexterm" name="id3"></a>
     271<a class="indexterm" name="id3"></a>
     272<a class="indexterm" name="id3"></a>
    273273Occasionally we hear from UNIX network administrators who want to use a UNIX-based DDNS server in place
    274274of the Microsoft DNS server. While this might be desirable to some, the MS Windows 200x DNS server is
    … …  
    278278Active Directory requires:
    279279</p><p>
    280 <a class="indexterm" name="id368685"></a>
    281 <a class="indexterm" name="id368692"></a>
    282 <a class="indexterm" name="id368698"></a>
     280<a class="indexterm" name="id3"></a>
     281<a class="indexterm" name="id3"></a>
     282<a class="indexterm" name="id3"></a>
    283283The use of DDNS is highly recommended with Active Directory, in which case the use of BIND9 is preferred for
    284284its ability to adequately support the SRV (service) records that are needed for Active Directory. Of course,
    … …  
    371371;; MSG SIZE  rcvd: 171
    372372</pre><p>
    373         </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id368969"></a>How Browsing Functions</h2></div></div></div><p>
    374 <a class="indexterm" name="id368977"></a>
    375 <a class="indexterm" name="id368984"></a>
    376 <a class="indexterm" name="id368991"></a>
    377 <a class="indexterm" name="id368997"></a>
    378 <a class="indexterm" name="id369004"></a>
     373        </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3"></a>How Browsing Functions</h2></div></div></div><p>
     374<a class="indexterm" name="id3"></a>
     375<a class="indexterm" name="id3"></a>
     376<a class="indexterm" name="id3"></a>
     377<a class="indexterm" name="id3"></a>
     378<a class="indexterm" name="id3"></a>
    379379MS Windows machines register their NetBIOS names (i.e., the machine name for each service type in operation)
    380380on startup.  The exact method by which this name registration takes place is determined by whether or not the
    … …  
    382382whether or not DNS for NetBIOS name resolution is enabled, and so on.
    383383</p><p>
    384 <a class="indexterm" name="id369018"></a>
    385 <a class="indexterm" name="id369024"></a>
    386 <a class="indexterm" name="id369031"></a>
     384<a class="indexterm" name="id3"></a>
     385<a class="indexterm" name="id3"></a>
     386<a class="indexterm" name="id3"></a>
    387387In the case where there is no WINS server, all name registrations as well as name lookups are done by UDP
    388388broadcast. This isolates name resolution to the local subnet, unless LMHOSTS is used to list all names and IP
    … …  
    391391parameter).
    392392</p><p>
    393 <a class="indexterm" name="id369055"></a>
    394 <a class="indexterm" name="id369062"></a>
    395 <a class="indexterm" name="id369068"></a>
     393<a class="indexterm" name="id3"></a>
     394<a class="indexterm" name="id3"></a>
     395<a class="indexterm" name="id3"></a>
    396396Where a WINS server is used, the MS Windows client will use UDP unicast to register with the WINS server. Such
    397397packets can be routed, and thus WINS allows name resolution to function across routed networks.
    398398</p><p>
    399 <a class="indexterm" name="id369080"></a>
    400 <a class="indexterm" name="id369087"></a>
    401 <a class="indexterm" name="id369096"></a>
    402 <a class="indexterm" name="id369103"></a>
    403 <a class="indexterm" name="id369109"></a>
    404 <a class="indexterm" name="id369116"></a>
    405 <a class="indexterm" name="id369123"></a>
    406 <a class="indexterm" name="id369130"></a>
     399<a class="indexterm" name="id3"></a>
     400<a class="indexterm" name="id3"></a>
     401<a class="indexterm" name="id3"></a>
     402<a class="indexterm" name="id3"></a>
     403<a class="indexterm" name="id3"></a>
     404<a class="indexterm" name="id3"></a>
     405<a class="indexterm" name="id3"></a>
     406<a class="indexterm" name="id3"></a>
    407407During the startup process, an election takes place to create a local master browser (LMB) if one does not
    408408already exist. On each NetBIOS network one machine will be elected to function as the domain master browser
    … …  
    414414criteria, will win the election as DMB.
    415415</p><p>
    416 <a class="indexterm" name="id369146"></a>
    417 <a class="indexterm" name="id369153"></a>
    418 <a class="indexterm" name="id369160"></a>
    419 <a class="indexterm" name="id369166"></a>
    420 <a class="indexterm" name="id369173"></a>
    421 <a class="indexterm" name="id369180"></a>
    422 <a class="indexterm" name="id369187"></a>
    423 <a class="indexterm" name="id369194"></a>
     416<a class="indexterm" name="id3"></a>
     417<a class="indexterm" name="id3"></a>
     418<a class="indexterm" name="id3"></a>
     419<a class="indexterm" name="id3"></a>
     420<a class="indexterm" name="id3"></a>
     421<a class="indexterm" name="id3"></a>
     422<a class="indexterm" name="id3"></a>
     423<a class="indexterm" name="id3"></a>
    424424Where a WINS server is used, the DMB registers its IP address with the WINS server using the name of the
    425425domain and the NetBIOS name type 1B (e.g., DOMAIN&lt;1B&gt;). All LMBs register their IP addresses with the WINS
    … …  
    429429they are on. The DMB is responsible for synchronizing the browse lists it obtains from the LMBs.
    430430</p><p>
    431 <a class="indexterm" name="id369217"></a>
     431<a class="indexterm" name="id3"></a>
    432432Clients wishing to browse the network make use of this list but also depend on the availability of correct
    433433name resolution to the respective IP address or addresses.
    434434</p><p>
    435 <a class="indexterm" name="id369228"></a>
     435<a class="indexterm" name="id3"></a>
    436436Any configuration that breaks name resolution and/or browsing intrinsics will annoy users because they will
    437437have to put up with protracted inability to use the network services.
    438438</p><p>
    439 <a class="indexterm" name="id369240"></a>
    440 <a class="indexterm" name="id369246"></a>
    441 <a class="indexterm" name="id369253"></a>
    442 <a class="indexterm" name="id369260"></a>
    443 <a class="indexterm" name="id369267"></a>
    444 <a class="indexterm" name="id369273"></a>
     439<a class="indexterm" name="id3"></a>
     440<a class="indexterm" name="id3"></a>
     441<a class="indexterm" name="id3"></a>
     442<a class="indexterm" name="id3"></a>
     443<a class="indexterm" name="id3"></a>
     444<a class="indexterm" name="id3"></a>
    445445Samba supports a feature that allows forced synchronization of browse lists across routed networks using the
    446446<a class="link" href="smb.conf.5.html#REMOTEBROWSESYNC">remote browse sync</a> parameter in the <code class="filename">smb.conf</code> file. This causes Samba to contact the
    … …  
    452452be provided. This mechanism could be via DNS, <code class="filename">/etc/hosts</code>, and so on.
    453453</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="DMB"></a>Configuring Workgroup Browsing</h3></div></div></div><p>
    454 <a class="indexterm" name="id369333"></a>
    455 <a class="indexterm" name="id369340"></a>
    456 <a class="indexterm" name="id369346"></a>
    457 <a class="indexterm" name="id369353"></a>
    458 <a class="indexterm" name="id369359"></a>
    459 <a class="indexterm" name="id369366"></a>
     454<a class="indexterm" name="id3"></a>
     455<a class="indexterm" name="id3"></a>
     456<a class="indexterm" name="id3"></a>
     457<a class="indexterm" name="id3"></a>
     458<a class="indexterm" name="id3"></a>
     459<a class="indexterm" name="id3"></a>
    460460To configure cross-subnet browsing on a network containing machines in a workgroup, not an NT domain, you need
    461461to set up one Samba server to be the DMB (note that this is not the same as a Primary Domain Controller,
    … …  
    465465presence of a DMB that makes cross-subnet browsing possible for a workgroup.
    466466</p><p>
    467 <a class="indexterm" name="id369387"></a>
     467<a class="indexterm" name="id3"></a>
    468468In a workgroup environment the DMB must be a Samba server, and there must only be one DMB per workgroup name.
    469469To set up a Samba server as a DMB, set the following option in the <em class="parameter"><code>[global]</code></em> section
    470470of the <code class="filename">smb.conf</code> file:
    471471</p><p>
    472 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id369415"></a><em class="parameter"><code>domain master = yes</code></em></td></tr></table><p>
    473 </p><p>
    474 <a class="indexterm" name="id369430"></a>
    475 <a class="indexterm" name="id369437"></a>
     472</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id3"></a><em class="parameter"><code>domain master = yes</code></em></td></tr></table><p>
     473</p><p>
     474<a class="indexterm" name="id3"></a>
     475<a class="indexterm" name="id3"></a>
    476476The DMB should preferably be the LMB for its own subnet. In order to achieve this, set the following options
    477477in the <em class="parameter"><code>[global]</code></em> section of the <code class="filename">smb.conf</code> file as shown in <a class="link" href="NetworkBrowsing.html#dmbexample" title="Example 10.1. Domain Master Browser smb.conf">Domain Master Browser smb.conf</a>
    478 </p><div class="example"><a name="dmbexample"></a><p class="title"><b>Example 10.1. Domain Master Browser smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id369489"></a><em class="parameter"><code>domain master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id369501"></a><em class="parameter"><code>local master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id369512"></a><em class="parameter"><code>preferred master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id369524"></a><em class="parameter"><code>os level = 65</code></em></td></tr></table></div></div><br class="example-break"><p>
    479 <a class="indexterm" name="id369538"></a>
    480 <a class="indexterm" name="id369545"></a>
     478</p><div class="example"><a name="dmbexample"></a><p class="title"><b>Example 10.1. Domain Master Browser smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id3"></a><em class="parameter"><code>os level = 65</code></em></td></tr></table></div></div><br class="example-break"><p>
     479<a class="indexterm" name="id3"></a>
     480<a class="indexterm" name="id3"></a>
    481481The DMB may be the same machine as the WINS server, if necessary.
    482482</p><p>
    483 <a class="indexterm" name="id369555"></a>
    484 <a class="indexterm" name="id369562"></a>
    485 <a class="indexterm" name="id369569"></a>
     483<a class="indexterm" name="id3"></a>
     484<a class="indexterm" name="id3"></a>
     485<a class="indexterm" name="id3"></a>
    486486Next, you should ensure that each of the subnets contains a machine that can act as an LMB for the workgroup.
    487487Any MS Windows NT/200x/XP machine should be able to do this, as will Windows 9x/Me machines (although these
    … …  
    489489set the following options in the <em class="parameter"><code>[global]</code></em> section of the <code class="filename">smb.conf</code> file as shown in
    490490<a class="link" href="NetworkBrowsing.html#lmbexample" title="Example 10.2. Local master browser smb.conf">Local master browser smb.conf</a>
    491 </p><div class="example"><a name="lmbexample"></a><p class="title"><b>Example 10.2. Local master browser smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id369624"></a><em class="parameter"><code>domain master = no</code></em></td></tr><tr><td><a class="indexterm" name="id369635"></a><em class="parameter"><code>local master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id369647"></a><em class="parameter"><code>preferred master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id369658"></a><em class="parameter"><code>os level = 65</code></em></td></tr></table></div></div><br class="example-break"><p>
    492 <a class="indexterm" name="id369673"></a>
     491</p><div class="example"><a name="lmbexample"></a><p class="title"><b>Example 10.2. Local master browser smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id3"></a><em class="parameter"><code>os level = 65</code></em></td></tr></table></div></div><br class="example-break"><p>
     492<a class="indexterm" name="id3"></a>
    493493Do not do this for more than one Samba server on each subnet, or they will war with
    494494each other over which is to be the LMB.
    495495</p><p>
    496 <a class="indexterm" name="id369684"></a>
    497 <a class="indexterm" name="id369690"></a>
     496<a class="indexterm" name="id3"></a>
     497<a class="indexterm" name="id3"></a>
    498498The <a class="link" href="smb.conf.5.html#LOCALMASTER">local master</a> parameter allows Samba to act as a
    499499LMB. The <a class="link" href="smb.conf.5.html#PREFERREDMASTER">preferred master</a> causes <code class="literal">nmbd</code>
    … …  
    501501parameter sets Samba high enough so it should win any browser elections.
    502502</p><p>
    503 <a class="indexterm" name="id369739"></a>
     503<a class="indexterm" name="id3"></a>
    504504If you have an NT machine on the subnet that you wish to be the LMB, you can disable Samba from
    505505becoming an LMB by setting the following options in the <em class="parameter"><code>[global]</code></em> section of the
    506506<code class="filename">smb.conf</code> file as shown in <a class="link" href="NetworkBrowsing.html#nombexample" title="Example 10.3. smb.conf for Not Being a Master Browser">smb.conf for Not Being a Master Browser</a>.
    507507</p><p>
    508 </p><div class="example"><a name="nombexample"></a><p class="title"><b>Example 10.3. smb.conf for Not Being a Master Browser</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id369794"></a><em class="parameter"><code>domain master = no</code></em></td></tr><tr><td><a class="indexterm" name="id369805"></a><em class="parameter"><code>local master = no</code></em></td></tr><tr><td><a class="indexterm" name="id369816"></a><em class="parameter"><code>preferred master = no</code></em></td></tr><tr><td><a class="indexterm" name="id369828"></a><em class="parameter"><code>os level = 0</code></em></td></tr></table></div></div><p><br class="example-break">
    509 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id369843"></a>Domain Browsing Configuration</h3></div></div></div><p>
    510 <a class="indexterm" name="id369850"></a>
    511 <a class="indexterm" name="id369857"></a>
    512 <a class="indexterm" name="id369864"></a>
    513 <a class="indexterm" name="id369870"></a>
     508</p><div class="example"><a name="nombexample"></a><p class="title"><b>Example 10.3. smb.conf for Not Being a Master Browser</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id3"></a><em class="parameter"><code>os level = 0</code></em></td></tr></table></div></div><p><br class="example-break">
     509</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>Domain Browsing Configuration</h3></div></div></div><p>
     510<a class="indexterm" name="id3"></a>
     511<a class="indexterm" name="id3"></a>
     512<a class="indexterm" name="id3"></a>
     513<a class="indexterm" name="id3"></a>
    514514If you are adding Samba servers to a Windows NT domain, then you must not set up a Samba server as a DMB.  By
    515515default, a Windows NT PDC for a domain is also the DMB for that domain. Network browsing may break if a Samba
    … …  
    517517WINS.
    518518</p><p>
    519 <a class="indexterm" name="id369887"></a>
     519<a class="indexterm" name="id3"></a>
    520520For subnets other than the one containing the Windows NT PDC, you may set up Samba servers as LMBs as
    521521described. To make a Samba server a Local Master Browser, set the following options in the <em class="parameter"><code>[global]</code></em> section of the <code class="filename">smb.conf</code> file as shown in <a class="link" href="NetworkBrowsing.html#remsmb" title="Example 10.4. Local Master Browser smb.conf">Local Master Browser
    522522smb.conf</a>
    523 </p><div class="example"><a name="remsmb"></a><p class="title"><b>Example 10.4. Local Master Browser smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id369940"></a><em class="parameter"><code>domain master = no</code></em></td></tr><tr><td><a class="indexterm" name="id369952"></a><em class="parameter"><code>local master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id369963"></a><em class="parameter"><code>preferred master = yes</code></em></td></tr><tr><td><a class="indexterm" name="id369975"></a><em class="parameter"><code>os level = 65</code></em></td></tr></table></div></div><br class="example-break"><p>
    524 <a class="indexterm" name="id369989"></a>
    525 <a class="indexterm" name="id369996"></a>
     523</p><div class="example"><a name="remsmb"></a><p class="title"><b>Example 10.4. Local Master Browser smb.conf</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id3"></a><em class="parameter"><code>os level = 65</code></em></td></tr></table></div></div><br class="example-break"><p>
     524<a class="indexterm" name="id3"></a>
     525<a class="indexterm" name="id3"></a>
    526526If you wish to have a Samba server fight the election with machines on the same subnet, you may set the
    527527<a class="link" href="smb.conf.5.html#OSLEVEL">os level</a> parameter to lower levels.  By doing this you can tune the order of machines
    528528that will become LMBs if they are running. For more details on this, refer to <a class="link" href="NetworkBrowsing.html#browse-force-master" title="Forcing Samba to Be the Master">Forcing Samba to Be the Master</a>.
    529529</p><p>
    530 <a class="indexterm" name="id370027"></a>
    531 <a class="indexterm" name="id370033"></a>
    532 <a class="indexterm" name="id370040"></a>
     530<a class="indexterm" name="id3"></a>
     531<a class="indexterm" name="id3"></a>
     532<a class="indexterm" name="id3"></a>
    533533If you have Windows NT machines that are members of the domain on all subnets and you are sure they will
    534534always be running, you can disable Samba from taking part in browser elections and ever becoming an LMB by
    … …  
    538538</p><div class="example"><a name="xremmb"></a><p class="title"><b>Example 10.5. <code class="filename">smb.conf</code> for Not Being a master browser</b></p><div class="example-contents"><em class="parameter"><code>[global]</code></em><a class="link" href="smb.conf.5.html#DOMAINMASTER">domain master = no</a><a class="link" href="smb.conf.5.html#LOCALMASTER">local master = no</a><a class="link" href="smb.conf.5.html#PREFERREDMASTER">preferred master = no</a><a class="link" href="smb.conf.5.html#OSLEVEL">os level = 0</a></div></div><p><br class="example-break">
    539539</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="browse-force-master"></a>Forcing Samba to Be the Master</h3></div></div></div><p>
    540 <a class="indexterm" name="id370152"></a>
    541 <a class="indexterm" name="id370158"></a>
    542 <a class="indexterm" name="id370165"></a>
    543 <a class="indexterm" name="id370172"></a>
    544 <a class="indexterm" name="id370178"></a>
    545 <a class="indexterm" name="id370185"></a>
    546 <a class="indexterm" name="id370192"></a>
     540<a class="indexterm" name="id3"></a>
     541<a class="indexterm" name="id3"></a>
     542<a class="indexterm" name="id3"></a>
     543<a class="indexterm" name="id3"></a>
     544<a class="indexterm" name="id3"></a>
     545<a class="indexterm" name="id3"></a>
     546<a class="indexterm" name="id3"></a>
    547547Who becomes the master browser is determined by an election process using broadcasts. Each election packet
    548548contains a number of parameters that determine what precedence (bias) a host should have in the election. By
    … …  
    558558level is 255.
    559559</p><p>
    560 <a class="indexterm" name="id370242"></a>
    561 <a class="indexterm" name="id370248"></a>
    562 <a class="indexterm" name="id370255"></a>
    563 <a class="indexterm" name="id370262"></a>
     560<a class="indexterm" name="id3"></a>
     561<a class="indexterm" name="id3"></a>
     562<a class="indexterm" name="id3"></a>
     563<a class="indexterm" name="id3"></a>
    564564If you want Samba to force an election on startup, set the <a class="link" href="smb.conf.5.html#PREFERREDMASTER">preferred master</a> global
    565565option in <code class="filename">smb.conf</code> to <code class="constant">yes</code>.  Samba will then have a slight advantage over other
    … …  
    569569they will force an election in order to become the LMB.
    570570</p><p>
    571 <a class="indexterm" name="id370309"></a>
    572 <a class="indexterm" name="id370316"></a>
    573 <a class="indexterm" name="id370322"></a>
    574 <a class="indexterm" name="id370329"></a>
    575 <a class="indexterm" name="id370336"></a>
     571<a class="indexterm" name="id3"></a>
     572<a class="indexterm" name="id3"></a>
     573<a class="indexterm" name="id3"></a>
     574<a class="indexterm" name="id3"></a>
     575<a class="indexterm" name="id3"></a>
    576576If you want Samba to be a <span class="emphasis"><em>DMB</em></span>, then it is recommended that you also set <a class="link" href="smb.conf.5.html#PREFERREDMASTER">preferred master</a> to <code class="constant">yes</code>, because Samba will not become a DMB for the whole of
    577577your LAN or WAN if it is not also a LMB on its own broadcast isolated subnet.
    578578</p><p>
    579 <a class="indexterm" name="id370365"></a>
    580 <a class="indexterm" name="id370371"></a>
    581 <a class="indexterm" name="id370378"></a>
    582 <a class="indexterm" name="id370385"></a>
    583 <a class="indexterm" name="id370391"></a>
     579<a class="indexterm" name="id3"></a>
     580<a class="indexterm" name="id3"></a>
     581<a class="indexterm" name="id3"></a>
     582<a class="indexterm" name="id3"></a>
     583<a class="indexterm" name="id3"></a>
    584584It is possible to configure two Samba servers to attempt to become the DMB for a domain. The first server that
    585585comes up will be the DMB. All other Samba servers will attempt to become the DMB every 5 minutes. They will
    … …  
    587587current DMB fail. The network bandwidth overhead of browser elections is relatively small, requiring
    588588approximately four UDP packets per machine per election. The maximum size of a UDP packet is 576 bytes.
    589 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id370405"></a>Making Samba the Domain Master</h3></div></div></div><p>
    590 <a class="indexterm" name="id370413"></a>
    591 <a class="indexterm" name="id370419"></a>
    592 <a class="indexterm" name="id370426"></a>
    593 <a class="indexterm" name="id370433"></a>
     589</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>Making Samba the Domain Master</h3></div></div></div><p>
     590<a class="indexterm" name="id3"></a>
     591<a class="indexterm" name="id3"></a>
     592<a class="indexterm" name="id3"></a>
     593<a class="indexterm" name="id3"></a>
    594594The domain master browser is responsible for collating the browse lists of multiple subnets so browsing can
    595595occur between subnets. You can make Samba act as the domain master browser by setting <a class="link" href="smb.conf.5.html#DOMAINMASTER">domain master = yes</a> in <code class="filename">smb.conf</code>. By default it will not be a domain master browser.
    596596</p><p>
    597 <a class="indexterm" name="id370462"></a>
    598 <a class="indexterm" name="id370468"></a>
     597<a class="indexterm" name="id3"></a>
     598<a class="indexterm" name="id3"></a>
    599599Do not set Samba to be the domain master for a workgroup that has the same name as an NT/200x domain.  If
    600600Samba is configured to be the domain master for a workgroup that is present on the same network as a Windows
    … …  
    604604every 12 minutes) from LMBs on other subnets and then contact them to synchronize browse lists.
    605605</p><p>
    606 <a class="indexterm" name="id370486"></a>
    607 <a class="indexterm" name="id370493"></a>
     606<a class="indexterm" name="id3"></a>
     607<a class="indexterm" name="id3"></a>
    608608If you want Samba to be the domain master, you should also set the <a class="link" href="smb.conf.5.html#OSLEVEL">os level</a> high
    609609enough to make sure it wins elections, and set <a class="link" href="smb.conf.5.html#PREFERREDMASTER">preferred master</a> to
    610610<code class="constant">yes</code>, to get Samba to force an election on startup.
    611611</p><p>
    612 <a class="indexterm" name="id370529"></a>
    613 <a class="indexterm" name="id370536"></a>
     612<a class="indexterm" name="id3"></a>
     613<a class="indexterm" name="id3"></a>
    614614All servers (including Samba) and clients should be using a WINS server to resolve NetBIOS names. If your
    615615clients are only using broadcasting to resolve NetBIOS names, then two things will occur:
    616616</p><div class="orderedlist"><ol type="1"><li><p>
    617 <a class="indexterm" name="id370556"></a>
    618 <a class="indexterm" name="id370563"></a>
     617<a class="indexterm" name="id3"></a>
     618<a class="indexterm" name="id3"></a>
    619619        LMBs will be unable to find a DMB because they will be looking only on the local subnet.
    620620        </p></li><li><p>
    621 <a class="indexterm" name="id370576"></a>
     621<a class="indexterm" name="id3"></a>
    622622        If a client happens to get hold of a domain-wide browse list and a user attempts to access a
    623623        host in that list, it will be unable to resolve the NetBIOS name of that host.
    624624        </p></li></ol></div><p>
    625 <a class="indexterm" name="id370590"></a>
     625<a class="indexterm" name="id3"></a>
    626626If, however, both Samba and your clients are using a WINS server, then:
    627627</p><div class="orderedlist"><ol type="1"><li><p>
    … …  
    632632        contact the WINS server to resolve the NetBIOS name of that host. As long as that host has registered its
    633633        NetBIOS name with the same WINS server, the user will be able to see that host..
    634         </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id370625"></a>Note about Broadcast Addresses</h3></div></div></div><p>
    635 <a class="indexterm" name="id370632"></a>
     634        </p></li></ol></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>Note about Broadcast Addresses</h3></div></div></div><p>
     635<a class="indexterm" name="id3"></a>
    636636If your network uses a zero-based broadcast address (for example, if it ends in a 0), then you will strike
    637637problems. Windows for Workgroups does not seem to support a zeros broadcast, and you will probably find that
    638638browsing and name lookups will not work.
    639 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id370644"></a>Multiple Interfaces</h3></div></div></div><p>
    640 <a class="indexterm" name="id370651"></a>
     639</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>Multiple Interfaces</h3></div></div></div><p>
     640<a class="indexterm" name="id3"></a>
    641641Samba supports machines with multiple network interfaces. If you have multiple interfaces, you will
    642642need to use the <a class="link" href="smb.conf.5.html#INTERFACES">interfaces</a> option in <code class="filename">smb.conf</code> to configure them. For example, the
    … …  
    645645<code class="literal">eth4</code> should be used by Samba. In this case, the following <code class="filename">smb.conf</code> file entries would
    646646permit that intent:
    647 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id370725"></a><em class="parameter"><code>interfaces = eth1, eth4</code></em></td></tr><tr><td><a class="indexterm" name="id370736"></a><em class="parameter"><code>bind interfaces only = Yes</code></em></td></tr></table><p>
    648 <a class="indexterm" name="id370748"></a>
    649 <a class="indexterm" name="id370755"></a>
    650 <a class="indexterm" name="id370762"></a>
    651 <a class="indexterm" name="id370768"></a>
    652 <a class="indexterm" name="id370775"></a>
    653 <a class="indexterm" name="id370782"></a>
    654 <a class="indexterm" name="id370788"></a>
     647</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id3"></a><em class="parameter"><code>bind interfaces only = Yes</code></em></td></tr></table><p>
     648<a class="indexterm" name="id3"></a>
     649<a class="indexterm" name="id3"></a>
     650<a class="indexterm" name="id3"></a>
     651<a class="indexterm" name="id3"></a>
     652<a class="indexterm" name="id3"></a>
     653<a class="indexterm" name="id3"></a>
     654<a class="indexterm" name="id3"></a>
    655655The <a class="link" href="smb.conf.5.html#BINDINTERFACESONLY">bind interfaces only = Yes</a> is necessary to exclude TCP/IP session
    656656services (ports 135, 139, and 445) over the interfaces that are not specified. Please be aware that
    … …  
    659659ethernet interface requires the use of a firewall to block ports 137 and 138 (UDP), and ports 135, 139, and
    660660445 (TCP) on all network interfaces that must not be able to access the Samba server.
    661 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id370820"></a>Use of the Remote Announce Parameter</h3></div></div></div><p>
     661</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>Use of the Remote Announce Parameter</h3></div></div></div><p>
    662662The <a class="link" href="smb.conf.5.html#REMOTEANNOUNCE">remote announce</a> parameter of <code class="filename">smb.conf</code> can be used to forcibly ensure that all
    663663the NetBIOS names on a network get announced to a remote network.  The syntax of the <a class="link" href="smb.conf.5.html#REMOTEANNOUNCE">remote announce</a> parameter is:
    664 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id370861"></a><em class="parameter"><code>remote announce = 192.168.12.23 [172.16.21.255] ...</code></em></td></tr></table><p>
     664</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id3"></a><em class="parameter"><code>remote announce = 192.168.12.23 [172.16.21.255] ...</code></em></td></tr></table><p>
    665665<span class="emphasis"><em>or</em></span>
    666 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id370882"></a><em class="parameter"><code>remote announce = 192.168.12.23/MIDEARTH [172.16.21.255/ELVINDORF] ...</code></em></td></tr></table><p>
     666</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id3"></a><em class="parameter"><code>remote announce = 192.168.12.23/MIDEARTH [172.16.21.255/ELVINDORF] ...</code></em></td></tr></table><p>
    667667
    668668where:
    669669</p><div class="variablelist"><dl><dt><span class="term"><em class="replaceable"><code>192.168.12.23</code></em> and <em class="replaceable"><code>172.16.21.255</code></em></span></dt><dd><p>
    670 <a class="indexterm" name="id370908"></a>
    671 <a class="indexterm" name="id370917"></a>
     670<a class="indexterm" name="id3"></a>
     671<a class="indexterm" name="id3"></a>
    672672                is either the LMB IP address or the broadcast address of the remote network.
    673673                That is, the LMB is at 192.168.1.23, or the address could be given as 172.16.21.255 where the netmask
    … …  
    679679                they belong to that workgroup. This may cause name resolution problems and should be avoided.
    680680                </p></dd></dl></div><p>
    681 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id370948"></a>Use of the Remote Browse Sync Parameter</h3></div></div></div><p>
    682 <a class="indexterm" name="id370956"></a>
    683 <a class="indexterm" name="id370963"></a>
     681</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>Use of the Remote Browse Sync Parameter</h3></div></div></div><p>
     682<a class="indexterm" name="id3"></a>
     683<a class="indexterm" name="id3"></a>
    684684The <a class="link" href="smb.conf.5.html#REMOTEBROWSESYNC">remote browse sync</a> parameter of <code class="filename">smb.conf</code> is used to announce to another LMB that
    685685it must synchronize its NetBIOS name list with our Samba LMB. This works only if the Samba server that has
    … …  
    688688The syntax of the <a class="link" href="smb.conf.5.html#REMOTEBROWSESYNC">remote browse sync</a> parameter is:
    689689
    690 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id371007"></a></td></tr></table><p>
    691 <a class="indexterm" name="id371014"></a>
    692 <a class="indexterm" name="id371021"></a>
     690</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id3"></a></td></tr></table><p>
     691<a class="indexterm" name="id3"></a>
     692<a class="indexterm" name="id3"></a>
    693693where <em class="replaceable"><code>192.168.10.40</code></em> is either the IP address of the
    694694remote LMB or the network broadcast address of the remote segment.
    695 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id371035"></a>WINS: The Windows Internetworking Name Server</h2></div></div></div><p>
    696 <a class="indexterm" name="id371043"></a>
    697 <a class="indexterm" name="id371050"></a>
    698 <a class="indexterm" name="id371057"></a>
     695</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3"></a>WINS: The Windows Internetworking Name Server</h2></div></div></div><p>
     696<a class="indexterm" name="id3"></a>
     697<a class="indexterm" name="id3"></a>
     698<a class="indexterm" name="id3"></a>
    699699Use of WINS (either Samba WINS or MS Windows NT Server WINS) is highly
    700700recommended. Every NetBIOS machine registers its name together with a
    … …  
    705705by registering the server (the type 0x20) name.
    706706</p><p>
    707 <a class="indexterm" name="id371071"></a>
    708 <a class="indexterm" name="id371078"></a>
     707<a class="indexterm" name="id3"></a>
     708<a class="indexterm" name="id3"></a>
    709709All NetBIOS names are up to 15 characters in length. The name_type variable
    710710is added to the end of the name, thus creating a 16 character name. Any
    … …  
    713713name_type information).
    714714</p><p>
    715 <a class="indexterm" name="id371090"></a>
    716 <a class="indexterm" name="id371097"></a>
    717 <a class="indexterm" name="id371104"></a>
    718 <a class="indexterm" name="id371111"></a>
     715<a class="indexterm" name="id3"></a>
     716<a class="indexterm" name="id3"></a>
     717<a class="indexterm" name="id3"></a>
     718<a class="indexterm" name="id3"></a>
    719719WINS can store these 16-character names as they get registered. A client
    720720that wants to log onto the network can ask the WINS server for a list
    … …  
    726726absence of WINS.
    727727</p><p>
    728 <a class="indexterm" name="id371131"></a>
    729 <a class="indexterm" name="id371138"></a>
    730 <a class="indexterm" name="id371144"></a>
    731 <a class="indexterm" name="id371151"></a>
    732 <a class="indexterm" name="id371158"></a>
     728<a class="indexterm" name="id3"></a>
     729<a class="indexterm" name="id3"></a>
     730<a class="indexterm" name="id3"></a>
     731<a class="indexterm" name="id3"></a>
     732<a class="indexterm" name="id3"></a>
    733733WINS also forces browse list synchronization by all LMBs. LMBs must synchronize their browse list with the
    734734DMB, and WINS helps the LMB to identify its DMB. By definition this will work only within a single workgroup.
    … …  
    737737only.
    738738</p><p>
    739 <a class="indexterm" name="id371172"></a>
    740 <a class="indexterm" name="id371178"></a>
    741 <a class="indexterm" name="id371185"></a>
    742 <a class="indexterm" name="id371192"></a>
     739<a class="indexterm" name="id3"></a>
     740<a class="indexterm" name="id3"></a>
     741<a class="indexterm" name="id3"></a>
     742<a class="indexterm" name="id3"></a>
    743743WINS will work correctly only if every client TCP/IP protocol stack
    744744is configured to use the WINS servers. Any client that is not
    … …  
    757757Never use <a class="link" href="smb.conf.5.html#WINSSUPPORT">wins support = yes</a> together with <a class="link" href="smb.conf.5.html#WINSSERVER">wins server = 10.0.0.18</a> particularly not using its own IP address. Specifying both will cause <span class="application">nmbd</span>
    758758to refuse to start!
    759 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id371282"></a>WINS Server Configuration</h3></div></div></div><p>
    760 <a class="indexterm" name="id371290"></a>
     759</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>WINS Server Configuration</h3></div></div></div><p>
     760<a class="indexterm" name="id3"></a>
    761761Either a Samba server or a Windows NT server machine may be set up
    762762as a WINS server. To configure a Samba server to be a WINS server, you must
    … …  
    764764the <em class="parameter"><code>[global]</code></em> section:
    765765</p><p>
    766 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id371320"></a><em class="parameter"><code>wins support = yes</code></em></td></tr></table><p>
    767 </p><p>
    768 <a class="indexterm" name="id371334"></a>
     766</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id3"></a><em class="parameter"><code>wins support = yes</code></em></td></tr></table><p>
     767</p><p>
     768<a class="indexterm" name="id3"></a>
    769769Versions of Samba prior to 1.9.17 had this parameter default to
    770770yes. If you have any older versions of Samba on your network, it is
    … …  
    775775all NetBIOS names registered with them, acting as a DNS for NetBIOS names.
    776776</p><p>
    777 <a class="indexterm" name="id371365"></a>
     777<a class="indexterm" name="id3"></a>
    778778It is strongly recommended to set up only one WINS server. Do not set the <a class="link" href="smb.conf.5.html#WINSSUPPORT">wins support = yes</a> option on more than one Samba server on a network.
    779779</p><p>
    780 <a class="indexterm" name="id371386"></a>
    781 <a class="indexterm" name="id371395"></a>
    782 <a class="indexterm" name="id371402"></a>
    783 <a class="indexterm" name="id371409"></a>
    784 <a class="indexterm" name="id371416"></a>
     780<a class="indexterm" name="id3"></a>
     781<a class="indexterm" name="id3"></a>
     782<a class="indexterm" name="id3"></a>
     783<a class="indexterm" name="id3"></a>
     784<a class="indexterm" name="id3"></a>
    785785To configure Windows NT/200x Server as a WINS server, install and configure the WINS service. See the Windows
    786786NT/200x documentation for details.  Windows NT/200x WINS servers can replicate to each other, allowing more
    … …  
    790790as a WINS server.  Currently only one Samba server should have the <a class="link" href="smb.conf.5.html#WINSSUPPORT">wins support = yes</a> parameter set.
    791791</p><p>
    792 <a class="indexterm" name="id371442"></a>
    793 <a class="indexterm" name="id371448"></a>
     792<a class="indexterm" name="id3"></a>
     793<a class="indexterm" name="id3"></a>
    794794After the WINS server has been configured, you must ensure that all machines participating on the network are
    795795configured with the address of this WINS server. If your WINS server is a Samba machine, fill in the Samba
    … …  
    797797Panel-&gt;Network-&gt;Protocols-&gt;TCP-&gt;WINS Server</span> dialogs in Windows 9x/Me or Windows NT/200x. To tell a
    798798Samba server the IP address of the WINS server, add the following line to the <em class="parameter"><code>[global]</code></em> section of all <code class="filename">smb.conf</code> files:
    799 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id371488"></a><em class="parameter"><code>wins server = &lt;name or IP address&gt;</code></em></td></tr></table><p>
     799</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id3"></a><em class="parameter"><code>wins server = &lt;name or IP address&gt;</code></em></td></tr></table><p>
    800800where &lt;name or IP address&gt; is either the DNS name of the WINS server
    801801machine or its IP address.
    … …  
    807807<code class="literal">nmbd</code> will fail to start.
    808808</p><p>
    809 <a class="indexterm" name="id371543"></a>
    810 <a class="indexterm" name="id371550"></a>
    811 <a class="indexterm" name="id371557"></a>
    812 <a class="indexterm" name="id371564"></a>
     809<a class="indexterm" name="id3"></a>
     810<a class="indexterm" name="id3"></a>
     811<a class="indexterm" name="id3"></a>
     812<a class="indexterm" name="id3"></a>
    813813There are two possible scenarios for setting up cross-subnet browsing.
    814814The first details setting up cross-subnet browsing on a network containing
    … …  
    816816part of a Windows NT domain. The second details setting up cross-subnet
    817817browsing on networks that contain NT domains.
    818 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id371576"></a>WINS Replication</h3></div></div></div><p>
    819 <a class="indexterm" name="id371583"></a>
    820 <a class="indexterm" name="id371593"></a>
     818</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>WINS Replication</h3></div></div></div><p>
     819<a class="indexterm" name="id3"></a>
     820<a class="indexterm" name="id3"></a>
    821821Samba-3 does not support native WINS replication. There was an approach to implement it, called
    822822<code class="filename">wrepld</code>, but it was never ready for action and the development is now discontinued.
    … …  
    826826<code class="filename">samba4WINS</code> are available at http://ftp.sernet.de/pub/samba4WINS.
    827827
    828 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id371626"></a>Static WINS Entries</h3></div></div></div><p>
    829 <a class="indexterm" name="id371634"></a>
    830 <a class="indexterm" name="id371640"></a>
    831 <a class="indexterm" name="id371647"></a>
    832 <a class="indexterm" name="id371654"></a>
     828</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>Static WINS Entries</h3></div></div></div><p>
     829<a class="indexterm" name="id3"></a>
     830<a class="indexterm" name="id3"></a>
     831<a class="indexterm" name="id3"></a>
     832<a class="indexterm" name="id3"></a>
    833833Adding static entries to your Samba WINS server is actually fairly easy.  All you have to do is add a line to
    834834<code class="filename">wins.dat</code>, typically located in <code class="filename">/usr/local/samba/var/locks</code> or <code class="filename">/var/run/samba</code>.
    … …  
    838838"NAME#TYPE" TTL ADDRESS+ FLAGS
    839839</pre><p>
    840 <a class="indexterm" name="id371698"></a>
    841 <a class="indexterm" name="id371704"></a>
     840<a class="indexterm" name="id3"></a>
     841<a class="indexterm" name="id3"></a>
    842842where NAME is the NetBIOS name, TYPE is the NetBIOS type, TTL is the time-to-live as an absolute time in
    843843seconds, ADDRESS+ is one or more addresses corresponding to the registration, and FLAGS are the NetBIOS flags
    … …  
    857857</pre><p>
    858858</p><p>
    859 <a class="indexterm" name="id371770"></a>
    860 <a class="indexterm" name="id371777"></a>
    861 <a class="indexterm" name="id371784"></a>
    862 <a class="indexterm" name="id371791"></a>
    863 <a class="indexterm" name="id371798"></a>
    864 <a class="indexterm" name="id371804"></a>
    865 <a class="indexterm" name="id371811"></a>
     859<a class="indexterm" name="id3"></a>
     860<a class="indexterm" name="id3"></a>
     861<a class="indexterm" name="id3"></a>
     862<a class="indexterm" name="id3"></a>
     863<a class="indexterm" name="id3"></a>
     864<a class="indexterm" name="id3"></a>
     865<a class="indexterm" name="id3"></a>
    866866The NetBIOS flags may be interpreted as additive hexadecimal values: 00 - Broadcast node registration, 20 -
    867867Peer node registration, 40 - Meta node registration, 60 - Hybrid node registration, 02 - Permanent name, 04 -
    … …  
    870870file from the Samba source code repository. These are the values for the NB flags.
    871871</p><p>
    872 <a class="indexterm" name="id371831"></a>
     872<a class="indexterm" name="id3"></a>
    873873Though this method works with early Samba-3 versions, there is a possibility that it may change in future
    874874versions if WINS replication is added.
    875 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id371843"></a>Helpful Hints</h2></div></div></div><p>
     875</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3"></a>Helpful Hints</h2></div></div></div><p>
    876876The following hints should be carefully considered because they are stumbling points
    877877for many new network administrators.
    878 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id371853"></a>Windows Networking Protocols</h3></div></div></div><p>
    879 <a class="indexterm" name="id371861"></a>
    880 <a class="indexterm" name="id371867"></a>
     878</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>Windows Networking Protocols</h3></div></div></div><p>
     879<a class="indexterm" name="id3"></a>
     880<a class="indexterm" name="id3"></a>
    881881A common cause of browsing problems results from the installation of more than one protocol on an MS Windows
    882882machine.
    … …  
    884884Do not use more than one protocol on MS Windows clients.
    885885</p></div><p>
    886 <a class="indexterm" name="id371883"></a>
    887 <a class="indexterm" name="id371890"></a>
     886<a class="indexterm" name="id3"></a>
     887<a class="indexterm" name="id3"></a>
    888888Every NetBIOS machine takes part in a process of electing the LMB (and DMB)
    889889every 15 minutes. A set of election criteria is used to determine the order
    … …  
    892892win and thus retain its role.
    893893</p><p>
    894 <a class="indexterm" name="id371903"></a>
    895 <a class="indexterm" name="id371910"></a>
    896 <a class="indexterm" name="id371916"></a>
    897 <a class="indexterm" name="id371923"></a>
    898 <a class="indexterm" name="id371929"></a>
    899 <a class="indexterm" name="id371936"></a>
     894<a class="indexterm" name="id3"></a>
     895<a class="indexterm" name="id3"></a>
     896<a class="indexterm" name="id3"></a>
     897<a class="indexterm" name="id3"></a>
     898<a class="indexterm" name="id3"></a>
     899<a class="indexterm" name="id3"></a>
    900900The election process is <span class="emphasis"><em>fought out, so to speak</em></span> over every NetBIOS network interface. In
    901901the case of a Windows 9x/Me machine that has both TCP/IP and IPX installed and has NetBIOS enabled over both
    … …  
    905905cease to function as an LMB, and browse list operation on all TCP/IP-only machines will therefore fail.
    906906</p><p>
    907 <a class="indexterm" name="id371960"></a>
    908 <a class="indexterm" name="id371967"></a>
     907<a class="indexterm" name="id3"></a>
     908<a class="indexterm" name="id3"></a>
    909909Windows 95, 98, 98se, and Me are referred to generically as Windows 9x/Me.  The Windows NT4, 200x, and XP use
    910910common protocols. These are roughly referred to as the Windows NT family, but it should be recognized that
    … …  
    914914</p><p>
    915915The safest rule of all to follow is: Use only one protocol!
    916 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id371983"></a>Name Resolution Order</h3></div></div></div><p>
    917 <a class="indexterm" name="id371991"></a>
    918 <a class="indexterm" name="id371998"></a>
     916</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>Name Resolution Order</h3></div></div></div><p>
     917<a class="indexterm" name="id3"></a>
     918<a class="indexterm" name="id3"></a>
    919919Resolution of NetBIOS names to IP addresses can take place using a number
    920920of methods. The only ones that can provide NetBIOS name_type information
    … …  
    923923Alternative means of name resolution include:
    924924</p><div class="itemizedlist"><ul type="disc"><li><p>Static <code class="filename">/etc/hosts</code>   hard to maintain and lacks name_type info.</p></li><li><p>DNS  is a good choice but lacks essential NetBIOS name_type information.</p></li></ul></div><p>
    925 <a class="indexterm" name="id372063"></a>
    926 <a class="indexterm" name="id372070"></a>
     925<a class="indexterm" name="id3"></a>
     926<a class="indexterm" name="id3"></a>
    927927Many sites want to restrict DNS lookups and avoid broadcast name
    928928resolution traffic. The <em class="parameter"><code>name resolve order</code></em> parameter is of great help here.
    929929The syntax of the <em class="parameter"><code>name resolve order</code></em> parameter is:
    930 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id372095"></a><em class="parameter"><code>name resolve order = wins lmhosts bcast host</code></em></td></tr></table><p>
     930</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id3"></a><em class="parameter"><code>name resolve order = wins lmhosts bcast host</code></em></td></tr></table><p>
    931931<span class="emphasis"><em>or</em></span>
    932 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id372115"></a><em class="parameter"><code>name resolve order = wins lmhosts   (eliminates bcast and host)</code></em></td></tr></table><p>
     932</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id3"></a><em class="parameter"><code>name resolve order = wins lmhosts   (eliminates bcast and host)</code></em></td></tr></table><p>
    933933The default is:
    934 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id372133"></a><em class="parameter"><code>name resolve order = host lmhost wins bcast</code></em></td></tr></table><p>
    935 <a class="indexterm" name="id372145"></a>
     934</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id3"></a><em class="parameter"><code>name resolve order = host lmhost wins bcast</code></em></td></tr></table><p>
     935<a class="indexterm" name="id3"></a>
    936936where &#8220;<span class="quote">host</span>&#8221; refers to the native methods used by the UNIX system to implement the
    937937gethostbyname() function call. This is normally controlled by <code class="filename">/etc/host.conf</code>,
    938938<code class="filename">/etc/nsswitch.conf</code> and <code class="filename">/etc/resolv.conf</code>.
    939 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id372177"></a>Technical Overview of Browsing</h2></div></div></div><p>
    940 <a class="indexterm" name="id372185"></a>
     939</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3"></a>Technical Overview of Browsing</h2></div></div></div><p>
     940<a class="indexterm" name="id3"></a>
    941941SMB networking provides a mechanism by which clients can access a list
    942942of machines in a network called <a class="link" href="smb.conf.5.html#BROWSELIST">browse list</a>. This list
    … …  
    948948document.
    949949</p><p>
    950 <a class="indexterm" name="id372212"></a>
    951 <a class="indexterm" name="id372219"></a>
    952 <a class="indexterm" name="id372226"></a>
     950<a class="indexterm" name="id32"></a>
     951<a class="indexterm" name="id3"></a>
     952<a class="indexterm" name="id3"></a>
    953953MS Windows 2000 and later versions, as with Samba-3 and later versions, can be
    954954configured to not use NetBIOS over TCP/IP. When configured this way,
    … …  
    957957from SMB machine names to IP addresses does not function correctly.
    958958</p><p>
    959 <a class="indexterm" name="id372239"></a>
    960 <a class="indexterm" name="id372246"></a>
     959<a class="indexterm" name="id3"></a>
     960<a class="indexterm" name="id3"></a>
    961961Where NetBIOS over TCP/IP is enabled, use of a WINS server is highly
    962962recommended to aid the resolution of NetBIOS (SMB) names to IP addresses.
    963963WINS allows remote segment clients to obtain NetBIOS name_type information
    964964that cannot be provided by any other means of name resolution.
    965 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id372256"></a>Browsing Support in Samba</h3></div></div></div><p>
    966 <a class="indexterm" name="id372264"></a>
    967 <a class="indexterm" name="id372271"></a>
    968 <a class="indexterm" name="id372277"></a>
    969 <a class="indexterm" name="id372284"></a>
     965</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>Browsing Support in Samba</h3></div></div></div><p>
     966<a class="indexterm" name="id3"></a>
     967<a class="indexterm" name="id3"></a>
     968<a class="indexterm" name="id3"></a>
     969<a class="indexterm" name="id3"></a>
    970970Samba facilitates browsing. The browsing is supported by <span class="application">nmbd</span>
    971971and is also controlled by options in the <code class="filename">smb.conf</code> file.
    … …  
    973973to support domain logons and scripts is now available.
    974974</p><p>
    975 <a class="indexterm" name="id372308"></a>
    976 <a class="indexterm" name="id372315"></a>
    977 <a class="indexterm" name="id372321"></a>
     975<a class="indexterm" name="id3"></a>
     976<a class="indexterm" name="id3"></a>
     977<a class="indexterm" name="id3"></a>
    978978Samba can also act as a DMB for a workgroup. This
    979979means that it will collate lists from LMBs into a
    … …  
    982982both Samba and your clients use a WINS server.
    983983</p><p>
    984 <a class="indexterm" name="id372334"></a>
     984<a class="indexterm" name="id3"></a>
    985985Do not set Samba to be the domain master for a workgroup that has the same
    986986name as an NT Domain. On each wide-area network, you must only ever have one
    … …  
    988988or any other type of domain master that is providing this service.
    989989</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    990 <a class="indexterm" name="id372347"></a>
    991 <a class="indexterm" name="id372354"></a>
     990<a class="indexterm" name="id3"></a>
     991<a class="indexterm" name="id3"></a>
    992992<code class="literal">nmbd</code> can be configured as a WINS server, but it is not
    993993necessary to specifically use Samba as your WINS server. MS Windows
    … …  
    998998recommended that you use one and only one Samba server as the WINS server.
    999999</p></div><p>
    1000 <a class="indexterm" name="id372373"></a>
     1000<a class="indexterm" name="id3"></a>
    10011001To get browsing to work, you need to run <code class="literal">nmbd</code> as usual, but must
    10021002use the <a class="link" href="smb.conf.5.html#WORKGROUP">workgroup</a> option in <code class="filename">smb.conf</code>
    10031003to control what workgroup Samba becomes a part of.
    10041004</p><p>
    1005 <a class="indexterm" name="id372407"></a>
     1005<a class="indexterm" name="id3"></a>
    10061006Samba also has a useful option for a Samba server to offer itself for browsing on another subnet. It is
    10071007recommended that this option is used only for &#8220;<span class="quote">unusual</span>&#8221; purposes: announcements over the
    10081008Internet, for example. See <a class="link" href="smb.conf.5.html#REMOTEANNOUNCE">remote announce</a> in the <code class="filename">smb.conf</code> man page.
    1009 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id372438"></a>Problem Resolution</h3></div></div></div><p>
    1010 <a class="indexterm" name="id372445"></a>
    1011 <a class="indexterm" name="id372452"></a>
     1009</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>Problem Resolution</h3></div></div></div><p>
     1010<a class="indexterm" name="id3"></a>
     1011<a class="indexterm" name="id3"></a>
    10121012If something does not work, the <code class="filename">log.nmbd</code> file will help
    10131013to track down the problem. Try a <a class="link" href="smb.conf.5.html#LOGLEVEL">log level</a> of 2 or 3 for finding
    … …  
    10151015in text form in a file called <code class="filename">browse.dat</code>.
    10161016</p><p>
    1017 <a class="indexterm" name="id372486"></a>
    1018 <a class="indexterm" name="id372493"></a>
     1017<a class="indexterm" name="id3"></a>
     1018<a class="indexterm" name="id3"></a>
    10191019If it does not work, you should still be able to
    10201020type the server name as <code class="filename">\\SERVER</code> in <code class="literal">filemanager</code>, then
    10211021press enter, and <code class="literal">filemanager</code> should display the list of available shares.
    10221022</p><p>
    1023 <a class="indexterm" name="id372522"></a>
    1024 <a class="indexterm" name="id372529"></a>
     1023<a class="indexterm" name="id3"></a>
     1024<a class="indexterm" name="id3"></a>
    10251025Some people find browsing fails because they do not have the global
    10261026<a class="link" href="smb.conf.5.html#GUESTACCOUNT">guest account</a> set to a valid account. Remember that the
    10271027IPC$ connection that lists the shares is done as guest and so you must have a valid guest account.
    10281028</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
    1029 <a class="indexterm" name="id372553"></a>
    1030 <a class="indexterm" name="id372560"></a>
    1031 <a class="indexterm" name="id372567"></a>
    1032 <a class="indexterm" name="id372573"></a>
    1033 <a class="indexterm" name="id372580"></a>
     1029<a class="indexterm" name="id3"></a>
     1030<a class="indexterm" name="id3"></a>
     1031<a class="indexterm" name="id3"></a>
     1032<a class="indexterm" name="id3"></a>
     1033<a class="indexterm" name="id3"></a>
    10341034The <code class="literal">IPC$</code> share is used by all SMB/CIFS clients to obtain the list of resources that is
    10351035available on the server. This is the source of the list of shares and printers when browsing an SMB/CIFS
    … …  
    10391039connection to the <code class="literal">\\server\share</code>.
    10401040</p></div><p>
    1041 <a class="indexterm" name="id372612"></a>
    1042 <a class="indexterm" name="id372619"></a>
    1043 <a class="indexterm" name="id372626"></a>
    1044 <a class="indexterm" name="id372632"></a>
     1041<a class="indexterm" name="id3"></a>
     1042<a class="indexterm" name="id3"></a>
     1043<a class="indexterm" name="id3"></a>
     1044<a class="indexterm" name="id3"></a>
    10451045MS Windows 2000 and later (as with Samba) can be configured to disallow
    10461046anonymous (i.e., guest account) access to the IPC$ share. In that case, the
    … …  
    10501050server resources.
    10511051</p><p>
    1052 <a class="indexterm" name="id372646"></a>
     1052<a class="indexterm" name="id3"></a>
    10531053The other big problem people have is that their broadcast address,
    10541054netmask, or IP address is wrong (specified with the <a class="link" href="smb.conf.5.html#INTERFACES">interfaces</a> option
    10551055in <code class="filename">smb.conf</code>)
    1056 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id372672"></a>Cross-Subnet Browsing</h3></div></div></div><p>
    1057 <a class="indexterm" name="id372680"></a>
    1058 <a class="indexterm" name="id372689"></a>
     1056</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>Cross-Subnet Browsing</h3></div></div></div><p>
     1057<a class="indexterm" name="id3"></a>
     1058<a class="indexterm" name="id3"></a>
    10591059Since the release of Samba 1.9.17 (alpha1), Samba has supported the replication of browse lists across subnet
    10601060boundaries. This section describes how to set this feature up in different settings.
    10611061</p><p>
    1062 <a class="indexterm" name="id372701"></a>
    1063 <a class="indexterm" name="id372708"></a>
    1064 <a class="indexterm" name="id372714"></a>
    1065 <a class="indexterm" name="id372721"></a>
    1066 <a class="indexterm" name="id372728"></a>
    1067 <a class="indexterm" name="id372734"></a>
     1062<a class="indexterm" name="id3"></a>
     1063<a class="indexterm" name="id3"></a>
     1064<a class="indexterm" name="id3"></a>
     1065<a class="indexterm" name="id3"></a>
     1066<a class="indexterm" name="id3"></a>
     1067<a class="indexterm" name="id34"></a>
    10681068To see browse lists that span TCP/IP subnets (i.e., networks separated by routers that do not pass broadcast
    10691069traffic), you must set up at least one WINS server. The WINS server acts as a DNS for NetBIOS names. This will
    … …  
    10771077considered last resort methods.
    10781078</p><p>
    1079 <a class="indexterm" name="id372764"></a>
    1080 <a class="indexterm" name="id372771"></a>
    1081 <a class="indexterm" name="id372778"></a>
    1082 <a class="indexterm" name="id372785"></a>
     1079<a class="indexterm" name="id3"></a>
     1080<a class="indexterm" name="id3"></a>
     1081<a class="indexterm" name="id3"></a>
     1082<a class="indexterm" name="id3"></a>
    10831083Remember, for browsing across subnets to work correctly, all machines, be they Windows 95, Windows NT, or
    10841084Samba servers, must have the IP address of a WINS server given to them by a DHCP server or by manual
    … …  
    10861086settings; for Samba, this is in the <code class="filename">smb.conf</code> file.
    10871087</p><p>
    1088 <a class="indexterm" name="id372804"></a>
    1089 <a class="indexterm" name="id372810"></a>
    1090 <a class="indexterm" name="id372817"></a>
     1088<a class="indexterm" name="id3"></a>
     1089<a class="indexterm" name="id30"></a>
     1090<a class="indexterm" name="id3"></a>
    10911091It is possible to operate Samba-3 without NetBIOS over TCP/IP. If you do this, be warned that if used outside
    10921092of MS ADS, this will forgo network browsing support. ADS permits network browsing support through DNS,
    10931093providing appropriate DNS records are inserted for all Samba servers.
    1094 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id372827"></a>Behavior of Cross-Subnet Browsing</h4></div></div></div><p>
    1095 <a class="indexterm" name="id372835"></a>
    1096 <a class="indexterm" name="id372842"></a>
     1094</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id3"></a>Behavior of Cross-Subnet Browsing</h4></div></div></div><p>
     1095<a class="indexterm" name="id3"></a>
     1096<a class="indexterm" name="id3"></a>
    10971097Cross-subnet browsing is a complicated dance, containing multiple moving parts. It has taken Microsoft several
    10981098years to get the code that correctly achieves this, and Samba lags behind in some areas.  Samba is capable of
    … …  
    11011101Consider a network set up as in <a class="link" href="NetworkBrowsing.html#browsing1" title="Figure 10.1. Cross-Subnet Browsing Example.">Cross-Subnet Browsing Example</a>.
    11021102</p><div class="figure"><a name="browsing1"></a><p class="title"><b>Figure 10.1. Cross-Subnet Browsing Example.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/browsing1.png" width="216" alt="Cross-Subnet Browsing Example."></div></div></div><br class="figure-break"><p>
    1103 <a class="indexterm" name="id372906"></a>
    1104 <a class="indexterm" name="id372913"></a>
    1105 <a class="indexterm" name="id372919"></a>
     1103<a class="indexterm" name="id3"></a>
     1104<a class="indexterm" name="id3"></a>
     1105<a class="indexterm" name="id3"></a>
    11061106This consists of three subnets (1, 2, 3) connected by two routers (R1, R2), which do not pass broadcasts.
    11071107Subnet 1 has five machines on it, subnet 2 has four machines, and subnet 3 has four machines. Assume for the
    … …  
    11111111it.
    11121112</p><p>
    1113 <a class="indexterm" name="id372934"></a>
    1114 <a class="indexterm" name="id372941"></a>
    1115 <a class="indexterm" name="id372947"></a>
     1113<a class="indexterm" name="id3"></a>
     1114<a class="indexterm" name="id3"></a>
     1115<a class="indexterm" name="id3"></a>
    11161116As these machines are booted up, elections for master browsers
    11171117take place on each of the three subnets. Assume that machine
    … …  
    11211121LMB on subnet 1 because it is set up as DMB.
    11221122</p><p>
    1123 <a class="indexterm" name="id372960"></a>
    1124 <a class="indexterm" name="id372966"></a>
     1123<a class="indexterm" name="id3"></a>
     1124<a class="indexterm" name="id36"></a>
    11251125On each of the three networks, machines that are configured to offer sharing services will broadcast that they
    11261126are offering these services. The LMB on each subnet will receive these broadcasts and keep a record of the
    … …  
    11291129list.
    11301130</p><p>
    1131 <a class="indexterm" name="id372980"></a>
    1132 <a class="indexterm" name="id372987"></a>
    1133 <a class="indexterm" name="id372994"></a>
    1134 <a class="indexterm" name="id373000"></a>
    1135 <a class="indexterm" name="id373007"></a>
     1131<a class="indexterm" name="id3"></a>
     1132<a class="indexterm" name="id3"></a>
     1133<a class="indexterm" name="id3"></a>
     1134<a class="indexterm" name="id30"></a>
     1135<a class="indexterm" name="id3"></a>
    11361136For each network, the LMB on that network is
    11371137considered <span class="emphasis"><em>authoritative</em></span> for all the names it receives via
    … …  
    11441144called <span class="emphasis"><em>non-authoritative.</em></span>
    11451145</p><p>
    1146 <a class="indexterm" name="id373035"></a>
     1146<a class="indexterm" name="id3"></a>
    11471147At this point the browse lists appear as shown in <a class="link" href="NetworkBrowsing.html#browsubnet" title="Table 10.1. Browse Subnet Example 1">Browse Subnet Example 1</a>
    11481148(these are the machines you would see in your network neighborhood if you looked in it on a particular network
    … …  
    11531153At this point all the subnets are separate, and no machine is seen across any of the subnets.
    11541154</p><p>
    1155 <a class="indexterm" name="id373125"></a>
    1156 <a class="indexterm" name="id373132"></a>
    1157 <a class="indexterm" name="id373138"></a>
    1158 <a class="indexterm" name="id373145"></a>
     1155<a class="indexterm" name="id3"></a>
     1156<a class="indexterm" name="id3"></a>
     1157<a class="indexterm" name="id38"></a>
     1158<a class="indexterm" name="id3"></a>
    11591159Now examine subnet 2 in <a class="link" href="NetworkBrowsing.html#brsbex" title="Table 10.2. Browse Subnet Example 2">Browse Subnet Example 2</a>.  As soon as N2_B has become the
    11601160LMB, it looks for a DMB with which to synchronize its browse list. It does this by querying the WINS server
    … …  
    11621162the DMB (N1_C) with the WINS server as soon as it was started.
    11631163</p><p>
    1164 <a class="indexterm" name="id373167"></a>
    1165 <a class="indexterm" name="id373174"></a>
    1166 <a class="indexterm" name="id373180"></a>
    1167 <a class="indexterm" name="id373187"></a>
     1164<a class="indexterm" name="id3"></a>
     1165<a class="indexterm" name="id3"></a>
     1166<a class="indexterm" name="id3"></a>
     1167<a class="indexterm" name="id3"></a>
    11681168Once N2_B knows the address of the DMB, it tells it that is the LMB for subnet 2 by sending a
    11691169<span class="emphasis"><em>MasterAnnouncement</em></span> packet as a UDP port 138 packet.  It then synchronizes with it by
    … …  
    11751175N2_A(*), N2_B(*), N2_C(*), N2_D(*)</td></tr><tr><td align="left">Subnet2</td><td align="left">N2_B</td><td align="justify">N2_A, N2_B, N2_C, N2_D, N1_A(*),
    11761176N1_B(*), N1_C(*), N1_D(*), N1_E(*)</td></tr><tr><td align="left">Subnet3</td><td align="left">N3_D</td><td align="justify">N3_A, N3_B, N3_C, N3_D</td></tr></tbody></table></div></div><br class="table-break"><p>
    1177 <a class="indexterm" name="id373295"></a>
     1177<a class="indexterm" name="id3"></a>
    11781178Servers with an (*) after them are non-authoritative names.
    11791179</p><p>
    1180 <a class="indexterm" name="id373306"></a>
     1180<a class="indexterm" name="id3"></a>
    11811181At this point users looking in their Network Neighborhood on subnets 1 or 2 will see all the servers on both;
    11821182users on subnet 3 will still see only the servers on their own subnet.
    11831183</p><p>
    1184 <a class="indexterm" name="id373317"></a>
     1184<a class="indexterm" name="id3"></a>
    11851185The same sequence of events that occurred for N2_B now occurs for the LMB on subnet 3 (N3_D). When it
    11861186synchronizes browse lists with the DMB (N1_A) it gets both the server entries on subnet 1 and those on subnet
    … …  
    11961196subnet 2 will still see only the servers on subnets 1 and 2, but not 3.
    11971197</p><p>
    1198 <a class="indexterm" name="id373427"></a>
    1199 <a class="indexterm" name="id373433"></a>
    1200 <a class="indexterm" name="id373440"></a>
     1198<a class="indexterm" name="id3"></a>
     1199<a class="indexterm" name="id3"></a>
     1200<a class="indexterm" name="id3"></a>
    12011201Finally, the LMB for subnet 2 (N2_B) will sync again
    12021202with the DMB (N1_C) and will receive the missing
    … …  
    12191219If either router R1 or R2 fails, the following will occur:
    12201220</p><div class="orderedlist"><ol type="1"><li><p>
    1221 <a class="indexterm" name="id373562"></a>
     1221<a class="indexterm" name="id3"></a>
    12221222        Names of computers on each side of the inaccessible network fragments
    12231223        will be maintained for as long as 36 minutes in the Network Neighborhood
    … …  
    12271227        names will not be removed from the Network Neighborhood lists.
    12281228        </p></li><li><p>
    1229 <a class="indexterm" name="id373584"></a>
    1230 <a class="indexterm" name="id373591"></a>
    1231 <a class="indexterm" name="id373598"></a>
     1229<a class="indexterm" name="id3"></a>
     1230<a class="indexterm" name="id3"></a>
     1231<a class="indexterm" name="id3"></a>
    12321232        If one of the fragments is cut off from the WINS server, it will only
    12331233        be able to access servers on its local subnet using subnet-isolated
    12341234        broadcast NetBIOS name resolution. The effect is similar to that of
    12351235        losing access to a DNS server.
    1236         </p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id373613"></a>Common Errors</h2></div></div></div><p>
    1237 <a class="indexterm" name="id373621"></a>
    1238 <a class="indexterm" name="id373627"></a>
     1236        </p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3"></a>Common Errors</h2></div></div></div><p>
     1237<a class="indexterm" name="id3"></a>
     1238<a class="indexterm" name="id3"></a>
    12391239Many questions are asked on the mailing lists regarding browsing. The majority of browsing
    12401240problems originate from incorrect configuration of NetBIOS name resolution. Some are of
    12411241particular note.
    1242 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id373637"></a>Flushing the Samba NetBIOS Name Cache</h3></div></div></div><p>
     1242</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>Flushing the Samba NetBIOS Name Cache</h3></div></div></div><p>
    12431243How Can One Flush the Samba NetBIOS Name Cache without Restarting Samba?
    12441244</p><p>
    1245 <a class="indexterm" name="id373649"></a>
    1246 <a class="indexterm" name="id373656"></a>
    1247 <a class="indexterm" name="id373662"></a>
    1248 <a class="indexterm" name="id373669"></a>
     1245<a class="indexterm" name="id3"></a>
     1246<a class="indexterm" name="id3"></a>
     1247<a class="indexterm" name="id32"></a>
     1248<a class="indexterm" name="id3"></a>
    12491249Samba's <code class="literal">nmbd</code> process controls all browse list handling. Under normal circumstances it is
    12501250safe to restart <code class="literal">nmbd</code>. This will effectively flush the Samba NetBIOS name cache and cause it
    … …  
    12561256other thing you can do is wait until the entry times out and is then flushed from the list.
    12571257This may take a long time on some networks (perhaps months).
    1258 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id373702"></a>Server Resources Cannot Be Listed</h3></div></div></div><p>&#8220;<span class="quote">My Client Reports "&#8216;<span class="quote">This server is not configured to list shared resources."</span>&#8217;</span>&#8221;</p><p>
     1258</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>Server Resources Cannot Be Listed</h3></div></div></div><p>&#8220;<span class="quote">My Client Reports "&#8216;<span class="quote">This server is not configured to list shared resources."</span>&#8217;</span>&#8221;</p><p>
    12591259Your guest account is probably invalid for some reason. Samba uses the
    12601260guest account for browsing in <code class="literal">smbd</code>. Check that your guest account is
    12611261valid.
    1262 </p><p>Also see <a class="link" href="smb.conf.5.html#GUESTACCOUNT">guest account</a> in the <code class="filename">smb.conf</code> man page.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id373747"></a>I Get an "<span class="errorname">Unable to browse the network</span>" Error</h3></div></div></div><p>This error can have multiple causes:
    1263 <a class="indexterm" name="id373759"></a>
     1262</p><p>Also see <a class="link" href="smb.conf.5.html#GUESTACCOUNT">guest account</a> in the <code class="filename">smb.conf</code> man page.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>I Get an "<span class="errorname">Unable to browse the network</span>" Error</h3></div></div></div><p>This error can have multiple causes:
     1263<a class="indexterm" name="id3"></a>
    12641264        </p><div class="itemizedlist"><ul type="disc"><li><p>There is no LMB. Configure <span class="application">nmbd</span>
    12651265                        or any other machine to serve as LMB.</p></li><li><p>You cannot log onto the machine that is the LMB.
    12661266                        Can you log on to it as a guest user? </p></li><li><p>There is no IP connectivity to the LMB.
    1267                         Can you reach it by broadcast?</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id373792"></a>Browsing of Shares and Directories is Very Slow</h3></div></div></div><p>&#8220;<span class="quote">
    1268 <a class="indexterm" name="id373801"></a>
     1267                        Can you reach it by broadcast?</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>Browsing of Shares and Directories is Very Slow</h3></div></div></div><p>&#8220;<span class="quote">
     1268<a class="indexterm" name="id3"></a>
    12691269There are only two machines on a test network. One is a Samba server, the other a Windows XP machine.
    12701270Authentication and logons work perfectly, but when I try to explore shares on the Samba server, the
    … …  
    12731273</span>&#8221;
    12741274</p><p>&#8220;<span class="quote">
    1275 <a class="indexterm" name="id373817"></a>
     1275<a class="indexterm" name="id3"></a>
    12761276But, the share is immediately available from a command shell (<code class="literal">cmd</code>, followed by
    12771277exploration with DOS command. Is this a Samba problem, or is it a Windows problem? How can I solve this?
    … …  
    12791279Here are a few possibilities:
    12801280</p><div class="variablelist"><dl><dt><span class="term">Bad Networking Hardware</span></dt><dd><p>
    1281 <a class="indexterm" name="id373846"></a>
    1282 <a class="indexterm" name="id373853"></a>
    1283 <a class="indexterm" name="id373860"></a>
    1284 <a class="indexterm" name="id373867"></a>
    1285 <a class="indexterm" name="id373874"></a>
     1281<a class="indexterm" name="id3"></a>
     1282<a class="indexterm" name="id3"></a>
     1283<a class="indexterm" name="id3"></a>
     1284<a class="indexterm" name="id3"></a>
     1285<a class="indexterm" name="id3"></a>
    12861286                Most common defective hardware problems center around low cost or defective hubs, routers,
    12871287                network interface controllers (NICs), and bad wiring. If one piece of hardware is defective,
    … …  
    12901290                but not all.
    12911291                </p></dd><dt><span class="term">The Windows XP WebClient</span></dt><dd><p>
    1292 <a class="indexterm" name="id373895"></a>
     1292<a class="indexterm" name="id3"></a>
    12931293                A number of sites have reported similar slow network browsing problems and found that when
    12941294                the WebClient service is turned off, the problem disappears. This is certainly something
    12951295                that should be explored because it is a simple solution  if it works.
    12961296                </p></dd><dt><span class="term">Inconsistent WINS Configuration</span></dt><dd><p>
    1297 <a class="indexterm" name="id373918"></a>
    1298 <a class="indexterm" name="id373924"></a>
     1297<a class="indexterm" name="id3"></a>
     1298<a class="indexterm" name="id3"></a>
    12991299                This type of problem is common when one client is configured to use a WINS server (that is
    13001300                a TCP/IP configuration setting) and there is no WINS server on the network. Alternatively,
    … …  
    13041304                server, nor should it be configured to use one.
    13051305                </p></dd><dt><span class="term">Incorrect DNS Configuration</span></dt><dd><p>
    1306 <a class="indexterm" name="id373947"></a>
    1307 <a class="indexterm" name="id373953"></a>
     1306<a class="indexterm" name="id3"></a>
     1307<a class="indexterm" name="id3"></a>
    13081308                If use of NetBIOS over TCP/IP is disabled, Active Directory is in use and the DNS server
    13091309                has been incorrectly configured. For further information refer to
    13101310                <a class="link" href="NetworkBrowsing.html#adsdnstech" title="DNS and Active Directory">DNS and Active Directory</a>.
    1311                 </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id373973"></a>Invalid Cached Share References Affects Network Browsing</h3></div></div></div><p>
    1312 <a class="indexterm" name="id373981"></a>
    1313 <a class="indexterm" name="id373988"></a>
     1311                </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3"></a>Invalid Cached Share References Affects Network Browsing</h3></div></div></div><p>
     1312<a class="indexterm" name="id3"></a>
     1313<a class="indexterm" name="id3"></a>
    13141314Cached references on your MS Windows client (workstation or server) to shares or servers that no longer exist
    13151315can cause MS Windows Explorer to appear unresponsive as it tries to connect to these shares. After a delay
    … …  
    13291329selecting <span class="emphasis"><em>Delete.</em></span>
    13301330</p></div><p>
    1331 <a class="indexterm" name="id374051"></a>
     1331<a class="indexterm" name="id3"></a>
    13321332Samba users have reported that these stale references negatively affect network browsing with Windows, Samba,
    13331333and Novell servers. It is suspected to be a universal problem not directly related to the Samba
Note: See TracChangeset for help on using the changeset viewer.