Updating TOSHARG files

(This used to be commit 2ada75f02f4ba7de548a56a14f1bb0281029e063)

1 files changed, 54 insertions, 12 deletions

diff --git a/docs/Samba3-HOWTO/TOSHARG-Problems.xml b/docs/Samba3-HOWTO/TOSHARG-Problems.xml
index 6b5e232af0..8f1d3c1849 100644
--- a/docs/Samba3-HOWTO/TOSHARG-Problems.xml
+++ b/docs/Samba3-HOWTO/TOSHARG-Problems.xml
@@ -13,15 +13,23 @@
 <title>Analyzing and Solving Samba Problems</title>
 
 <para>
-There are many sources of information available in the form 
-of mailing lists, RFCs, and documentation. The documentation that comes
-with the Samba distribution contains good explanations of 
-general SMB topics such as browsing.</para> 
+<indexterm><primary>RFCs</primary></indexterm>
+<indexterm><primary>SMB</primary></indexterm>
+<indexterm><primary>documentation</primary></indexterm>
+There are many sources of information available in the form of mailing lists, RFCs, and documentation. The
+documentation that comes with the Samba distribution contains good explanations of general SMB topics such as
+browsing.
+</para> 
 	
 <sect1>
 <title>Diagnostics Tools</title>
 
 <para>
+<indexterm><primary>sniffer</primary></indexterm>
+<indexterm><primary>LAN</primary></indexterm>
+<indexterm><primary>analyzes data</primary></indexterm>
+<indexterm><primary>SMB networking</primary></indexterm>
+<indexterm><primary>network analyzer</primary></indexterm>
 With SMB networking, it is often not immediately clear what the cause is of a certain problem. Samba itself
 provides rather useful information, but in some cases you might have to fall back to using a
 <emphasis>sniffer</emphasis>. A sniffer is a program that listens on your LAN, analyzes the data sent on it,
@@ -32,15 +40,29 @@ and displays it on the screen.
 <title>Debugging with Samba Itself</title>
 
 <para>
+<indexterm><primary>diagnostic tools</primary></indexterm>
+<indexterm><primary>debugging problems</primary></indexterm>
+<indexterm><primary>smbd</primary></indexterm>
+<indexterm><primary>nmbd</primary></indexterm>
+<indexterm><primary>debugging passwords</primary></indexterm>
+<indexterm><primary>debug level</primary></indexterm>
+<indexterm><primary>log level</primary></indexterm>
 One of the best diagnostic tools for debugging problems is Samba itself.  You can use the <option>-d
 option</option> for both &smbd; and &nmbd; to specify the <smbconfoption name="debug level"/> at which to run.
 See the man pages for <command>smbd, nmbd</command>, and &smb.conf; for more information regarding debugging
-options. The debug level can range from 1 (the default) to 10 (100 for debugging passwords).
+options. The debug level (log level) can range from 1 (the default) to 10 (100 for debugging passwords).
 </para>
 	
 <para>
+<indexterm><primary>debugging</primary></indexterm>
+<indexterm><primary>gcc</primary></indexterm>
+<indexterm><primary>gdb</primary></indexterm>
+<indexterm><primary>smbd</primary></indexterm>
+<indexterm><primary>nmbd</primary></indexterm>
+<indexterm><primary>LsaEnumTrustedDomains</primary></indexterm>
+<indexterm><primary>attach gdb</primary></indexterm>
 Another helpful method of debugging is to compile Samba using the <command>gcc -g </command> flag. This will
-include debug information in the binaries and allow you to attach gdb to the running
+include debug information in the binaries and allow you to attach <command>gdb</command> to the running
 <command>smbd/nmbd</command> process.  To attach <command>gdb</command> to an <command>smbd</command> process
 for an NT workstation, first get the workstation to make the connection. Pressing ctrl-alt-delete and going
 down to the domain box is sufficient (at least, the first time you join the domain) to generate a
@@ -52,12 +74,13 @@ between pressing <command>ctrl-alt-delete</command> and actually typing in your
 
 <para>
 Some useful Samba commands worth investigating are:
-</para>
-	
+<indexterm><primary>testparm</primary></indexterm>
+<indexterm><primary>smbclient</primary></indexterm>
 <screen>
 &prompt;<userinput>testparm | more</userinput>
 &prompt;<userinput>smbclient -L //{netbios name of server}</userinput>
 </screen>
+</para>
 
 </sect2>
 
@@ -65,6 +88,9 @@ Some useful Samba commands worth investigating are:
 	<title>Tcpdump</title>
   
 <para>
