diff options
| author | bubulle <bubulle@alioth.debian.org> | 2008-05-28 03:56:49 +0000 |
|---|---|---|
| committer | bubulle <bubulle@alioth.debian.org> | 2008-05-28 03:56:49 +0000 |
| commit | 0381e1741f55a5691275f8df62da9fcc8818db3d (patch) | |
| tree | 3424758d8df73604eca5d787a6cb50964da7f665 /docs/htmldocs/Samba3-HOWTO/integrate-ms-networks.html | |
| parent | bba625b04e0d12c2c03a345554d98b8575f4f380 (diff) | |
| download | samba-0381e1741f55a5691275f8df62da9fcc8818db3d.tar.gz | |
Load samba-3.2.0rc1 into branches/samba/upstream-3.2.upstream/3.2.0_rc1
git-svn-id: svn://svn.debian.org/svn/pkg-samba/branches/samba/upstream-3.2@1898 fc4039ab-9d04-0410-8cac-899223bdd6b0
Diffstat (limited to 'docs/htmldocs/Samba3-HOWTO/integrate-ms-networks.html')
| -rw-r--r-- | docs/htmldocs/Samba3-HOWTO/integrate-ms-networks.html | 170 |
1 files changed, 85 insertions, 85 deletions
diff --git a/docs/htmldocs/Samba3-HOWTO/integrate-ms-networks.html b/docs/htmldocs/Samba3-HOWTO/integrate-ms-networks.html index 1213067060..19b54204a2 100644 --- a/docs/htmldocs/Samba3-HOWTO/integrate-ms-networks.html +++ b/docs/htmldocs/Samba3-HOWTO/integrate-ms-networks.html @@ -1,18 +1,18 @@ -<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.72.0"><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 href="mailto:jht@samba.org">jht@samba.org</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#id432559">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="integrate-ms-networks.html#id432576">Background Information</a></span></dt><dt><span class="sect1"><a href="integrate-ms-networks.html#id432695">Name Resolution in a Pure UNIX/Linux World</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id432767"><code class="filename">/etc/hosts</code></a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id432923"><code class="filename">/etc/resolv.conf</code></a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id432956"><code class="filename">/etc/host.conf</code></a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id433004"><code class="filename">/etc/nsswitch.conf</code></a></span></dt></dl></dd><dt><span class="sect1"><a href="integrate-ms-networks.html#id433113">Name Resolution as Used within MS Windows Networking</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id433506">The NetBIOS Name Cache</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id433586">The LMHOSTS File</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id433711">HOSTS File</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id433736">DNS Lookup</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id433763">WINS Lookup</a></span></dt></dl></dd><dt><span class="sect1"><a href="integrate-ms-networks.html#id433898">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id433909">Pinging Works Only One Way</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id433936">Very Slow Network Connections</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id433974">Samba Server Name-Change Problem</a></span></dt></dl></dd></dl></div><p> -<a class="indexterm" name="id432523"></a> +<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.1"><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:jht@samba.org">jht@samba.org</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#id2690396">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="integrate-ms-networks.html#id2690416">Background Information</a></span></dt><dt><span class="sect1"><a href="integrate-ms-networks.html#id2690545">Name Resolution in a Pure UNIX/Linux World</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2690618"><code class="filename">/etc/hosts</code></a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2690807"><code class="filename">/etc/resolv.conf</code></a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2690843"><code class="filename">/etc/host.conf</code></a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2690894"><code class="filename">/etc/nsswitch.conf</code></a></span></dt></dl></dd><dt><span class="sect1"><a href="integrate-ms-networks.html#id2691018">Name Resolution as Used within MS Windows Networking</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2691452">The NetBIOS Name Cache</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2691545">The LMHOSTS File</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2691717">HOSTS File</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2691745">DNS Lookup</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2691772">WINS Lookup</a></span></dt></dl></dd><dt><span class="sect1"><a href="integrate-ms-networks.html#id2691910">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="integrate-ms-networks.html#id2691923">Pinging Works Only One Way</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2691954">Very Slow Network Connections</a></span></dt><dt><span class="sect2"><a href="integrate-ms-networks.html#id2691996">Samba Server Name-Change Problem</a></span></dt></dl></dd></dl></div><p> +<a class="indexterm" name="id2690354"></a> This chapter deals with NetBIOS over TCP/IP name to IP address resolution. If your MS Windows clients are not configured to use NetBIOS over TCP/IP, then this section does not apply to your installation. If your installation involves the use of NetBIOS over TCP/IP, then this chapter may help you to resolve networking problems. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -<a class="indexterm" name="id432538"></a> -<a class="indexterm" name="id432544"></a> +<a class="indexterm" name="id2690372"></a> +<a class="indexterm" name="id2690378"></a> NetBIOS over TCP/IP has nothing to do with NetBEUI. NetBEUI is NetBIOS over Logical Link Control (LLC). On modern networks it is highly advised to not run NetBEUI at all. Note also that there is no such thing as NetBEUI over TCP/IP the existence of such a protocol is a complete and utter misapprehension. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id432559"></a>Features and Benefits</h2></div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690396"></a>Features and Benefits</h2></div></div></div><p> Many MS Windows network administrators have never been exposed to basic TCP/IP networking as it is implemented in a UNIX/Linux operating system. Likewise, many UNIX and Linux administrators have not been exposed to the intricacies of MS Windows TCP/IP-based @@ -20,12 +20,12 @@ networking (and may have no desire to be, either). </p><p> This chapter gives a short introduction to the basics of how a name can be resolved to its IP address for each operating system environment. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id432576"></a>Background Information</h2></div></div></div><p> -<a class="indexterm" name="id432584"></a> -<a class="indexterm" name="id432590"></a> -<a class="indexterm" name="id432597"></a> -<a class="indexterm" name="id432604"></a> -<a class="indexterm" name="id432611"></a> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690416"></a>Background Information</h2></div></div></div><p> +<a class="indexterm" name="id2690424"></a> +<a class="indexterm" name="id2690431"></a> +<a class="indexterm" name="id2690438"></a> +<a class="indexterm" name="id2690445"></a> +<a class="indexterm" name="id2690452"></a> Since the introduction of MS Windows 2000, it is possible to run MS Windows networking without the use of NetBIOS over TCP/IP. NetBIOS over TCP/IP uses UDP port 137 for NetBIOS name resolution and uses TCP port 139 for NetBIOS session services. When NetBIOS over @@ -36,43 +36,43 @@ When using Windows 2000 or later clients, if NetBIOS over TCP/IP is not disabled the client will use UDP port 137 (NetBIOS Name Service, also known as the Windows Internet Name Service, or WINS), TCP port 139, and TCP port 445 (for actual file and print traffic). </p></div><p> -<a class="indexterm" name="id432633"></a> -<a class="indexterm" name="id432640"></a> -<a class="indexterm" name="id432646"></a> -<a class="indexterm" name="id432653"></a> -<a class="indexterm" name="id432660"></a> -<a class="indexterm" name="id432667"></a> +<a class="indexterm" name="id2690480"></a> +<a class="indexterm" name="id2690486"></a> +<a class="indexterm" name="id2690493"></a> +<a class="indexterm" name="id2690500"></a> +<a class="indexterm" name="id2690506"></a> +<a class="indexterm" name="id2690513"></a> When NetBIOS over TCP/IP is disabled, the use of DNS is essential. Most installations that disable NetBIOS over TCP/IP today use MS Active Directory Service (ADS). ADS requires -<a class="indexterm" name="id432675"></a> dynamic DNS with Service Resource -Records (SRV RR) and with Incremental Zone Transfers (IXFR). <a class="indexterm" name="id432685"></a> +<a class="indexterm" name="id2690523"></a> dynamic DNS with Service Resource +Records (SRV RR) and with Incremental Zone Transfers (IXFR). <a class="indexterm" name="id2690534"></a> Use of DHCP with ADS is recommended as a further means of maintaining central control over the client workstation network configuration. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id432695"></a>Name Resolution in a Pure UNIX/Linux World</h2></div></div></div><p> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690545"></a>Name Resolution in a Pure UNIX/Linux World</h2></div></div></div><p> The key configuration files covered in this section are: -</p><a class="indexterm" name="id432705"></a><a class="indexterm" name="id432712"></a><a class="indexterm" name="id432718"></a><a class="indexterm" name="id432725"></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="id432767"></a><code class="filename">/etc/hosts</code></h3></div></div></div><p> +</p><a class="indexterm" name="id2690556"></a><a class="indexterm" name="id2690562"></a><a class="indexterm" name="id2690569"></a><a class="indexterm" name="id2690576"></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="id2690618"></a><code class="filename">/etc/hosts</code></h3></div></div></div><p> This file contains a static list of IP addresses and names. </p><pre class="programlisting"> 127.0.0.1 localhost localhost.localdomain 192.168.1.1 bigbox.quenya.org bigbox alias4box </pre><p> </p><p> -<a class="indexterm" name="id432788"></a> -<a class="indexterm" name="id432795"></a> +<a class="indexterm" name="id2690641"></a> +<a class="indexterm" name="id2690648"></a> The purpose of <code class="filename">/etc/hosts</code> is to provide a name resolution mechanism so users do not need to remember IP addresses. </p><p> -<a class="indexterm" name="id432812"></a> -<a class="indexterm" name="id432819"></a> -<a class="indexterm" name="id432825"></a> +<a class="indexterm" name="id2690666"></a> +<a class="indexterm" name="id2690673"></a> +<a class="indexterm" name="id2690680"></a> Network packets that are sent over the physical network transport layer communicate not via IP addresses but rather using the Media Access Control address, or MAC address. IP addresses are currently 32 bits in length and are typically presented as four decimal numbers that are separated by a dot (or period) for example, 168.192.1.1. </p><p> -<a class="indexterm" name="id432842"></a> +<a class="indexterm" name="id2690698"></a> MAC addresses use 48 bits (or 6 bytes) and are typically represented as two-digit hexadecimal numbers separated by colons: 40:8e:0a:12:34:56. </p><p> @@ -84,14 +84,14 @@ interface, the assignment of an IP address makes sense from a network management address can be assigned per MAC address. One address must be the primary IP address this is the address that will be returned in the Address Resolution Protocol (ARP) reply. </p><p> -<a class="indexterm" name="id432864"></a> +<a class="indexterm" name="id2690729"></a> When a user or a process wants to communicate with another machine, the protocol implementation ensures that the “<span class="quote">machine name</span>” or “<span class="quote">host name</span>” is resolved to an IP address in a manner that is controlled by the TCP/IP configuration control files. The file <code class="filename">/etc/hosts</code> is one such file. </p><p> -<a class="indexterm" name="id432890"></a> +<a class="indexterm" name="id2690756"></a> When the IP address of the destination interface has been determined, a protocol called ARP/RARP is used to identify the MAC address of the target interface. ARP is a broadcast-oriented method that uses User Datagram Protocol (UDP) to send a request to all interfaces on the local network segment using the all 1s MAC address. @@ -99,7 +99,7 @@ Network interfaces are programmed to respond to two MAC addresses only; their ow address ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will contain the MAC address and the primary IP address for each interface. </p><p> -<a class="indexterm" name="id432904"></a> +<a class="indexterm" name="id2690786"></a> The <code class="filename">/etc/hosts</code> file is foundational to all UNIX/Linux TCP/IP installations and as a minimum will contain the localhost and local network interface IP addresses and the @@ -107,7 +107,7 @@ primary names by which they are known within the local machine. This file helps to prime the pump so a basic level of name resolution can exist before any other method of name resolution becomes available. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id432923"></a><code class="filename">/etc/resolv.conf</code></h3></div></div></div><p> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2690807"></a><code class="filename">/etc/resolv.conf</code></h3></div></div></div><p> This file tells the name resolution libraries: </p><div class="itemizedlist"><ul type="disc"><li><p>The name of the domain to which the machine belongs. @@ -117,8 +117,8 @@ This file tells the name resolution libraries: </p></li><li><p>The name or IP address of available domain name servers that may be asked to perform name-to-address translation lookups. - </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id432956"></a><code class="filename">/etc/host.conf</code></h3></div></div></div><p> -<a class="indexterm" name="id432967"></a> + </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2690843"></a><code class="filename">/etc/host.conf</code></h3></div></div></div><p> +<a class="indexterm" name="id2690854"></a> <code class="filename">/etc/host.conf</code> is the primary means by which the setting in <code class="filename">/etc/resolv.conf</code> may be effected. It is a critical configuration file. This file controls the order by which name resolution may proceed. The typical structure is: @@ -127,8 +127,8 @@ order hosts,bind multi on </pre><p>Both addresses should be returned. Please refer to the man page for <code class="filename">host.conf</code> for further details. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id433004"></a><code class="filename">/etc/nsswitch.conf</code></h3></div></div></div><p> -<a class="indexterm" name="id433015"></a> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2690894"></a><code class="filename">/etc/nsswitch.conf</code></h3></div></div></div><p> +<a class="indexterm" name="id2690905"></a> This file controls the actual name resolution targets. The file typically has resolver object specifications as follows: </p><pre class="programlisting"> @@ -160,11 +160,11 @@ It should be noted that unless a network request/message must be sent, TCP/IP networks are silent. All TCP/IP communications assume a principal of speaking only when necessary. </p><p> -<a class="indexterm" name="id433043"></a> -<a class="indexterm" name="id433050"></a> -<a class="indexterm" name="id433057"></a> -<a class="indexterm" name="id433064"></a> -<a class="indexterm" name="id433070"></a> +<a class="indexterm" name="id2690941"></a> +<a class="indexterm" name="id2690948"></a> +<a class="indexterm" name="id2690955"></a> +<a class="indexterm" name="id2690962"></a> +<a class="indexterm" name="id2690969"></a> Starting with version 2.2.0, Samba has Linux support for extensions to the name service switch infrastructure so Linux clients will be able to obtain resolution of MS Windows NetBIOS names to IP @@ -177,11 +177,11 @@ the <code class="filename">/etc/nsswitch.conf</code> file. At this point, it will be possible to ping any MS Windows machine by its NetBIOS machine name, as long as that machine is within the workgroup to which both the Samba machine and the MS Windows machine belong. -</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id433113"></a>Name Resolution as Used within MS Windows Networking</h2></div></div></div><p> -<a class="indexterm" name="id433121"></a> -<a class="indexterm" name="id433128"></a> -<a class="indexterm" name="id433135"></a> -<a class="indexterm" name="id433142"></a> +</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2691018"></a>Name Resolution as Used within MS Windows Networking</h2></div></div></div><p> +<a class="indexterm" name="id2691027"></a> +<a class="indexterm" name="id2691034"></a> +<a class="indexterm" name="id2691040"></a> +<a class="indexterm" name="id2691047"></a> MS Windows networking is predicated on the name each machine is given. This name is known variously (and inconsistently) as the “<span class="quote">computer name,</span>” “<span class="quote">machine name,</span>” “<span class="quote">networking name,</span>” “<span class="quote">NetBIOS name,</span>” or “<span class="quote">SMB name.</span>” All terms mean the same thing with the @@ -192,19 +192,19 @@ the machine is associated. All NetBIOS names are exactly 16 characters in length service level information for the NetBIOS name that is registered. A NetBIOS machine name is therefore registered for each service type that is provided by the client/server. </p><p> -<a href="integrate-ms-networks.html#uniqnetbiosnames" title="Table 29.1. Unique NetBIOS Names">Unique NetBIOS names</a> and <a href="integrate-ms-networks.html#netbiosnamesgrp" title="Table 29.2. Group Names">group names</a> tables +<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> tables list typical NetBIOS name/service type registrations. </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> -<a class="indexterm" name="id433323"></a> +<a class="indexterm" name="id2691243"></a> It should be noted that all NetBIOS machines register their own -names as per <a href="integrate-ms-networks.html#uniqnetbiosnames" title="Table 29.1. Unique NetBIOS Names">Unique NetBIOS names</a> and <a href="integrate-ms-networks.html#netbiosnamesgrp" title="Table 29.2. Group Names">group names</a>. This is in vast contrast to TCP/IP +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 installations where the system administrator traditionally determines in the <code class="filename">/etc/hosts</code> or in the DNS database what names are associated with each IP address. </p><p> -<a class="indexterm" name="id433355"></a> -<a class="indexterm" name="id433362"></a> -<a class="indexterm" name="id433369"></a> +<a class="indexterm" name="id2691278"></a> +<a class="indexterm" name="id2691285"></a> +<a class="indexterm" name="id2691292"></a> One further point of clarification should be noted. The <code class="filename">/etc/hosts</code> file and the DNS records do not provide the NetBIOS name information that MS Windows clients depend on to locate the type of service that may @@ -216,8 +216,8 @@ registered the name type *<1C>. A logon request is then sent to each IP address that is returned in the enumerated list of IP addresses. Whichever machine first replies, it then ends up providing the logon services. </p><p> -<a class="indexterm" name="id433393"></a> -<a class="indexterm" name="id433399"></a> +<a class="indexterm" name="id2691324"></a> +<a class="indexterm" name="id2691330"></a> The name “<span class="quote">workgroup</span>” or “<span class="quote">domain</span>” really can be confusing, since these have the added significance of indicating what is the security architecture of the MS Windows network. The term “<span class="quote">workgroup</span>” indicates @@ -230,14 +230,14 @@ will simply opt to have no security at all. It is possible to have user-level security in a workgroup environment, thus requiring the use of a username and a matching password. </p><p> -<a class="indexterm" name="id433426"></a> -<a class="indexterm" name="id433433"></a> -<a class="indexterm" name="id433442"></a> -<a class="indexterm" name="id433451"></a> -<a class="indexterm" name="id433461"></a> -<a class="indexterm" name="id433470"></a> -<a class="indexterm" name="id433476"></a> -<a class="indexterm" name="id433483"></a> +<a class="indexterm" name="id2691363"></a> +<a class="indexterm" name="id2691370"></a> +<a class="indexterm" name="id2691379"></a> +<a class="indexterm" name="id2691389"></a> +<a class="indexterm" name="id2691398"></a> +<a class="indexterm" name="id2691408"></a> +<a class="indexterm" name="id2691414"></a> +<a class="indexterm" name="id2691421"></a> MS Windows networking is thus predetermined to use machine names for all local and remote machine message passing. The protocol used is called Server Message Block (SMB), and this is implemented using @@ -252,10 +252,10 @@ NBT or NetBT, the NetBIOS over TCP/IP. MS Windows machines use a complex array of name resolution mechanisms. Since we are primarily concerned with TCP/IP, this demonstration is limited to this area. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id433506"></a>The NetBIOS Name Cache</h3></div></div></div><p> -<a class="indexterm" name="id433514"></a> -<a class="indexterm" name="id433521"></a> -<a class="indexterm" name="id433528"></a> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2691452"></a>The NetBIOS Name Cache</h3></div></div></div><p> +<a class="indexterm" name="id2691460"></a> +<a class="indexterm" name="id2691467"></a> +<a class="indexterm" name="id2691473"></a> All MS Windows machines employ an in-memory buffer in which is stored the NetBIOS names and IP addresses for all external machines that machine has communicated with over the @@ -263,7 +263,7 @@ past 10 to 15 minutes. It is more efficient to obtain an IP address for a machine from the local cache than it is to go through all the configured name resolution mechanisms. </p><p> -<a class="indexterm" name="id433539"></a> +<a class="indexterm" name="id2691488"></a> If a machine whose name is in the local name cache is shut down before the name is expired and flushed from the cache, then an attempt to exchange a message with that machine will be subject @@ -271,14 +271,14 @@ to timeout delays. Its name is in the cache, so a name resolution lookup will succeed, but the machine cannot respond. This can be frustrating for users but is a characteristic of the protocol. </p><p> -<a class="indexterm" name="id433553"></a> -<a class="indexterm" name="id433560"></a> -<a class="indexterm" name="id433566"></a> +<a class="indexterm" name="id2691511"></a> +<a class="indexterm" name="id2691518"></a> +<a class="indexterm" name="id2691525"></a> The MS Windows utility that allows examination of the NetBIOS name cache is called “<span class="quote">nbtstat.</span>” The Samba equivalent is called <code class="literal">nmblookup</code>. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id433586"></a>The LMHOSTS File</h3></div></div></div><p> -<a class="indexterm" name="id433593"></a> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2691545"></a>The LMHOSTS File</h3></div></div></div><p> +<a class="indexterm" name="id2691553"></a> This file is usually located in MS Windows NT 4.0 or Windows 200x/XP in the directory <code class="filename">%SystemRoot%\SYSTEM32\DRIVERS\ETC</code> and contains the IP address and the machine name in matched pairs. The <code class="filename">LMHOSTS</code> file @@ -363,15 +363,15 @@ It typically looks like this: # so keeping the number of comments to a minimum will improve performance. # Therefore it is not advisable to simply add lmhosts file entries onto the # end of this file. -</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id433711"></a>HOSTS File</h3></div></div></div><p> +</pre></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2691717"></a>HOSTS File</h3></div></div></div><p> This file is usually located in MS Windows NT 4.0 or Windows 200x/XP in the directory <code class="filename">%SystemRoot%\SYSTEM32\DRIVERS\ETC</code> and contains the IP address and the IP hostname in matched pairs. It can be used by the name resolution infrastructure in MS Windows, depending on how the TCP/IP environment is configured. This file is in every way the equivalent of the UNIX/Linux <code class="filename">/etc/hosts</code> file. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id433736"></a>DNS Lookup</h3></div></div></div><p> -<a class="indexterm" name="id433744"></a> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2691745"></a>DNS Lookup</h3></div></div></div><p> +<a class="indexterm" name="id2691753"></a> This capability is configured in the TCP/IP setup area in the network configuration facility. If enabled, an elaborate name resolution sequence is followed, the precise nature of which is dependent on how the NetBIOS @@ -382,10 +382,10 @@ cache. If that fails, then DNS, HOSTS, and LMHOSTS are checked. If set to Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the WINS server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast lookup is used. -</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id433763"></a>WINS Lookup</h3></div></div></div><p> -<a class="indexterm" name="id433771"></a> -<a class="indexterm" name="id433778"></a> -<a class="indexterm" name="id433787"></a> +</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2691772"></a>WINS Lookup</h3></div></div></div><p> +<a class="indexterm" name="id2691780"></a> +<a class="indexterm" name="id2691787"></a> +<a class="indexterm" name="id2691796"></a> A WINS (Windows Internet Name Server) service is the equivalent of the rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores the names and IP addresses that are registered by a Windows client @@ -393,19 +393,19 @@ if the TCP/IP setup has been given at least one WINS server IP address. </p><p> To configure Samba to be a WINS server, the following parameter needs to be added to the <code class="filename">smb.conf</code> file: -</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id433817"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr></table><p> -<a class="indexterm" name="id433831"></a> +</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2691829"></a><em class="parameter"><code>wins support = Yes</code></em></td></tr></table><p> +<a class="indexterm" name="id2691843"></a> To configure Samba to use a WINS server, the following parameters are needed in the <code class="filename">smb.conf</code> file: -</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id433853"></a><em class="parameter"><code>wins support = No</code></em></td></tr><tr><td><a class="indexterm" name="id433865"></a><em class="parameter"><code>wins server = xxx.xxx.xxx.xxx</code></em></td></tr></table><p> +</p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2691865"></a><em class="parameter"><code>wins support = No</code></em></td></tr><tr><td><a class="indexterm" name="id2691877"></a><em class="parameter"><code>wins server = xxx.xxx.xxx.xxx</code></em></td></tr></table><p> where <em class="replaceable"><code>xxx.xxx.xxx.xxx</code></em> is the IP address of the WINS server. </p><p>For information about setting up Samba as a WINS server, read -<a 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="id433898"></a>Common Errors</h2></div></div></div><p> +<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="id2691910"></a>Common Errors</h2></div></div></div><p> TCP/IP network configuration problems find every network administrator sooner or later. The cause can be anything from keyboard mishaps to forgetfulness to simple mistakes to carelessness. Of course, no one is ever deliberately careless! -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id433909"></a>Pinging Works Only One Way</h3></div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2691923"></a>Pinging Works Only One Way</h3></div></div></div><p> “<span class="quote">I can ping my Samba server from Windows, but I cannot ping my Windows machine from the Samba server.</span>” </p><p> @@ -415,10 +415,10 @@ carelessness. Of course, no one is ever deliberately careless! </p><p> Due to inconsistent netmasks, the Windows machine was on network 192.168.1.0/24, while the Samba server was on network 192.168.1.128/25 logically a different network. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id433936"></a>Very Slow Network Connections</h3></div></div></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2691954"></a>Very Slow Network Connections</h3></div></div></div><p> A common cause of slow network response includes: </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 - 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="id433974"></a>Samba Server Name-Change Problem</h3></div></div></div><p> + 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="id2691996"></a>Samba Server Name-Change Problem</h3></div></div></div><p> “<span class="quote">The name of the Samba server was changed, Samba was restarted, and now the Samba server cannot be pinged by its new name from an MS Windows NT4 workstation, but it does still respond to pinging using the old name. Why?</span>” |