- Timestamp:
- Jan 15, 2010, 8:21:06 AM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.3.x/docs/htmldocs/Samba3-HOWTO/integrate-ms-networks.html
r342 r368 1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 29. Integrating MS Windows Networks with Samba</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.7 4.0"><link rel="home" href="index.html" title="The Official Samba 3.3.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="pam.html" title="Chapter 28. PAM-Based Distributed Authentication"><link rel="next" href="unicode.html" title="Chapter 30. Unicode/Charsets"></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 29. Integrating MS Windows Networks with Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="pam.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="unicode.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="integrate-ms-networks"></a>Chapter 29. Integrating MS Windows Networks with Samba</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:[email protected]">[email protected]</a>></code></p></div></div></div></div><div><p class="pubdate"> (Jan 01 2001) </p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668091">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668111">Background Information</a></span></dt><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668240">Name Resolution in a Pure UNIX/Linux World</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668313">/etc/hosts</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668502">/etc/resolv.conf</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668538">/etc/host.conf</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2668589">/etc/nsswitch.conf</a></span></dt></dl></dd><dt><span class="sect1"><a href="integrate-ms-networks.html#id2668713">Name Resolution as Used within MS Windows Networking</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669148">The NetBIOS Name Cache</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669234">The LMHOSTS File</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669410">HOSTS File</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669438">DNS Lookup</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669465">WINS Lookup</a></span></dt></dl></dd><dt><span class="sect1"><a href="integrate-ms-networks.html#id2669603">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669616">Pinging Works Only One Way</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669647">Very Slow Network Connections</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2669689">Samba Server Name-Change Problem</a></span></dt></dl></dd></dl></div><p>2 <a class="indexterm" name="id26 68049"></a>1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 29. Integrating MS Windows Networks with Samba</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.7">Samba Server Name-Change Problem</a></span></dt></dl></dd></dl></div><p> 2 <a class="indexterm" name="id26"></a> 3 3 This chapter deals with NetBIOS over TCP/IP name to IP address resolution. If 4 4 your MS Windows clients are not configured to use NetBIOS over TCP/IP, then this 5 5 section does not apply to your installation. If your installation involves the use of 6 6 NetBIOS over TCP/IP, then this chapter may help you to resolve networking problems. 7 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>8 <a class="indexterm" name="id26 68066"></a>9 <a class="indexterm" name="id26 68073"></a>7 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 8 <a class="indexterm" name="id26"></a> 9 <a class="indexterm" name="id26"></a> 10 10 NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS 11 11 over Logical Link Control (LLC). On modern networks it is highly advised … … 13 13 NetBEUI over TCP/IP the existence of such a protocol is a complete 14 14 and utter misapprehension. 15 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2668091"></a>Features and Benefits</h2></div></div></div><p>15 </p></div><div class="sect1" "></a>Features and Benefits</h2></div></div></div><p> 16 16 Many MS Windows network administrators have never been exposed to basic TCP/IP 17 17 networking as it is implemented in a UNIX/Linux operating system. Likewise, many UNIX and … … 21 21 This chapter gives a short introduction to the basics of how a name can be resolved to 22 22 its IP address for each operating system environment. 23 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2668111"></a>Background Information</h2></div></div></div><p>24 <a class="indexterm" name="id26 68119"></a>25 <a class="indexterm" name="id26 68126"></a>26 <a class="indexterm" name="id26 68133"></a>27 <a class="indexterm" name="id26 68140"></a>28 <a class="indexterm" name="id26 68147"></a>23 </p></div><div class="sect1" "></a>Background Information</h2></div></div></div><p> 24 <a class="indexterm" name="id26"></a> 25 <a class="indexterm" name="id26"></a> 26 <a class="indexterm" name="id26"></a> 27 <a class="indexterm" name="id26"></a> 28 <a class="indexterm" name="id26"></a> 29 29 Since the introduction of MS Windows 2000, it is possible to run MS Windows networking 30 30 without the use of NetBIOS over TCP/IP. NetBIOS over TCP/IP uses UDP port 137 for NetBIOS … … 32 32 TCP/IP is disabled on MS Windows 2000 and later clients, then only the TCP port 445 is 33 33 used, and the UDP port 137 and TCP port 139 are not. 34 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>34 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 35 35 When using Windows 2000 or later clients, if NetBIOS over TCP/IP is not disabled, then 36 36 the client will use UDP port 137 (NetBIOS Name Service, also known as the Windows Internet 37 37 Name Service, or WINS), TCP port 139, and TCP port 445 (for actual file and print traffic). 38 38 </p></div><p> 39 <a class="indexterm" name="id26 68175"></a>40 <a class="indexterm" name="id26 68181"></a>41 <a class="indexterm" name="id26 68188"></a>42 <a class="indexterm" name="id26 68195"></a>43 <a class="indexterm" name="id26 68201"></a>44 <a class="indexterm" name="id26 68208"></a>39 <a class="indexterm" name="id26"></a> 40 <a class="indexterm" name="id26"></a> 41 <a class="indexterm" name="id26"></a> 42 <a class="indexterm" name="id26"></a> 43 <a class="indexterm" name="id26"></a> 44 <a class="indexterm" name="id26"></a> 45 45 When NetBIOS over TCP/IP is disabled, the use of DNS is essential. Most installations that disable NetBIOS 46 46 over TCP/IP today use MS Active Directory Service (ADS). ADS requires 47 <a class="indexterm" name="id26 68218"></a> dynamic DNS with Service Resource48 Records (SRV RR) and with Incremental Zone Transfers (IXFR). <a class="indexterm" name="id26 68229"></a>47 <a class="indexterm" name="id26"></a> dynamic DNS with Service Resource 48 Records (SRV RR) and with Incremental Zone Transfers (IXFR). <a class="indexterm" name="id26"></a> 49 49 Use of DHCP with ADS is recommended as a further means of maintaining central control over the client 50 50 workstation network configuration. 51 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2668240"></a>Name Resolution in a Pure UNIX/Linux World</h2></div></div></div><p>51 </p></div><div class="sect1" "></a>Name Resolution in a Pure UNIX/Linux World</h2></div></div></div><p> 52 52 The key configuration files covered in this section are: 53 </p><a class="indexterm" name="id26 68250"></a><a class="indexterm" name="id2668257"></a><a class="indexterm" name="id2668264"></a><a class="indexterm" name="id2668271"></a><div class="itemizedlist"><ul type="disc"><li><p><code class="filename">/etc/hosts</code></p></li><li><p><code class="filename">/etc/resolv.conf</code></p></li><li><p><code class="filename">/etc/host.conf</code></p></li><li><p><code class="filename">/etc/nsswitch.conf</code></p></li></ul></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2668313"></a><code class="filename">/etc/hosts</code></h3></div></div></div><p>53 </p><a class="indexterm" name="id26"></a><code class="filename">/etc/hosts</code></h3></div></div></div><p> 54 54 This file contains a static list of IP addresses and names. 55 55 </p><pre class="programlisting"> … … 58 58 </pre><p> 59 59 </p><p> 60 <a class="indexterm" name="id26 68336"></a>61 <a class="indexterm" name="id26 68343"></a>60 <a class="indexterm" name="id26"></a> 61 <a class="indexterm" name="id26"></a> 62 62 The purpose of <code class="filename">/etc/hosts</code> is to provide a 63 63 name resolution mechanism so users do not need to remember 64 64 IP addresses. 65 65 </p><p> 66 <a class="indexterm" name="id26 68361"></a>67 <a class="indexterm" name="id26 68368"></a>68 <a class="indexterm" name="id26 68375"></a>66 <a class="indexterm" name="id26"></a> 67 <a class="indexterm" name="id26"></a> 68 <a class="indexterm" name="id26"></a> 69 69 Network packets that are sent over the physical network transport 70 70 layer communicate not via IP addresses but rather using the Media … … 73 73 numbers that are separated by a dot (or period) for example, 168.192.1.1. 74 74 </p><p> 75 <a class="indexterm" name="id26 68393"></a>75 <a class="indexterm" name="id26"></a> 76 76 MAC addresses use 48 bits (or 6 bytes) and are typically represented 77 77 as two-digit hexadecimal numbers separated by colons: 40:8e:0a:12:34:56. … … 85 85 address that will be returned in the Address Resolution Protocol (ARP) reply. 86 86 </p><p> 87 <a class="indexterm" name="id26 68424"></a>87 <a class="indexterm" name="id26"></a> 88 88 When a user or a process wants to communicate with another machine, 89 the protocol implementation ensures that the “<span class="quote">machine name</span>” or“<span class="quote">host90 name</span>” is resolved to an IP address in a manner that is controlled89 the protocol implementation ensures that the “<span class="quote">host 90 name</span>” is resolved to an IP address in a manner that is controlled 91 91 by the TCP/IP configuration control files. The file 92 92 <code class="filename">/etc/hosts</code> is one such file. 93 93 </p><p> 94 <a class="indexterm" name="id26 68451"></a>94 <a class="indexterm" name="id26"></a> 95 95 When the IP address of the destination interface has been determined, a protocol called ARP/RARP is used to 96 96 identify the MAC address of the target interface. ARP is a broadcast-oriented method that uses User Datagram … … 100 100 IP address for each interface. 101 101 </p><p> 102 <a class="indexterm" name="id26 68480"></a>102 <a class="indexterm" name="id26"></a> 103 103 The <code class="filename">/etc/hosts</code> file is foundational to all 104 104 UNIX/Linux TCP/IP installations and as a minimum will contain … … 108 108 resolution can exist before any other method of name resolution 109 109 becomes available. 110 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2668502"></a><code class="filename">/etc/resolv.conf</code></h3></div></div></div><p>110 </p></div><div class="sect2" "></a><code class="filename">/etc/resolv.conf</code></h3></div></div></div><p> 111 111 This file tells the name resolution libraries: 112 </p><div class="itemizedlist"><ul type="disc"><li><p>The name of the domain to which the machine112 </p><div class="itemizedlist"><ul ><p>The name of the domain to which the machine 113 113 belongs. 114 </p></li><li ><p>The name(s) of any domains that should be114 </p></li><li><p>The name(s) of any domains that should be 115 115 automatically searched when trying to resolve unqualified 116 116 host names to their IP address. 117 </p></li><li ><p>The name or IP address of available domain117 </p></li><li><p>The name or IP address of available domain 118 118 name servers that may be asked to perform name-to-address 119 119 translation lookups. 120 </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2668538"></a><code class="filename">/etc/host.conf</code></h3></div></div></div><p>121 <a class="indexterm" name="id26 68549"></a>120 </p></li></ul></div></div><div class="sect2" "></a><code class="filename">/etc/host.conf</code></h3></div></div></div><p> 121 <a class="indexterm" name="id26"></a> 122 122 <code class="filename">/etc/host.conf</code> is the primary means by which the setting in 123 123 <code class="filename">/etc/resolv.conf</code> may be effected. It is a critical configuration file. This file controls … … 128 128 </pre><p>Both addresses should be returned. Please refer to the 129 129 man page for <code class="filename">host.conf</code> for further details. 130 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2668589"></a><code class="filename">/etc/nsswitch.conf</code></h3></div></div></div><p>131 <a class="indexterm" name="id26 68600"></a>130 </p></div><div class="sect2" "></a><code class="filename">/etc/nsswitch.conf</code></h3></div></div></div><p> 131 <a class="indexterm" name="id26"></a> 132 132 This file controls the actual name resolution targets. The 133 133 file typically has resolver object specifications as follows: … … 161 161 principal of speaking only when necessary. 162 162 </p><p> 163 <a class="indexterm" name="id26 68636"></a>164 <a class="indexterm" name="id26 68643"></a>165 <a class="indexterm" name="id26 68650"></a>166 <a class="indexterm" name="id26 68657"></a>167 <a class="indexterm" name="id26 68664"></a>163 <a class="indexterm" name="id26"></a> 164 <a class="indexterm" name="id26"></a> 165 <a class="indexterm" name="id26"></a> 166 <a class="indexterm" name="id26"></a> 167 <a class="indexterm" name="id26"></a> 168 168 Starting with version 2.2.0, Samba has Linux support for extensions to 169 169 the name service switch infrastructure so Linux clients will … … 173 173 nsswitch/libnss_wins.so</code></strong>). The resulting library should 174 174 then be installed in the <code class="filename">/lib</code> directory, and 175 the <em class="parameter"><code>wins</code></em> parameter needs to be added to the “<span class="quote">hosts:</span>”line in175 the <em class="parameter"><code>wins</code></em> parameter needs to be added to the line in 176 176 the <code class="filename">/etc/nsswitch.conf</code> file. At this point, it 177 177 will be possible to ping any MS Windows machine by its NetBIOS 178 178 machine name, as long as that machine is within the workgroup to 179 179 which both the Samba machine and the MS Windows machine belong. 180 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2668713"></a>Name Resolution as Used within MS Windows Networking</h2></div></div></div><p>181 <a class="indexterm" name="id26 68722"></a>182 <a class="indexterm" name="id26 68728"></a>183 <a class="indexterm" name="id26 68735"></a>184 <a class="indexterm" name="id26 68742"></a>180 </p></div></div><div class="sect1" "></a>Name Resolution as Used within MS Windows Networking</h2></div></div></div><p> 181 <a class="indexterm" name="id26"></a> 182 <a class="indexterm" name="id26"></a> 183 <a class="indexterm" name="id26"></a> 184 <a class="indexterm" name="id26"></a> 185 185 MS Windows networking is predicated on the name each machine is given. This name is known variously (and 186 inconsistently) as the “<span class="quote">computer name,</span>” “<span class="quote">machine name,</span>”“<span class="quote">networking187 name,</span>” “<span class="quote">NetBIOS name,</span>” or “<span class="quote">SMB name.</span>”All terms mean the same thing with the188 exception of “<span class="quote">NetBIOS name,</span>”which can also apply to the name of the workgroup or the domain189 name. The terms “<span class="quote">workgroup</span>” and “<span class="quote">domain</span>”are really just a simple name with which186 inconsistently) as the “<span class="quote">networking 187 name,</span>” All terms mean the same thing with the 188 exception of which can also apply to the name of the workgroup or the domain 189 name. The terms are really just a simple name with which 190 190 the machine is associated. All NetBIOS names are exactly 16 characters in length. The 191 191 16<sup>th</sup> character is reserved. It is used to store a 1-byte value that indicates … … 196 196 list typical NetBIOS name/service type registrations. 197 197 </p><div class="table"><a name="uniqnetbiosnames"></a><p class="title"><b>Table 29.1. Unique NetBIOS Names</b></p><div class="table-contents"><table summary="Unique NetBIOS Names" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="left">MACHINENAME<00></td><td align="justify">Server Service is running on MACHINENAME</td></tr><tr><td align="left">MACHINENAME<03></td><td align="justify">Generic machine name (NetBIOS name)</td></tr><tr><td align="left">MACHINENAME<20></td><td align="justify">LanMan server service is running on MACHINENAME</td></tr><tr><td align="left">WORKGROUP<1b></td><td align="justify">Domain master browser</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="netbiosnamesgrp"></a><p class="title"><b>Table 29.2. Group Names</b></p><div class="table-contents"><table summary="Group Names" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="left">WORKGROUP<03></td><td align="justify">Generic name registered by all members of WORKGROUP</td></tr><tr><td align="left">WORKGROUP<1c></td><td align="justify">Domain cntrollers/netlogon servers</td></tr><tr><td align="left">WORKGROUP<1d></td><td align="justify">Local master browsers</td></tr><tr><td align="left">WORKGROUP<1e></td><td align="justify">Browser election service</td></tr></tbody></table></div></div><br class="table-break"><p> 198 <a class="indexterm" name="id26 68939"></a>198 <a class="indexterm" name="id26"></a> 199 199 It should be noted that all NetBIOS machines register their own 200 200 names as per <a class="link" href="integrate-ms-networks.html#uniqnetbiosnames" title="Table 29.1. Unique NetBIOS Names">Unique NetBIOS names</a> and <a class="link" href="integrate-ms-networks.html#netbiosnamesgrp" title="Table 29.2. Group Names">group names</a>. This is in vast contrast to TCP/IP … … 203 203 are associated with each IP address. 204 204 </p><p> 205 <a class="indexterm" name="id26 68974"></a>206 <a class="indexterm" name="id26 68981"></a>207 <a class="indexterm" name="id26 68987"></a>205 <a class="indexterm" name="id26"></a> 206 <a class="indexterm" name="id26"></a> 207 <a class="indexterm" name="id26"></a> 208 208 One further point of clarification should be noted. The <code class="filename">/etc/hosts</code> 209 209 file and the DNS records do not provide the NetBIOS name information … … 217 217 Whichever machine first replies, it then ends up providing the logon services. 218 218 </p><p> 219 <a class="indexterm" name="id26 69019"></a>220 <a class="indexterm" name="id26 69026"></a>221 The name “<span class="quote">workgroup</span>” or “<span class="quote">domain</span>”really can be confusing, since these219 <a class="indexterm" name="id26"></a> 220 <a class="indexterm" name="id26"></a> 221 The name really can be confusing, since these 222 222 have the added significance of indicating what is the security 223 architecture of the MS Windows network. The term “<span class="quote">workgroup</span>”indicates223 architecture of the MS Windows network. The term indicates 224 224 that the primary nature of the network environment is that of a 225 225 peer-to-peer design. In a workgroup, all machines are responsible for … … 231 231 of a username and a matching password. 232 232 </p><p> 233 <a class="indexterm" name="id26 69059"></a>234 <a class="indexterm" name="id26 69065"></a>235 <a class="indexterm" name="id26 69075"></a>236 <a class="indexterm" name="id26 69084"></a>237 <a class="indexterm" name="id26 69094"></a>238 <a class="indexterm" name="id26 69103"></a>239 <a class="indexterm" name="id26 69110"></a>240 <a class="indexterm" name="id26 69117"></a>233 <a class="indexterm" name="id26"></a> 234 <a class="indexterm" name="id26"></a> 235 <a class="indexterm" name="id26"></a> 236 <a class="indexterm" name="id26"></a> 237 <a class="indexterm" name="id26"></a> 238 <a class="indexterm" name="id26"></a> 239 <a class="indexterm" name="id26"></a> 240 <a class="indexterm" name="id26"></a> 241 241 MS Windows networking is thus predetermined to use machine names 242 242 for all local and remote machine message passing. The protocol used is … … 253 253 Since we are primarily concerned with TCP/IP, this demonstration is 254 254 limited to this area. 255 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669148"></a>The NetBIOS Name Cache</h3></div></div></div><p>256 <a class="indexterm" name="id26 69155"></a>257 <a class="indexterm" name="id26 69162"></a>258 <a class="indexterm" name="id26 69169"></a>255 </p><div class="sect2" "></a>The NetBIOS Name Cache</h3></div></div></div><p> 256 <a class="indexterm" name="id26"></a> 257 <a class="indexterm" name="id26"></a> 258 <a class="indexterm" name="id26"></a> 259 259 All MS Windows machines employ an in-memory buffer in which is 260 260 stored the NetBIOS names and IP addresses for all external … … 264 264 configured name resolution mechanisms. 265 265 </p><p> 266 <a class="indexterm" name="id26 69184"></a>266 <a class="indexterm" name="id26"></a> 267 267 If a machine whose name is in the local name cache is shut 268 268 down before the name is expired and flushed from the cache, then … … 272 272 frustrating for users but is a characteristic of the protocol. 273 273 </p><p> 274 <a class="indexterm" name="id26 69200"></a>275 <a class="indexterm" name="id26 69207"></a>276 <a class="indexterm" name="id26 69214"></a>274 <a class="indexterm" name="id26"></a> 275 <a class="indexterm" name="id26"></a> 276 <a class="indexterm" name="id26"></a> 277 277 The MS Windows utility that allows examination of the NetBIOS 278 name cache is called “<span class="quote">nbtstat.</span>”The Samba equivalent278 name cache is called The Samba equivalent 279 279 is called <code class="literal">nmblookup</code>. 280 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669234"></a>The LMHOSTS File</h3></div></div></div><p>281 <a class="indexterm" name="id26 69242"></a>280 </p></div><div class="sect2" "></a>The LMHOSTS File</h3></div></div></div><p> 281 <a class="indexterm" name="id26"></a> 282 282 This file is usually located in MS Windows NT 4.0 or Windows 200x/XP in the directory 283 283 <code class="filename">%SystemRoot%\SYSTEM32\DRIVERS\ETC</code> and contains the IP address … … 364 364 # Therefore it is not advisable to simply add lmhosts file entries onto the 365 365 # end of this file. 366 </pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669410"></a>HOSTS File</h3></div></div></div><p>366 </pre></div><div class="sect2" "></a>HOSTS File</h3></div></div></div><p> 367 367 This file is usually located in MS Windows NT 4.0 or Windows 200x/XP in 368 368 the directory <code class="filename">%SystemRoot%\SYSTEM32\DRIVERS\ETC</code> and contains … … 371 371 on how the TCP/IP environment is configured. This file is in 372 372 every way the equivalent of the UNIX/Linux <code class="filename">/etc/hosts</code> file. 373 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669438"></a>DNS Lookup</h3></div></div></div><p>374 <a class="indexterm" name="id26 69446"></a>373 </p></div><div class="sect2" "></a>DNS Lookup</h3></div></div></div><p> 374 <a class="indexterm" name="id26"></a> 375 375 This capability is configured in the TCP/IP setup area in the network 376 376 configuration facility. If enabled, an elaborate name resolution sequence … … 383 383 WINS server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast 384 384 lookup is used. 385 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669465"></a>WINS Lookup</h3></div></div></div><p>386 <a class="indexterm" name="id26 69473"></a>387 <a class="indexterm" name="id26 69480"></a>388 <a class="indexterm" name="id26 69489"></a>385 </p></div><div class="sect2" "></a>WINS Lookup</h3></div></div></div><p> 386 <a class="indexterm" name="id26"></a> 387 <a class="indexterm" name="id26"></a> 388 <a class="indexterm" name="id26"></a> 389 389 A WINS (Windows Internet Name Server) service is the equivalent of the 390 390 rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores … … 394 394 To configure Samba to be a WINS server, the following parameter needs 395 395 to be added to the <code class="filename">smb.conf</code> file: 396 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2669522"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr></table><p>397 <a class="indexterm" name="id26 69536"></a>396 </p><table "></a><em class="parameter"><code>wins support = Yes</code></em></td></tr></table><p> 397 <a class="indexterm" name="id26"></a> 398 398 To configure Samba to use a WINS server, the following parameters are 399 399 needed in the <code class="filename">smb.conf</code> file: 400 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2669558"></a><em class="parameter"><code>wins support = No</code></em></td></tr><tr><td><a class="indexterm" name="id2669570"></a><em class="parameter"><code>wins server = xxx.xxx.xxx.xxx</code></em></td></tr></table><p>400 </p><table "></a><em class="parameter"><code>wins server = xxx.xxx.xxx.xxx</code></em></td></tr></table><p> 401 401 where <em class="replaceable"><code>xxx.xxx.xxx.xxx</code></em> is the IP address 402 402 of the WINS server. 403 403 </p><p>For information about setting up Samba as a WINS server, read 404 <a class="link" href="NetworkBrowsing.html" title="Chapter 10. Network Browsing">Network Browsing</a>.</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2669603"></a>Common Errors</h2></div></div></div><p>404 <a class="link" href="NetworkBrowsing.html" title="Chapter 10. Network Browsing">Network Browsing</a>.</p></div></div><div class="sect1" "></a>Common Errors</h2></div></div></div><p> 405 405 TCP/IP network configuration problems find every network administrator sooner or later. 406 406 The cause can be anything from keyboard mishaps to forgetfulness to simple mistakes to 407 407 carelessness. Of course, no one is ever deliberately careless! 408 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669616"></a>Pinging Works Only One Way</h3></div></div></div><p>409 “<span class="quote">I can ping my Samba server from Windows, but I cannot ping my Windows410 machine from the Samba server.</span>” 408 </p><div class="sect2" "></a>Pinging Works Only One Way</h3></div></div></div><p> 409 “<span class="quote">I can ping my Samba server from Windows, but I cannot ping my Windows 410 machine from the Samba server.</span>” 411 411 </p><p> 412 412 The Windows machine was at IP address 192.168.1.2 with netmask 255.255.255.0, the … … 416 416 Due to inconsistent netmasks, the Windows machine was on network 192.168.1.0/24, while 417 417 the Samba server was on network 192.168.1.128/25 logically a different network. 418 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669647"></a>Very Slow Network Connections</h3></div></div></div><p>418 </p></div><div class="sect2" "></a>Very Slow Network Connections</h3></div></div></div><p> 419 419 A common cause of slow network response includes: 420 </p><div class="itemizedlist"><ul type="disc"><li><p>Client is configured to use DNS and the DNS server is down.</p></li><li><p>Client is configured to use remote DNS server, but the421 remote connection is down.</p></li><li ><p>Client is configured to use a WINS server, but there is no WINS server.</p></li><li><p>Client is not configured to use a WINS server, but there is a WINS server.</p></li><li><p>Firewall is filtering out DNS or WINS traffic.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2669689"></a>Samba Server Name-Change Problem</h3></div></div></div><p>422 “<span class="quote">The name of the Samba server was changed, Samba was restarted, and now the Samba server cannot be420 </p><div class="itemizedlist"><ul ><p>Client is configured to use remote DNS server, but the 421 remote connection is down.</p></li><li"></a>Samba Server Name-Change Problem</h3></div></div></div><p> 422 “<span class="quote">The name of the Samba server was changed, Samba was restarted, and now the Samba server cannot be 423 423 pinged by its new name from an MS Windows NT4 workstation, but it does still respond to pinging using 424 the old name. Why?</span>” 424 the old name. Why?</span>” 425 425 </p><p> 426 426 From this description, three things are obvious: 427 </p><div class="itemizedlist"><ul type="disc"><li><p>WINS is not in use; only broadcast-based name resolution is used.</p></li><li><p>The Samba server was renamed and restarted within the last 10 or 15 minutes.</p></li><li><p>The old Samba server name is still in the NetBIOS name cache on the MS Windows NT4 workstation.</p></li></ul></div><p>427 </p><div class="itemizedlist"><ul ><p>The old Samba server name is still in the NetBIOS name cache on the MS Windows NT4 workstation.</p></li></ul></div><p> 428 428 To find what names are present in the NetBIOS name cache on the MS Windows NT4 machine, 429 429 open a <code class="literal">cmd</code> shell and then:
Note:
See TracChangeset
for help on using the changeset viewer.
