-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 16. Networking Primer</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="RefSection.html" title="Part III. Reference Section"><link rel="prev" href="appendix.html" title="Chapter 15. A Collection of Useful Tidbits"><link rel="next" href="apa.html" title="Appendix A. GNU General Public License version 3"></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 16. Networking Primer</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="appendix.html">Prev</a> </td><th width="60%" align="center">Part III. Reference Section</th><td width="20%" align="right"> <a accesskey="n" href="apa.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="primer"></a>Chapter 16. Networking Primer</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="primer.html#id26254
30">Requirements and Notes</a></span></dt><dt><span class="sect1"><a href="primer.html#id2625592">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2625652">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#id2625769">Exercises</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2625894">Single-Machine Broadcast Activity</a></span></dt><dt><span class="sect2"><a href="primer.html#secondmachine">Second Machine Startup Broadcast Interaction</a></span></dt><dt><span class="sect2"><a href="primer.html#id2627042">Simple Windows Client Connection Characteristics</a></span></dt><dt><span class="sect2"><a href="primer.html#id2627544">Windows 200x/XP Client Interaction with Samba-3</a></span></dt><dt><span class="sect2"><a href="primer.html#id2628113">Conclusions to Exercises</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#chap01conc">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2628227">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#chap01qa">Questions and Answers</a></span></dt></dl></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 16. Networking Primer</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Samba-3 by Example"><link rel="up" href="RefSection.html" title="Part III. Reference Section"><link rel="prev" href="appendix.html" title="Chapter 15. A Collection of Useful Tidbits"><link rel="next" href="apa.html" title="Appendix A. GNU General Public License version 3"></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 16. Networking Primer</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="appendix.html">Prev</a> </td><th width="60%" align="center">Part III. Reference Section</th><td width="20%" align="right"> <a accesskey="n" href="apa.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="primer"></a>Chapter 16. Networking Primer</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="primer.html#id26254
07">Requirements and Notes</a></span></dt><dt><span class="sect1"><a href="primer.html#id2625568">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2625629">Assignment Tasks</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#id2625745">Exercises</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2625871">Single-Machine Broadcast Activity</a></span></dt><dt><span class="sect2"><a href="primer.html#secondmachine">Second Machine Startup Broadcast Interaction</a></span></dt><dt><span class="sect2"><a href="primer.html#id2627019">Simple Windows Client Connection Characteristics</a></span></dt><dt><span class="sect2"><a href="primer.html#id2627521">Windows 200x/XP Client Interaction with Samba-3</a></span></dt><dt><span class="sect2"><a href="primer.html#id2628089">Conclusions to Exercises</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#chap01conc">Dissection and Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="primer.html#id2628204">Technical Issues</a></span></dt></dl></dd><dt><span class="sect1"><a href="primer.html#chap01qa">Questions and Answers</a></span></dt></dl></div><p>
You are about to use the equivalent of a microscope to look at the information
that runs through the veins of a Windows network. We do more to observe the information than
to interrogate it. When you are done with this primer, you should have a good understanding
</p><p>
Samba can be configured with a minimum of complexity. Simplicity should be mastered
before you get too deeply into complexities. Let's get moving: we have work to do.
- </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id26254
30"></a>Requirements and Notes</h2></div></div></div><p>
+ </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id26254
07"></a>Requirements and Notes</h2></div></div></div><p>
Successful completion of this primer requires two Microsoft Windows 9x/Me Workstations
as well as two Microsoft Windows XP Professional Workstations, each equipped with an Ethernet
card connected using a hub. Also required is one additional server (either Windows
sniffer and analysis application (Wireshark is a good choice). All work should be undertaken
on a quiet network where there is no other traffic. It is best to use a dedicated hub
with only the machines under test connected at the time of the exercises.
- </p><p><a class="indexterm" name="id2625451"></a>
+ </p><p><a class="indexterm" name="id2625428"></a>
Wireshark (formerly Ethereal) has become the network protocol analyzer of choice for many network administrators.
You may find more information regarding this tool from the
<a class="ulink" href="http://www.wireshark.org" target="_top">Wireshark</a> Web site. Wireshark installation
filter. Ethernet switches may filter out traffic that is not directed at the machine
that is used to monitor traffic; this would not allow you to complete the projects.
</p></div><p>
- <a class="indexterm" name="id2625520"></a>
+ <a class="indexterm" name="id2625497"></a>
Do not worry too much if you do not have access to all this equipment; network captures
from the exercises are provided on the enclosed CD-ROM. This makes it possible to dive directly
into the analytical part of the exercises if you so desire.
- </p><p><a class="indexterm" name="id2625536"></a><a class="indexterm" name="id2625547"></a>
+ </p><p><a class="indexterm" name="id2625513"></a><a class="indexterm" name="id2625524"></a>
Please do not be alarmed at the use of a high-powered analysis tool (Wireshark) in this
primer. We expose you only to a minimum of detail necessary to complete
the exercises. If you choose to use any other network sniffer and protocol
</p><p>
<a class="link" href="primer.html#chap01qa" title="Questions and Answers">“Questions and Answers”</a> also provides useful information
that may help you to avoid significantly time-consuming networking problems.
- </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id26255
92"></a>Introduction</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="id26255
68"></a>Introduction</h2></div></div></div><p>
The purpose of this chapter is to create familiarity with key aspects of Microsoft Windows
network computing. If you want a solid technical grounding, do not gloss over these exercises.
The points covered are recurrent issues on the Samba mailing lists.
- </p><p><a class="indexterm" name="id2625606"></a>
+ </p><p><a class="indexterm" name="id2625583"></a>
You can see from these exercises that Windows networking involves quite a lot of network
broadcast traffic. You can look into the contents of some packets, but only to see
some particular information that the Windows client sends to a server in the course of
Recommended preparatory reading: <span class="emphasis"><em>The Official Samba-3 HOWTO and Reference Guide, Second
Edition</em></span> (TOSHARG2) Chapter 9, “<span class="quote">Network Browsing,</span>” and Chapter 3,
“<span class="quote">Server Types and Security Modes.</span>”
- </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2625652"></a>Assignment Tasks</h3></div></div></div><p><a class="indexterm" name="id2625659"></a>
+ </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2625629"></a>Assignment Tasks</h3></div></div></div><p><a class="indexterm" name="id2625636"></a>
You are about to witness how Microsoft Windows computer networking functions. The
exercises step through identification of how a client machine establishes a
connection to a remote Windows server. You observe how Windows machines find
each other (i.e., how browsing works) and how the two key types of user identification
(share mode security and user mode security) are affected.
- </p><p><a class="indexterm" name="id2625676"></a>
+ </p><p><a class="indexterm" name="id2625653"></a>
The networking protocols used by MS Windows networking when working with Samba
use TCP/IP as the transport protocol. The protocols that are specific to Windows
networking are encapsulated in TCP/IP. The network analyzer we use (Wireshark)
is able to show you the contents of the TCP/IP packets (or messages).
- </p><div class="procedure"><a name="chap01tasks"></a><p class="title"><b>Procedure 16.1. Diagnostic Tasks</b></p><ol type="1"><li><p><a class="indexterm" name="id2625709"></a><a class="indexterm" name="id2625720"></a><a class="indexterm" name="id2625728"></a>
+ </p><div class="procedure"><a name="chap01tasks"></a><p class="title"><b>Procedure 16.1. Diagnostic Tasks</b></p><ol type="1"><li><p><a class="indexterm" name="id2625686"></a><a class="indexterm" name="id2625697"></a><a class="indexterm" name="id2625705"></a>
Examine network traces to witness SMB broadcasts, host announcements,
and name resolution processes.
</p></li><li><p>
</p></li><li><p>
Review traces of network logons for a Windows 9x/Me client as well as
a domain logon for a Windows XP Professional client.
- </p></li></ol></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id26257
69"></a>Exercises</h2></div></div></div><p>
- <a class="indexterm" name="id2625776"></a>
+ </p></li></ol></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id26257
45"></a>Exercises</h2></div></div></div><p>
+ <a class="indexterm" name="id2625753"></a>
You are embarking on a course of discovery. The first part of the exercise requires
two MS Windows 9x/Me systems. We called one machine <code class="constant">WINEPRESSME</code> and the
other <code class="constant">MILGATE98</code>. Each needs an IP address; we used <code class="literal">10.1.1.10</code>
</p><div class="itemizedlist"><ul type="disc"><li><p>Windows 98 name: MILGATE98</p></li><li><p>Windows Me name: WINEPRESSME</p></li><li><p>Windows XP Professional name: LightrayXP</p></li><li><p>Samba-3.0.20 running on a SUSE Enterprise Linux 9</p></li></ul></div><p>
Choose a workgroup name (MIDEARTH) for each exercise.
</p><p>
- <a class="indexterm" name="id2625866"></a>
+ <a class="indexterm" name="id2625842"></a>
The network captures provided on the CD-ROM included with this book were captured using <code class="constant">Ethereal</code>
version <code class="literal">0.10.6</code>. A later version suffices without problems (i.e. you should be using Wireshark), but an earlier version may not
expose all the information needed. Each capture file has been decoded and listed as a trace file. A summary of all
perform the time-consuming equipment configuration and test work. This is a good time to point out that the value
that can be derived from this book really does warrant your taking sufficient time to practice each exercise with
care and attention to detail.
- </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26258
94"></a>Single-Machine Broadcast Activity</h3></div></div></div><p>
+ </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26258
71"></a>Single-Machine Broadcast Activity</h3></div></div></div><p>
In this section, we start a single Windows 9x/Me machine, then monitor network activity for 30 minutes.
- </p><div class="procedure"><a name="id2625
906"></a><p class="title"><b>Procedure 16.2. Monitoring Windows 9x Steps</b></p><ol type="1"><li><p>
+ </p><div class="procedure"><a name="id2625
882"></a><p class="title"><b>Procedure 16.2. Monitoring Windows 9x Steps</b></p><ol type="1"><li><p>
Start the machine from which network activity will be monitored (using <code class="literal">Wireshark</code>).
Launch <code class="literal">Wireshark</code>, click
<span class="guimenu">Capture</span> → <span class="guimenuitem">Start</span>.
</p></li><li><p>
Analyze the capture. Identify each discrete message type that was captured. Note what transport protocol
was used. Identify the timing between messages of identical types.
- </p></li></ol></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id26260
28"></a>Findings</h4></div></div></div><p>
+ </p></li></ol></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id26260
05"></a>Findings</h4></div></div></div><p>
The summary of the first 10 minutes of the packet capture should look like <a class="link" href="primer.html#pktcap01" title="Figure 16.1. Windows Me Broadcasts The First 10 Minutes">“Windows Me Broadcasts The First 10 Minutes”</a>.
A screenshot of a later stage of the same capture is shown in <a class="link" href="primer.html#pktcap02" title="Figure 16.2. Windows Me Later Broadcast Sample">“Windows Me Later Broadcast Sample”</a>.
- </p><div class="figure"><a name="pktcap01"></a><p class="title"><b>Figure 16.1. Windows Me Broadcasts The First 10 Minutes</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WINREPRESSME-Capture.png" width="216" alt="Windows Me Broadcasts The First 10 Minutes"></div></div></div><br class="figure-break"><div class="figure"><a name="pktcap02"></a><p class="title"><b>Figure 16.2. Windows Me Later Broadcast Sample</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WINREPRESSME-Capture2.png" width="226.8" alt="Windows Me Later Broadcast Sample"></div></div></div><br class="figure-break"><p><a class="indexterm" name="id2626145"></a><a class="indexterm" name="id2626157"></a>
+ </p><div class="figure"><a name="pktcap01"></a><p class="title"><b>Figure 16.1. Windows Me Broadcasts The First 10 Minutes</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WINREPRESSME-Capture.png" width="216" alt="Windows Me Broadcasts The First 10 Minutes"></div></div></div><br class="figure-break"><div class="figure"><a name="pktcap02"></a><p class="title"><b>Figure 16.2. Windows Me Later Broadcast Sample</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WINREPRESSME-Capture2.png" width="226.8" alt="Windows Me Later Broadcast Sample"></div></div></div><br class="figure-break"><p><a class="indexterm" name="id2626122"></a><a class="indexterm" name="id2626134"></a>
Broadcast messages observed are shown in <a class="link" href="primer.html#capsstats01" title="Table 16.1. Windows Me Startup Broadcast Capture Statistics">“Windows Me Startup Broadcast Capture Statistics”</a>.
Actual observations vary a little, but not by much.
Early in the startup process, the Windows Me machine broadcasts its name for two reasons:
first to ensure that its name would not result in a name clash, and second to establish its
presence with the Local Master Browser (LMB).
- </p><div class="table"><a name="capsstats01"></a><p class="title"><b>Table 16.1. Windows Me Startup Broadcast Capture Statistics</b></p><div class="table-contents"><table summary="Windows Me Startup Broadcast Capture Statistics" border="1"><colgroup><col align="left"><col align="center"><col align="center"><col align="left"></colgroup><thead><tr><th align="left">Message</th><th align="center">Type</th><th align="center">Num</th><th align="left">Notes</th></tr></thead><tbody><tr><td align="left">WINEPRESSME<00></td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.6 sec apart</td></tr><tr><td align="left">WINEPRESSME<03></td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.6 sec apart</td></tr><tr><td align="left">WINEPRESSME<20></td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH<00></td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH<1d></td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH<1e></td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH<1b></td><td align="center">Qry</td><td align="center">84</td><td align="left">300 sec apart at stable operation</td></tr><tr><td align="left">__MSBROWSE__</td><td align="center">Reg</td><td align="center">8</td><td align="left">Registered after winning election to Browse Master</td></tr><tr><td align="left">JHT<03></td><td align="center">Reg</td><td align="center">8</td><td align="left">4 x 2. This is the name of the user that logged onto Windows</td></tr><tr><td align="left">Host Announcement WINEPRESSME</td><td align="center">Ann</td><td align="center">2</td><td align="left">Observed at 10 sec</td></tr><tr><td align="left">Domain/Workgroup Announcement MIDEARTH</td><td align="center">Ann</td><td align="center">18</td><td align="left">300 sec apart at stable operation</td></tr><tr><td align="left">Local Master Announcement WINEPRESSME</td><td align="center">Ann</td><td align="center">18</td><td align="left">300 sec apart at stable operation</td></tr><tr><td align="left">Get Backup List Request</td><td align="center">Qry</td><td align="center">12</td><td align="left">6 x 2 early in startup, 0.5 sec apart</td></tr><tr><td align="left">Browser Election Request</td><td align="center">Ann</td><td align="center">10</td><td align="left">5 x 2 early in startup</td></tr><tr><td align="left">Request Announcement WINEPRESSME</td><td align="center">Ann</td><td align="center">4</td><td align="left">Early in startup</td></tr></tbody></table></div></div><br class="table-break"><p><a class="indexterm" name="id2626504"></a><a class="indexterm" name="id2626512"></a>
+ </p><div class="table"><a name="capsstats01"></a><p class="title"><b>Table 16.1. Windows Me Startup Broadcast Capture Statistics</b></p><div class="table-contents"><table summary="Windows Me Startup Broadcast Capture Statistics" border="1"><colgroup><col align="left"><col align="center"><col align="center"><col align="left"></colgroup><thead><tr><th align="left">Message</th><th align="center">Type</th><th align="center">Num</th><th align="left">Notes</th></tr></thead><tbody><tr><td align="left">WINEPRESSME<00></td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.6 sec apart</td></tr><tr><td align="left">WINEPRESSME<03></td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.6 sec apart</td></tr><tr><td align="left">WINEPRESSME<20></td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH<00></td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH<1d></td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH<1e></td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH<1b></td><td align="center">Qry</td><td align="center">84</td><td align="left">300 sec apart at stable operation</td></tr><tr><td align="left">__MSBROWSE__</td><td align="center">Reg</td><td align="center">8</td><td align="left">Registered after winning election to Browse Master</td></tr><tr><td align="left">JHT<03></td><td align="center">Reg</td><td align="center">8</td><td align="left">4 x 2. This is the name of the user that logged onto Windows</td></tr><tr><td align="left">Host Announcement WINEPRESSME</td><td align="center">Ann</td><td align="center">2</td><td align="left">Observed at 10 sec</td></tr><tr><td align="left">Domain/Workgroup Announcement MIDEARTH</td><td align="center">Ann</td><td align="center">18</td><td align="left">300 sec apart at stable operation</td></tr><tr><td align="left">Local Master Announcement WINEPRESSME</td><td align="center">Ann</td><td align="center">18</td><td align="left">300 sec apart at stable operation</td></tr><tr><td align="left">Get Backup List Request</td><td align="center">Qry</td><td align="center">12</td><td align="left">6 x 2 early in startup, 0.5 sec apart</td></tr><tr><td align="left">Browser Election Request</td><td align="center">Ann</td><td align="center">10</td><td align="left">5 x 2 early in startup</td></tr><tr><td align="left">Request Announcement WINEPRESSME</td><td align="center">Ann</td><td align="center">4</td><td align="left">Early in startup</td></tr></tbody></table></div></div><br class="table-break"><p><a class="indexterm" name="id2626480"></a><a class="indexterm" name="id2626488"></a>
From the packet trace, it should be noted that no messages were propagated over TCP/IP;
all messages employed UDP/IP. When steady-state operation has been achieved, there is a cycle
of various announcements, re-election of a browse master, and name queries. These create
the symphony of announcements by which network browsing is made possible.
- </p><p><a class="indexterm" name="id2626529"></a>
+ </p><p><a class="indexterm" name="id2626506"></a>
For detailed information regarding the precise behavior of the CIFS/SMB protocols,
refer to the book “<span class="quote">Implementing CIFS: The Common Internet File System,</span>”
by Christopher Hertel, (Prentice Hall PTR, ISBN: 013047116X).
</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="secondmachine"></a>Second Machine Startup Broadcast Interaction</h3></div></div></div><p>
At this time, the machine you used to capture the single-system startup trace should still be running.
The objective of this task is to identify the interaction of two machines in respect to broadcast activity.
- </p><div class="procedure"><a name="id26265
65"></a><p class="title"><b>Procedure 16.3. Monitoring of Second Machine Activity</b></p><ol type="1"><li><p>
+ </p><div class="procedure"><a name="id26265
42"></a><p class="title"><b>Procedure 16.3. Monitoring of Second Machine Activity</b></p><ol type="1"><li><p>
On the machine from which network activity will be monitored (using <code class="literal">Wireshark</code>),
launch <code class="literal">Wireshark</code> and click
<span class="guimenu">Capture</span> → <span class="guimenuitem">Start</span>.
</p></li><li><p>
Analyze the capture trace, taking note of the transport protocols used, the types of messages observed,
and what interaction took place between the two machines. Leave both machines running for the next task.
- </p></li></ol></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id26266
81"></a>Findings</h4></div></div></div><p>
+ </p></li></ol></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id26266
58"></a>Findings</h4></div></div></div><p>
<a class="link" href="primer.html#capsstats02" title="Table 16.2. Second Machine (Windows 98) Capture Statistics">“Second Machine (Windows 98) Capture Statistics”</a> summarizes capture statistics observed. As in the previous case,
all announcements used UDP/IP broadcasts. Also, as was observed with the last example, the second
Windows 9x/Me machine broadcasts its name on startup to ensure that there exists no name clash
to explore the inner details of the precise mechanism of how this functions should refer to
“<span class="quote">Implementing CIFS: The Common Internet File System.</span>”
</p><div class="table"><a name="capsstats02"></a><p class="title"><b>Table 16.2. Second Machine (Windows 98) Capture Statistics</b></p><div class="table-contents"><table summary="Second Machine (Windows 98) Capture Statistics" border="1"><colgroup><col align="left"><col align="center"><col align="center"><col align="left"></colgroup><thead><tr><th align="left">Message</th><th align="center">Type</th><th align="center">Num</th><th align="left">Notes</th></tr></thead><tbody><tr><td align="left">MILGATE98<00></td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.6 sec apart</td></tr><tr><td align="left">MILGATE98<03></td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.6 sec apart</td></tr><tr><td align="left">MILGATE98<20></td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH<00></td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH<1d></td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH<1e></td><td align="center">Reg</td><td align="center">8</td><td align="left">4 lots of 2, 0.75 sec apart</td></tr><tr><td align="left">MIDEARTH<1b></td><td align="center">Qry</td><td align="center">18</td><td align="left">900 sec apart at stable operation</td></tr><tr><td align="left">JHT<03></td><td align="center">Reg</td><td align="center">2</td><td align="left">This is the name of the user that logged onto Windows</td></tr><tr><td align="left">Host Announcement MILGATE98</td><td align="center">Ann</td><td align="center">14</td><td align="left">Every 120 sec</td></tr><tr><td align="left">Domain/Workgroup Announcement MIDEARTH</td><td align="center">Ann</td><td align="center">6</td><td align="left">900 sec apart at stable operation</td></tr><tr><td align="left">Local Master Announcement WINEPRESSME</td><td align="center">Ann</td><td align="center">6</td><td align="left">Insufficient detail to determine frequency</td></tr></tbody></table></div></div><br class="table-break"><p>
- <a class="indexterm" name="id2626964"></a>
- <a class="indexterm" name="id2626971"></a>
- <a class="indexterm" name="id2626978"></a>
+ <a class="indexterm" name="id2626940"></a>
+ <a class="indexterm" name="id2626947"></a>
+ <a class="indexterm" name="id2626954"></a>
Observation of the contents of Host Announcements, Domain/Workgroup Announcements,
and Local Master Announcements is instructive. These messages convey a significant
level of detail regarding the nature of each machine that is on the network. An example
dissection of a Host Announcement is given in <a class="link" href="primer.html#hostannounce" title="Figure 16.3. Typical Windows 9x/Me Host Announcement">“Typical Windows 9x/Me Host Announcement”</a>.
- </p><div class="figure"><a name="hostannounce"></a><p class="title"><b>Figure 16.3. Typical Windows 9x/Me Host Announcement</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/HostAnnouncment.png" width="221.4" alt="Typical Windows 9x/Me Host Announcement"></div></div></div><br class="figure-break"></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26270
42"></a>Simple Windows Client Connection Characteristics</h3></div></div></div><p>
+ </p><div class="figure"><a name="hostannounce"></a><p class="title"><b>Figure 16.3. Typical Windows 9x/Me Host Announcement</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/HostAnnouncment.png" width="221.4" alt="Typical Windows 9x/Me Host Announcement"></div></div></div><br class="figure-break"></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26270
19"></a>Simple Windows Client Connection Characteristics</h3></div></div></div><p>
The purpose of this exercise is to discover how Microsoft Windows clients create (establish)
connections with remote servers. The methodology involves analysis of a key aspect of how
Windows clients access remote servers: the session setup protocol.
- </p><div class="procedure"><a name="id26270
56"></a><p class="title"><b>Procedure 16.4. Client Connection Exploration Steps</b></p><ol type="1"><li><p>
+ </p><div class="procedure"><a name="id26270
33"></a><p class="title"><b>Procedure 16.4. Client Connection Exploration Steps</b></p><ol type="1"><li><p>
Configure a Windows 9x/Me machine (MILGATE98) with a share called <code class="constant">Stuff</code>.
Create a <em class="parameter"><code>Full Access</code></em> control password on this share.
</p></li><li><p>
When the share called <code class="constant">Stuff</code> is being displayed, stop the capture.
Save the captured data in case it is needed for later analysis.
</p></li><li><p>
- <a class="indexterm" name="id2627187"></a>
+ <a class="indexterm" name="id2627164"></a>
From the top of the packets captured, scan down to locate the first packet that has
interpreted as <code class="constant">Session Setup AndX, User: anonymous; Tree Connect AndX,
Path: \\MILGATE98\IPC$</code>.
- </p></li><li><p><a class="indexterm" name="id2627206"></a><a class="indexterm" name="id2627214"></a>
+ </p></li><li><p><a class="indexterm" name="id2627183"></a><a class="indexterm" name="id2627191"></a>
In the dissection (analysis) panel, expand the <code class="constant">SMB, Session Setup AndX Request,
and Tree Connect AndX Request</code>. Examine both operations. Identify the name of
the user Account and what password was used. The Account name should be empty.
decoded of the type <code class="constant">Session Setup AndX</code>. Locate the last such packet
that was targeted at the <code class="constant">\\MILGATE98\IPC$</code> service.
</p></li><li><p>
- <a class="indexterm" name="id2627259"></a>
- <a class="indexterm" name="id2627266"></a>
+ <a class="indexterm" name="id2627236"></a>
+ <a class="indexterm" name="id2627242"></a>
Dissect this packet as per the previous one. This packet should have a password length
of 24 (characters) and should have a password field, the contents of which is a
long hexadecimal number. Observe the name in the Account field. This is a User Mode
session setup packet.
- </p></li></ol></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id26272
80"></a>Findings and Comments</h4></div></div></div><p>
- <a class="indexterm" name="id2627288"></a>
- The <code class="constant">IPC$</code> share serves a vital purpose<sup>[<a name="id2627299" href="#ftn.id2627299" class="footnote">15</a>]</sup>
+ </p></li></ol></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id26272
56"></a>Findings and Comments</h4></div></div></div><p>
+ <a class="indexterm" name="id2627265"></a>
+ The <code class="constant">IPC$</code> share serves a vital purpose<sup>[<a name="id2627276" href="#ftn.id2627276" class="footnote">15</a>]</sup>
in SMB/CIFS-based networking. A Windows client connects to this resource to obtain the list of
resources that are available on the server. The server responds with the shares and print queues that
are available. In most but not all cases, the connection is made with a <code class="constant">NULL</code>
username and a <code class="constant">NULL</code> password.
</p><p>
- <a class="indexterm" name="id2627320"></a>
+ <a class="indexterm" name="id2627296"></a>
The two packets examined are material evidence of how Windows clients may
interoperate with Samba. Samba requires every connection setup to be authenticated using
valid UNIX account credentials (UID/GID). This means that even a <code class="constant">NULL</code>
session setup can be established only by automatically mapping it to a valid UNIX
account.
</p><p>
- <a class="indexterm" name="id2627339"></a><a class="indexterm" name="id2627345"></a>
- <a class="indexterm" name="id2627354"></a>
+ <a class="indexterm" name="id2627316"></a><a class="indexterm" name="id2627322"></a>
+ <a class="indexterm" name="id2627331"></a>
Samba has a special name for the <code class="constant">NULL</code>, or empty, user account:
it calls it the <a class="link" href="smb.conf.5.html#GUESTACCOUNT" target="_top">guest account</a>. The
default value of this parameter is <code class="constant">nobody</code>; however, this can be
FTP account. A sample NULL Session Setup AndX packet dissection is shown in
<a class="link" href="primer.html#nullconnect" title="Figure 16.4. Typical Windows 9x/Me NULL SessionSetUp AndX Request">“Typical Windows 9x/Me NULL SessionSetUp AndX Request”</a>.
</p><div class="figure"><a name="nullconnect"></a><p class="title"><b>Figure 16.4. Typical Windows 9x/Me NULL SessionSetUp AndX Request</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/NullConnect.png" width="221.4" alt="Typical Windows 9x/Me NULL SessionSetUp AndX Request"></div></div></div><br class="figure-break"><p>
- <a class="indexterm" name="id2627439"></a>
- <a class="indexterm" name="id2627446"></a>
- <a class="indexterm" name="id2627453"></a>
+ <a class="indexterm" name="id2627416"></a>
+ <a class="indexterm" name="id2627423"></a>
+ <a class="indexterm" name="id2627430"></a>
When a UNIX/Linux system does not have a <code class="constant">nobody</code> user account
(<code class="filename">/etc/passwd</code>), the operation of the <code class="constant">NULL</code>
account cannot validate and thus connections that utilize the guest account
problem reported on the Samba mailing list. A sample User Mode session setup AndX
is shown in <a class="link" href="primer.html#userconnect" title="Figure 16.5. Typical Windows 9x/Me User SessionSetUp AndX Request">“Typical Windows 9x/Me User SessionSetUp AndX Request”</a>.
</p><div class="figure"><a name="userconnect"></a><p class="title"><b>Figure 16.5. Typical Windows 9x/Me User SessionSetUp AndX Request</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/UserConnect.png" width="221.4" alt="Typical Windows 9x/Me User SessionSetUp AndX Request"></div></div></div><br class="figure-break"><p>
- <a class="indexterm" name="id2627530"></a>
+ <a class="indexterm" name="id2627507"></a>
The User Mode connection packet contains the account name and the domain name.
The password is provided in Microsoft encrypted form, and its length is shown
as 24 characters. This is the length of Microsoft encrypted passwords.
- </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26275
44"></a>Windows 200x/XP Client Interaction with Samba-3</h3></div></div></div><p>
+ </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26275
21"></a>Windows 200x/XP Client Interaction with Samba-3</h3></div></div></div><p>
By now you may be asking, “<span class="quote">Why did you choose to work with Windows 9x/Me?</span>”
</p><p>
First, we want to demonstrate the simple case. This book is not intended to be a detailed treatise
To complete this exercise, you need a Windows XP Professional client that has been configured as
a domain member of either a Samba-controlled domain or a Windows NT4 or 200x Active Directory domain.
Here we do not provide details for how to configure this, as full coverage is provided earlier in this book.
- </p><div class="procedure"><a name="id26275
87"></a><p class="title"><b>Procedure 16.5. Steps to Explore Windows XP Pro Connection Set-up</b></p><ol type="1"><li><p>
+ </p><div class="procedure"><a name="id26275
64"></a><p class="title"><b>Procedure 16.5. Steps to Explore Windows XP Pro Connection Set-up</b></p><ol type="1"><li><p>
Start your domain controller. Also, start the Wireshark monitoring machine, launch Wireshark,
and then wait for the next step to complete.
</p></li><li><p>
If desired, the Windows XP Professional client and the domain controller are no longer needed for exercises
in this chapter.
</p></li><li><p>
- <a class="indexterm" name="id2627813"></a>
- <a class="indexterm" name="id2627820"></a>
+ <a class="indexterm" name="id2627790"></a>
+ <a class="indexterm" name="id2627797"></a>
From the top of the packets captured, scan down to locate the first packet that has
interpreted as <code class="constant">Session Setup AndX Request, NTLMSSP_AUTH</code>.
</p></li><li><p>
- <a class="indexterm" name="id2627840"></a>
- <a class="indexterm" name="id2627847"></a>
- <a class="indexterm" name="id2627854"></a>
+ <a class="indexterm" name="id2627817"></a>
+ <a class="indexterm" name="id2627824"></a>
+ <a class="indexterm" name="id2627831"></a>
In the dissection (analysis) panel, expand the <code class="constant">SMB, Session Setup AndX Request</code>.
Expand the packet decode information, beginning at the <code class="constant">Security Blob:</code>
entry. Expand the <code class="constant">GSS-API -> SPNEGO -> netTokenTarg -> responseToken -> NTLMSSP</code>
decoded of the type <code class="constant">Session Setup AndX Request</code>. Click the last such packet that
has been decoded as <code class="constant">Session Setup AndX Request, NTLMSSP_AUTH</code>.
</p></li><li><p>
- <a class="indexterm" name="id2627917"></a>
+ <a class="indexterm" name="id2627893"></a>
In the dissection (analysis) panel, expand the <code class="constant">SMB, Session Setup AndX Request</code>.
Expand the packet decode information, beginning at the <code class="constant">Security Blob:</code>
entry. Expand the <code class="constant">GSS-API -> SPNEGO -> netTokenTarg -> responseToken -> NTLMSSP</code>
The values of these two parameters are the Microsoft encrypted password hashes: respectively, the LanMan
password and then the NT (case-preserving) password hash.
</p></li><li><p>
- <a class="indexterm" name="id2627978"></a>
- <a class="indexterm" name="id2627985"></a>
+ <a class="indexterm" name="id2627955"></a>
+ <a class="indexterm" name="id2627962"></a>
The passwords are 24-character hexadecimal numbers. This packet confirms that this is a User Mode
session setup packet.
- </p></li></ol></div><div class="figure"><a name="XPCap01"></a><p class="title"><b>Figure 16.6. Typical Windows XP NULL Session Setup AndX Request</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WindowsXP-NullConnection.png" width="270" alt="Typical Windows XP NULL Session Setup AndX Request"></div></div></div><br class="figure-break"><div class="figure"><a name="XPCap02"></a><p class="title"><b>Figure 16.7. Typical Windows XP User Session Setup AndX Request</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WindowsXP-UserConnection.png" width="270" alt="Typical Windows XP User Session Setup AndX Request"></div></div></div><br class="figure-break"><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2628081"></a>Discussion</h4></div></div></div><p><a class="indexterm" name="id2628088"></a>
+ </p></li></ol></div><div class="figure"><a name="XPCap01"></a><p class="title"><b>Figure 16.6. Typical Windows XP NULL Session Setup AndX Request</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WindowsXP-NullConnection.png" width="270" alt="Typical Windows XP NULL Session Setup AndX Request"></div></div></div><br class="figure-break"><div class="figure"><a name="XPCap02"></a><p class="title"><b>Figure 16.7. Typical Windows XP User Session Setup AndX Request</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/WindowsXP-UserConnection.png" width="270" alt="Typical Windows XP User Session Setup AndX Request"></div></div></div><br class="figure-break"><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2628058"></a>Discussion</h4></div></div></div><p><a class="indexterm" name="id2628065"></a>
This exercise demonstrates that, while the specific protocol for the Session Setup AndX is handled
in a more sophisticated manner by recent MS Windows clients, the underlying rules or principles
remain the same. Thus it is demonstrated that MS Windows XP Professional clients still use a
<code class="constant">NULL-Session</code> connection to query and locate resources on an advanced network
technology server (one using Windows NT4/200x or Samba). It also demonstrates that an authenticated
connection must be made before resources can be used.
- </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2628
113"></a>Conclusions to Exercises</h3></div></div></div><p>
+ </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2628
089"></a>Conclusions to Exercises</h3></div></div></div><p>
In summary, the following points have been established in this chapter:
</p><div class="itemizedlist"><ul type="disc"><li><p>
When NetBIOS over TCP/IP protocols are enabled, MS Windows networking employs broadcast-oriented messaging protocols to provide knowledge of network services.
file or in an LDAP database. Samba-3 permits use of multiple <em class="parameter"><code>passdb backend</code></em>
databases in concurrent deployment. Refer to <span class="emphasis"><em>TOSHARG2</em></span>, Chapter 10, “<span class="quote">Account Information Databases.</span>”
</p></li></ul></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="chap01conc"></a>Dissection and Discussion</h2></div></div></div><p>
- <a class="indexterm" name="id2628200"></a>
+ <a class="indexterm" name="id2628177"></a>
The exercises demonstrate the use of the <code class="constant">guest</code> account, the way that
MS Windows clients and servers resolve computer names to a TCP/IP address, and how connections
between a client and a server are established.
Those wishing background information regarding NetBIOS name types should refer to
the Microsoft knowledgebase article
<a class="ulink" href="http://support.microsoft.com/support/kb/articles/Q102/78/8.asp" target="_top">Q102878.</a>
- </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26282
27"></a>Technical Issues</h3></div></div></div><p>
- <a class="indexterm" name="id2628235"></a>
+ </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id26282
04"></a>Technical Issues</h3></div></div></div><p>
+ <a class="indexterm" name="id2628212"></a>
Network browsing involves SMB broadcast announcements, SMB enumeration requests,
connections to the <code class="constant">IPC$</code> share, share enumerations, and SMB connection
setup processes. The use of anonymous connections to a Samba server involve the use of
</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="chap01qa"></a>Questions and Answers</h2></div></div></div><p>
The questions and answers given in this section are designed to highlight important aspects of Microsoft
Windows networking.
- </p><div class="qandaset"><dl><dt> <a href="primer.html#id2628281">
+ </p><div class="qandaset"><dl><dt> <a href="primer.html#id2628258">
What is the significance of the MIDEARTH<1b> type query?
- </a></dt><dt> <a href="primer.html#id2628328">
+ </a></dt><dt> <a href="primer.html#id2628304">
What is the significance of the MIDEARTH<1d> type name registration?
- </a></dt><dt> <a href="primer.html#id2628402">
+ </a></dt><dt> <a href="primer.html#id2628378">
What is the role and significance of the <01><02>__MSBROWSE__<02><01>
name registration?
- </a></dt><dt> <a href="primer.html#id2628434">
+ </a></dt><dt> <a href="primer.html#id2628411">
What is the significance of the MIDEARTH<1e> type name registration?
- </a></dt><dt> <a href="primer.html#id2628465">
+ </a></dt><dt> <a href="primer.html#id2628442">
What is the significance of the guest account in smb.conf?
- </a></dt><dt> <a href="primer.html#id2628543">
+ </a></dt><dt> <a href="primer.html#id2628520">
Is it possible to reduce network broadcast activity with Samba-3?
- </a></dt><dt> <a href="primer.html#id2628652">
+ </a></dt><dt> <a href="primer.html#id2628629">
Can I just use plain-text passwords with Samba?
- </a></dt><dt> <a href="primer.html#id2628739">
+ </a></dt><dt> <a href="primer.html#id2628716">
What parameter in the smb.conf file is used to enable the use of encrypted passwords?
- </a></dt><dt> <a href="primer.html#id2628780">
+ </a></dt><dt> <a href="primer.html#id2628757">
Is it necessary to specify encrypt passwords = Yes
when Samba-3 is configured as a domain member?
- </a></dt><dt> <a href="primer.html#id2628812">
+ </a></dt><dt> <a href="primer.html#id2628789">
Is it necessary to specify a guest account when Samba-3 is configured
as a domain member server?
- </a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id26282
81"></a><a name="id2628283"></a></td><td align="left" valign="top"><p>
+ </a></dt></dl><table border="0" summary="Q and A Set"><col align="left" width="1%"><tbody><tr class="question"><td align="left" valign="top"><a name="id26282
58"></a><a name="id2628260"></a></td><td align="left" valign="top"><p>
What is the significance of the MIDEARTH<1b> type query?
</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
- <a class="indexterm" name="id2628296"></a>
- <a class="indexterm" name="id2628305"></a>
+ <a class="indexterm" name="id2628272"></a>
+ <a class="indexterm" name="id2628282"></a>
This is a broadcast announcement by which the Windows machine is attempting to
locate a Domain Master Browser (DMB) in the event that it might exist on the network.
Refer to <span class="emphasis"><em>TOSHARG2,</em></span> Chapter 9, Section 9.7, “<span class="quote">Technical Overview of Browsing,</span>”
for details regarding the function of the DMB and its role in network browsing.
- </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id26283
28"></a><a name="id2628330"></a></td><td align="left" valign="top"><p>
+ </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id26283
04"></a><a name="id2628306"></a></td><td align="left" valign="top"><p>
What is the significance of the MIDEARTH<1d> type name registration?
</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
- <a class="indexterm" name="id2628342"></a>
- <a class="indexterm" name="id2628351"></a>
+ <a class="indexterm" name="id2628319"></a>
+ <a class="indexterm" name="id2628328"></a>
This name registration records the machine IP addresses of the LMBs.
Network clients can query this name type to obtain a list of browser servers from the
master browser.
The IP address of the DMB (if one exists)
</p></li><li><p>
The IP address of the LMB on the local segment
- </p></li></ul></div></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628
402"></a><a name="id2628404"></a></td><td align="left" valign="top"><p>
+ </p></li></ul></div></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628
378"></a><a name="id2628381"></a></td><td align="left" valign="top"><p>
What is the role and significance of the <01><02>__MSBROWSE__<02><01>
name registration?
</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
- <a class="indexterm" name="id2628419"></a>
+ <a class="indexterm" name="id2628396"></a>
This name is registered by the browse master to broadcast and receive domain announcements.
Its scope is limited to the local network segment, or subnet. By querying this name type,
master browsers on networks that have multiple domains can find the names of master browsers
for each domain.
- </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id26284
34"></a><a name="id2628436"></a></td><td align="left" valign="top"><p>
+ </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id26284
11"></a><a name="id2628413"></a></td><td align="left" valign="top"><p>
What is the significance of the MIDEARTH<1e> type name registration?
</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
- <a class="indexterm" name="id2628449"></a>
+ <a class="indexterm" name="id2628425"></a>
This name is registered by all browse masters in a domain or workgroup. The registration
name type is known as the Browser Election Service. Master browsers register themselves
with this name type so that DMBs can locate them to perform cross-subnet
browse list updates. This name type is also used to initiate elections for Master Browsers.
- </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id26284
65"></a><a name="id2628467"></a></td><td align="left" valign="top"><p>
- <a class="indexterm" name="id2628471"></a>
+ </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id26284
42"></a><a name="id2628444"></a></td><td align="left" valign="top"><p>
+ <a class="indexterm" name="id2628448"></a>
What is the significance of the <em class="parameter"><code>guest account</code></em> in smb.conf?
</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
This parameter specifies the default UNIX account to which MS Windows networking
Samba operation. Either the operating system must have an account called <code class="constant">nobody</code>
or there must be an entry in the <code class="filename">smb.conf</code> file with a valid UNIX account, such as
<a class="link" href="smb.conf.5.html#GUESTACCOUNT" target="_top">guest account = ftp</a>.
- </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id26285
43"></a><a name="id2628545"></a></td><td align="left" valign="top"><p>
+ </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id26285
20"></a><a name="id2628522"></a></td><td align="left" valign="top"><p>
Is it possible to reduce network broadcast activity with Samba-3?
</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
- <a class="indexterm" name="id2628557"></a>
- <a class="indexterm" name="id2628564"></a>
+ <a class="indexterm" name="id2628534"></a>
+ <a class="indexterm" name="id2628540"></a>
Yes, there are two ways to do this. The first involves use of WINS (See <span class="emphasis"><em>TOSHARG2</em></span>, Chapter 9,
Section 9.5, “<span class="quote">WINS The Windows Inter-networking Name Server</span>”); the
alternate method involves disabling the use of NetBIOS over TCP/IP. This second method requires
a correctly configured DNS server (see <span class="emphasis"><em>TOSHARG2</em></span>, Chapter 9, Section 9.3, “<span class="quote">Discussion</span>”).
</p><p>
- <a class="indexterm" name="id2628595"></a>
- <a class="indexterm" name="id2628602"></a>
- <a class="indexterm" name="id2628611"></a>
+ <a class="indexterm" name="id2628572"></a>
+ <a class="indexterm" name="id2628579"></a>
+ <a class="indexterm" name="id2628588"></a>
The use of WINS reduces network broadcast traffic. The reduction is greatest when all network
clients are configured to operate in <em class="parameter"><code>Hybrid Mode</code></em>. This can be effected through
use of DHCP to set the NetBIOS node type to type 8 for all network clients. Additionally, it is
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
Use of SMB without NetBIOS is possible only on Windows 200x/XP Professional clients and servers, as
well as with Samba-3.
- </p></div></td></tr><tr class="question"><td align="left" valign="top"><a name="id26286
52"></a><a name="id2628654"></a></td><td align="left" valign="top"><p>
+ </p></div></td></tr><tr class="question"><td align="left" valign="top"><a name="id26286
29"></a><a name="id2628631"></a></td><td align="left" valign="top"><p>
Can I just use plain-text passwords with Samba?
</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
Yes, you can configure Samba to use plain-text passwords, though this does create a few problems.
a UNIX system account for that user. On systems that run <code class="literal">winbindd</code> to access the Samba
PDC/BDC to provide Windows user and group accounts, the <em class="parameter"><code>idmap uid, idmap gid</code></em> ranges
set in the <code class="filename">smb.conf</code> file provide the local UID/GIDs needed for local identity management purposes.
- </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id26287
39"></a><a name="id2628741"></a></td><td align="left" valign="top"><p>
+ </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id26287
16"></a><a name="id2628718"></a></td><td align="left" valign="top"><p>
What parameter in the <code class="filename">smb.conf</code> file is used to enable the use of encrypted passwords?
</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
The parameter in the <code class="filename">smb.conf</code> file that controls this behavior is known as <em class="parameter"><code>encrypt
passwords</code></em>. The default setting for this in Samba-3 is <code class="constant">Yes (Enabled)</code>.
- </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id26287
80"></a><a name="id2628782"></a></td><td align="left" valign="top"><p>
+ </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id26287
57"></a><a name="id2628759"></a></td><td align="left" valign="top"><p>
Is it necessary to specify <a class="link" href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords = Yes</a>
when Samba-3 is configured as a domain member?
</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
No. This is the default behavior.
- </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628
812"></a><a name="id2628814"></a></td><td align="left" valign="top"><p>
+ </p></td></tr><tr class="question"><td align="left" valign="top"><a name="id2628
789"></a><a name="id2628791"></a></td><td align="left" valign="top"><p>
Is it necessary to specify a <em class="parameter"><code>guest account</code></em> when Samba-3 is configured
as a domain member server?
</p></td></tr><tr class="answer"><td align="left" valign="top"></td><td align="left" valign="top"><p>
<code class="constant">nobody</code>. If this account does not exist on the UNIX server, then it is
necessary to provide a <a class="link" href="smb.conf.5.html#GUESTACCOUNT" target="_top">guest account = an_account</a>,
where <code class="constant">an_account</code> is a valid local UNIX user account.
- </p></td></tr></tbody></table></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id26272
99" href="#id2627299" class="para">15</a>] </sup>TOSHARG2, Sect 4.5.1</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="appendix.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="RefSection.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="apa.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 15. A Collection of Useful Tidbits </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix A.
+ </p></td></tr></tbody></table></div></div><div class="footnotes"><br><hr width="100" align="left"><div class="footnote"><p><sup>[<a name="ftn.id26272
76" href="#id2627276" class="para">15</a>] </sup>TOSHARG2, Sect 4.5.1</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="appendix.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="RefSection.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="apa.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 15. A Collection of Useful Tidbits </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix A.
GNU General Public License version 3
</td></tr></table></div></body></html>
git.samba.org / abartlet / samba-debian.git / blobdiff