+<indexterm><primary>tcpdump</primary></indexterm>
+<indexterm><primary>tethereal</primary></indexterm>
+<indexterm><primary>ethereal</primary></indexterm>
 <ulink url="http://www.tcpdump.org/">Tcpdump</ulink> was the first 
 UNIX sniffer with SMB support. It is a command-line utility and 
 now, its SMB support is somewhat lagging that of <command>ethereal</command> 
@@ -77,6 +103,7 @@ and <command>tethereal</command>.
 	<title>Ethereal</title>
 
 <para>
+<indexterm><primary>ethereal</primary></indexterm>
 <ulink url="http://www.ethereal.com/">Ethereal</ulink> is a graphical sniffer, available for both UNIX (Gtk)
 and Windows. Ethereal's SMB support is quite good. For details on the use of <command>ethereal</command>, read
 the well-written Ethereal User Guide.
@@ -85,6 +112,7 @@ the well-written Ethereal User Guide.
 <figure id="ethereal1"><title>Starting a Capture.</title><imagefile>ethereal1</imagefile></figure>
 
 <para>
+<indexterm><primary>ports</primary></indexterm>
 Listen for data on ports 137, 138, 139, and 445. For example, use the filter <userinput>port 137, port 138,
 port 139, or port 445</userinput> as seen in <link linkend="ethereal1">Starting a Capture</link> snapshot.
 </para>
@@ -101,6 +129,12 @@ A console version of ethereal is available as well and is called <command>tether
 <title>The Windows Network Monitor</title>
 	
 <para>
+<indexterm><primary>Network Monitor</primary></indexterm>
+<indexterm><primary>Netmon</primary></indexterm>
+<indexterm><primary>Microsoft Developer Network CDs</primary></indexterm>
+<indexterm><primary>SMS</primary></indexterm>
+<indexterm><primary>promiscuous mode</primary></indexterm>
+<indexterm><primary>ethereal</primary></indexterm>
 For tracing things on Microsoft Windows NT, Network Monitor (aka Netmon) is available on Microsoft Developer
 Network CDs, the Windows NT Server install CD, and the SMS CDs. The version of Netmon that ships with SMS
 allows for dumping packets between any two computers (i.e., placing the network interface in promiscuous
@@ -113,6 +147,7 @@ files.
 <title>Installing Network Monitor on an NT Workstation</title>
 
 <para>
+<indexterm><primary>Netmon.</primary></indexterm>
 Installing Netmon on an NT workstation requires a couple of steps. The following are instructions for
 installing Netmon V4.00.349, which comes with Microsoft Windows NT Server 4.0, on Microsoft Windows NT
 Workstation 4.0. The process should be similar for other versions of Windows NT version of Netmon. You will
@@ -120,6 +155,7 @@ need both the Microsoft Windows NT Server 4.0 Install CD and the Workstation 4.0
 </para> 
 
 <para>
+<indexterm><primary>Network Monitor Tools and Agent</primary></indexterm>
 Initially you will need to install <application>Network Monitor Tools and Agent</application>
 on the NT Server to do this: 
 </para>
@@ -217,12 +253,16 @@ If you do post a message to one of the lists, please observe the following guide
 
 <itemizedlist>
 
-	<listitem><para>Always remember that the developers are volunteers; they are
+	<listitem><para>
+<indexterm><primary>volunteers</primary></indexterm>
+	Always remember that the developers are volunteers; they are
 	not paid and they never guarantee to produce a particular feature at 
 	a particular time. Any timelines are <quote>best guess,</quote> and nothing more.
 	</para></listitem>
 
-	<listitem><para>Always mention what version of Samba you are using and what 
+	<listitem><para>
+<indexterm><primary>PDC</primary></indexterm>
+	Always mention what version of Samba you are using and what 
 	operating system it's running under. You should list the relevant sections of
 	your &smb.conf; file, at least the options in <smbconfsection name="[global]"/>
 	that affect PDC support.
@@ -243,7 +283,9 @@ If you do post a message to one of the lists, please observe the following guide
 	with such bad netiquet bahavior.
 	</para></listitem> 
 
-	<listitem><para>Don't cross post. Work out which is the best list to post to 
+	<listitem><para>
+<indexterm><primary>cross post</primary></indexterm>
+	Don't cross post. Work out which is the best list to post to 
 	and see what happens. Do not post to both samba-ntdom and samba-technical.
 	Many people active on the lists subscribe to more 
 	than one list and get annoyed to see the same message two or more times.
@@ -251,7 +293,7 @@ If you do post a message to one of the lists, please observe the following guide
 	with on another list will forward it on for you.</para></listitem>
 
 	<listitem><para>You might include <emphasis>partial</emphasis>
-	log files written at a debug level set to as much as 20. 
+	log files written at a log level set to as much as 20. 
 	Please do not send the entire log but just enough to give the context of the
 	error messages.</para></listitem>