- Timestamp:
- Sep 30, 2008, 7:14:08 AM (17 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.0/docs/htmldocs/Samba3-HOWTO/integrate-ms-networks.html
r134 r158 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.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="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="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#id4 48624">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="integrate-ms-networks.html#id448641">Background Information</a></span></dt><dt><span class="sect1"><a href="integrate-ms-networks.html#id448760">Name Resolution in a Pure UNIX/Linux World</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id448831"><code class="filename">/etc/hosts</code></a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id448992"><code class="filename">/etc/resolv.conf</code></a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id449025"><code class="filename">/etc/host.conf</code></a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id449073"><code class="filename">/etc/nsswitch.conf</code></a></span></dt></dl></dd><dt><span class="sect1"><a href="integrate-ms-networks.html#id449183">Name Resolution as Used within MS Windows Networking</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id449576">The NetBIOS Name Cache</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id449659">The LMHOSTS File</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id449764">HOSTS File</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id449789">DNS Lookup</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id449811">WINS Lookup</a></span></dt></dl></dd><dt><span class="sect1"><a href="integrate-ms-networks.html#id449942">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id449953">Pinging Works Only One Way</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id449980">Very Slow Network Connections</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id450018">Samba Server Name-Change Problem</a></span></dt></dl></dd></dl></div><p>2 <a class="indexterm" name="id4 48587"></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.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="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="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#id4">Samba Server Name-Change Problem</a></span></dt></dl></dd></dl></div><p> 2 <a class="indexterm" name="id4"></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 … … 6 6 NetBIOS over TCP/IP, then this chapter may help you to resolve networking problems. 7 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="id4 48602"></a>9 <a class="indexterm" name="id4 48609"></a>8 <a class="indexterm" name="id4"></a> 9 <a class="indexterm" name="id4"></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="id4 48624"></a>Features and Benefits</h2></div></div></div><p>15 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id4"></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="id4 48641"></a>Background Information</h2></div></div></div><p>24 <a class="indexterm" name="id4 48648"></a>25 <a class="indexterm" name="id4 48655"></a>26 <a class="indexterm" name="id4 48662"></a>27 <a class="indexterm" name="id4 48669"></a>28 <a class="indexterm" name="id4 48676"></a>23 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id4"></a>Background Information</h2></div></div></div><p> 24 <a class="indexterm" name="id4"></a> 25 <a class="indexterm" name="id4"></a> 26 <a class="indexterm" name="id4"></a> 27 <a class="indexterm" name="id4"></a> 28 <a class="indexterm" name="id4"></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 … … 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="id4 48698"></a>40 <a class="indexterm" name="id4 48704"></a>41 <a class="indexterm" name="id4 48711"></a>42 <a class="indexterm" name="id4 48718"></a>43 <a class="indexterm" name="id4 48724"></a>44 <a class="indexterm" name="id4 48731"></a>39 <a class="indexterm" name="id4"></a> 40 <a class="indexterm" name="id4"></a> 41 <a class="indexterm" name="id4"></a> 42 <a class="indexterm" name="id4"></a> 43 <a class="indexterm" name="id4"></a> 44 <a class="indexterm" name="id4"></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="id4 48740"></a> dynamic DNS with Service Resource48 Records (SRV RR) and with Incremental Zone Transfers (IXFR). <a class="indexterm" name="id4 48750"></a>47 <a class="indexterm" name="id4"></a> dynamic DNS with Service Resource 48 Records (SRV RR) and with Incremental Zone Transfers (IXFR). <a class="indexterm" name="id4"></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="id4 48760"></a>Name Resolution in a Pure UNIX/Linux World</h2></div></div></div><p>51 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id4"></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="id4 48770"></a><a class="indexterm" name="id448776"></a><a class="indexterm" name="id448783"></a><a class="indexterm" name="id448790"></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="id448831"></a><code class="filename">/etc/hosts</code></h3></div></div></div><p>53 </p><a class="indexterm" name="id4"></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="id4 48853"></a>61 <a class="indexterm" name="id4 48860"></a>60 <a class="indexterm" name="id4"></a> 61 <a class="indexterm" name="id4"></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="id4 48876"></a>67 <a class="indexterm" name="id4 48883"></a>68 <a class="indexterm" name="id4 48890"></a>66 <a class="indexterm" name="id4"></a> 67 <a class="indexterm" name="id4"></a> 68 <a class="indexterm" name="id4"></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="id4 48906"></a>75 <a class="indexterm" name="id4"></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="id4 48929"></a>87 <a class="indexterm" name="id4"></a> 88 88 When a user or a process wants to communicate with another machine, 89 89 the protocol implementation ensures that the “<span class="quote">machine name</span>” or “<span class="quote">host … … 92 92 <code class="filename">/etc/hosts</code> is one such file. 93 93 </p><p> 94 <a class="indexterm" name="id4 48954"></a>94 <a class="indexterm" name="id4"></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="id4 48974"></a>102 <a class="indexterm" name="id4"></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="id4 48992"></a><code class="filename">/etc/resolv.conf</code></h3></div></div></div><p>110 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id4"></a><code class="filename">/etc/resolv.conf</code></h3></div></div></div><p> 111 111 This file tells the name resolution libraries: 112 112 </p><div class="itemizedlist"><ul type="disc"><li><p>The name of the domain to which the machine … … 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="id4 49025"></a><code class="filename">/etc/host.conf</code></h3></div></div></div><p>121 <a class="indexterm" name="id4 49036"></a>120 </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id4"></a><code class="filename">/etc/host.conf</code></h3></div></div></div><p> 121 <a class="indexterm" name="id4"></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="id4 49073"></a><code class="filename">/etc/nsswitch.conf</code></h3></div></div></div><p>131 <a class="indexterm" name="id4 49084"></a>130 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id4"></a><code class="filename">/etc/nsswitch.conf</code></h3></div></div></div><p> 131 <a class="indexterm" name="id4"></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="id4 49113"></a>164 <a class="indexterm" name="id4 49120"></a>165 <a class="indexterm" name="id4 49126"></a>166 <a class="indexterm" name="id4 49133"></a>167 <a class="indexterm" name="id4 49140"></a>163 <a class="indexterm" name="id4"></a> 164 <a class="indexterm" name="id4"></a> 165 <a class="indexterm" name="id4"></a> 166 <a class="indexterm" name="id4"></a> 167 <a class="indexterm" name="id4"></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 … … 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="id4 49183"></a>Name Resolution as Used within MS Windows Networking</h2></div></div></div><p>181 <a class="indexterm" name="id4 49191"></a>182 <a class="indexterm" name="id4 49198"></a>183 <a class="indexterm" name="id4 49204"></a>184 <a class="indexterm" name="id4 49211"></a>180 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id4"></a>Name Resolution as Used within MS Windows Networking</h2></div></div></div><p> 181 <a class="indexterm" name="id4"></a> 182 <a class="indexterm" name="id4"></a> 183 <a class="indexterm" name="id4"></a> 184 <a class="indexterm" name="id4"></a> 185 185 MS Windows networking is predicated on the name each machine is given. This name is known variously (and 186 186 inconsistently) as the “<span class="quote">computer name,</span>” “<span class="quote">machine name,</span>” “<span class="quote">networking … … 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="id4 49393"></a>198 <a class="indexterm" name="id4"></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="id4 49425"></a>206 <a class="indexterm" name="id4 49432"></a>207 <a class="indexterm" name="id4 49439"></a>205 <a class="indexterm" name="id4"></a> 206 <a class="indexterm" name="id4"></a> 207 <a class="indexterm" name="id4"></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="id4 49463"></a>220 <a class="indexterm" name="id4 49469"></a>219 <a class="indexterm" name="id4"></a> 220 <a class="indexterm" name="id4"></a> 221 221 The name “<span class="quote">workgroup</span>” or “<span class="quote">domain</span>” really can be confusing, since these 222 222 have the added significance of indicating what is the security … … 231 231 of a username and a matching password. 232 232 </p><p> 233 <a class="indexterm" name="id4 49496"></a>234 <a class="indexterm" name="id4 49503"></a>235 <a class="indexterm" name="id4 49512"></a>236 <a class="indexterm" name="id4 49521"></a>237 <a class="indexterm" name="id4 49531"></a>238 <a class="indexterm" name="id4 49540"></a>239 <a class="indexterm" name="id4 49546"></a>240 <a class="indexterm" name="id4 49553"></a>233 <a class="indexterm" name="id4"></a> 234 <a class="indexterm" name="id4"></a> 235 <a class="indexterm" name="id4"></a> 236 <a class="indexterm" name="id4"></a> 237 <a class="indexterm" name="id4"></a> 238 <a class="indexterm" name="id4"></a> 239 <a class="indexterm" name="id4"></a> 240 <a class="indexterm" name="id4"></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="id4 49576"></a>The NetBIOS Name Cache</h3></div></div></div><p>256 <a class="indexterm" name="id4 49584"></a>257 <a class="indexterm" name="id4 49591"></a>258 <a class="indexterm" name="id4 49598"></a>255 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id4"></a>The NetBIOS Name Cache</h3></div></div></div><p> 256 <a class="indexterm" name="id4"></a> 257 <a class="indexterm" name="id4"></a> 258 <a class="indexterm" name="id4"></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="id4 49609"></a>266 <a class="indexterm" name="id4"></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="id4 49626"></a>275 <a class="indexterm" name="id4 49633"></a>276 <a class="indexterm" name="id4 49640"></a>274 <a class="indexterm" name="id4"></a> 275 <a class="indexterm" name="id4"></a> 276 <a class="indexterm" name="id4"></a> 277 277 The MS Windows utility that allows examination of the NetBIOS 278 278 name cache is called “<span class="quote">nbtstat.</span>” 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="id4 49659"></a>The LMHOSTS File</h3></div></div></div><p>281 <a class="indexterm" name="id4 49667"></a>280 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id4"></a>The LMHOSTS File</h3></div></div></div><p> 281 <a class="indexterm" name="id4"></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="id4 49764"></a>HOSTS File</h3></div></div></div><p>366 </pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id4"></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="id4 49789"></a>DNS Lookup</h3></div></div></div><p>374 <a class="indexterm" name="id4 49796"></a>373 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id4"></a>DNS Lookup</h3></div></div></div><p> 374 <a class="indexterm" name="id4"></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="id4 49811"></a>WINS Lookup</h3></div></div></div><p>386 <a class="indexterm" name="id4 49818"></a>387 <a class="indexterm" name="id4 49825"></a>388 <a class="indexterm" name="id4 49835"></a>385 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id4"></a>WINS Lookup</h3></div></div></div><p> 386 <a class="indexterm" name="id4"></a> 387 <a class="indexterm" name="id4"></a> 388 <a class="indexterm" name="id4"></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="id4 49864"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr></table><p>397 <a class="indexterm" name="id4 49878"></a>396 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id4"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr></table><p> 397 <a class="indexterm" name="id4"></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="id4 49899"></a><em class="parameter"><code>wins support = No</code></em></td></tr><tr><td><a class="indexterm" name="id449910"></a><em class="parameter"><code>wins server = xxx.xxx.xxx.xxx</code></em></td></tr></table><p>400 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id4"></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="id4 49942"></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" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id4"></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="id4 49953"></a>Pinging Works Only One Way</h3></div></div></div><p>408 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id4"></a>Pinging Works Only One Way</h3></div></div></div><p> 409 409 “<span class="quote">I can ping my Samba server from Windows, but I cannot ping my Windows 410 410 machine from the Samba server.</span>” … … 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="id4 49980"></a>Very Slow Network Connections</h3></div></div></div><p>418 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id4"></a>Very Slow Network Connections</h3></div></div></div><p> 419 419 A common cause of slow network response includes: 420 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 the 421 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="id4 50018"></a>Samba Server Name-Change Problem</h3></div></div></div><p>421 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="id4"></a>Samba Server Name-Change Problem</h3></div></div></div><p> 422 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
Note:
See TracChangeset
for help on using the changeset viewer.
