Put info about solving samba problems in a seperate appendix (it was in the

PDC chapter now)
(This used to be commit 30a2aa69665ef7107a7ec622f4158bae78a0492e)

3 files changed, 374 insertions, 448 deletions

diff --git a/docs/docbook/projdoc/Problems.sgml b/docs/docbook/projdoc/Problems.sgml
new file mode 100644
index 0000000000..1f880a78cd
--- /dev/null
+++ b/docs/docbook/projdoc/Problems.sgml
@@ -0,0 +1,276 @@
+<chapter id="problems">
+
+<chapterinfo>
+	&author.jerry;
+	&author.jelmer;
+	<author>
+		<firstname>David</firstname><surname>Bannon</surname>
+		<affiliation>
+			<orgname>Samba Team</orgname>
+			<address><email>dbannon@samba.org</email></address>
+		</affiliation>
+	</author>
+	<pubdate>8 Apr 2003</pubdate>
+</chapterinfo>
+
+<title>Analysing and solving samba problems</title>
+
+<para>
+There are many sources of information available in the form 
+of mailing lists, RFC's and documentation.  The docs that come 
+with the samba distribution contain very good explanations of 
+general SMB topics such as browsing.</para> 
+	
+<sect1>
+<title>Diagnostics tools</title>
+
+  <para>
+One of the best diagnostic tools for debugging problems is Samba itself.  
+You can use the -d option for both smbd and nmbd to specify what 
+'debug level' at which to run.  See the man pages on smbd, nmbd  and 
+smb.conf for more information on debugging options.  The debug 
+level can range from 1 (the default) to 10 (100 for debugging passwords).
+</para>
+	
+<para>
+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 smbd / nmbd process.  In order to attach gdb to an smbd 
+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, on the first time you join the domain) to 
+generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation 
+maintains an open connection, and therefore there will be an smbd 
+process running (assuming that you haven't set a really short smbd 
+idle timeout)  So, in between pressing ctrl alt delete, and actually 
+typing in your password, you can gdb attach and continue.
+</para>
+
+<para>
+Some useful samba commands worth investigating:
+</para>
+	
+<itemizedlist>
+	<listitem><para>testparam | more</para></listitem>
+	<listitem><para>smbclient -L //{netbios name of server}</para></listitem>
+</itemizedlist>
+   
+<para>
+An SMB enabled version of tcpdump is available from 
+<ulink url="http://www.tcpdump.org/">http://www.tcpdup.org/</ulink>.
+Ethereal, another good packet sniffer for Unix and Win32
+hosts, can be downloaded from <ulink 
+url="http://www.ethereal.com/">http://www.ethereal.com</ulink>.
+</para>
+	
+<para>
+For tracing things on the Microsoft Windows NT, Network Monitor 
+(aka. netmon) is available on the Microsoft Developer Network CD's, 
+the Windows NT Server install CD and the SMS CD's.  The version of 
+netmon that ships with SMS allows for dumping packets between any two 
+computers (i.e. placing the network interface in promiscuous mode).  
+The version on the NT Server install CD will only allow monitoring 
+of network traffic directed to the local NT box and broadcasts on the 
+local subnet.  Be aware that Ethereal can read and write netmon 
+formatted files.
+</para>
+
+</sect1>
+
+<sect1>
+<title>Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</title>
+
+<para>
+Installing netmon on an NT workstation requires a couple 
+of steps.  The following are 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 version of 
+Windows NT / Netmon.  You will need both the Microsoft Windows 
+NT Server 4.0 Install CD and the Workstation 4.0 Install CD.
+</para> 
+
+<para>
+Initially you will need to install 'Network Monitor Tools and Agent' 
+on the NT Server.  To do this 
+</para>
+
+<itemizedlist>
+	<listitem><para>Goto Start - Settings - Control Panel - 
+	Network - Services - Add </para></listitem>
+	
+	<listitem><para>Select the 'Network Monitor Tools and Agent' and 
+	click on 'OK'.</para></listitem> 
+	
+	<listitem><para>Click 'OK' on the Network Control Panel.
+	</para></listitem> 
+	
+	<listitem><para>Insert the Windows NT Server 4.0 install CD 
+	when prompted.</para></listitem> 
+</itemizedlist>
+
+<para>
+At this point the Netmon files should exist in 
+<filename>%SYSTEMROOT%\System32\netmon\*.*</filename>.    
+Two subdirectories exist as well, <filename>parsers\</filename> 
+which contains the necessary DLL's for parsing the netmon packet 
+dump, and <filename>captures\</filename>.
+</para>
+
+<para>
+In order to install the Netmon tools on an NT Workstation, you will 
+first need to install the 'Network  Monitor Agent' from the Workstation 
+install CD.
+</para>
+
+<itemizedlist>
+	<listitem><para>Goto Start - Settings - Control Panel - 
+	Network - Services - Add</para></listitem> 
+
+	<listitem><para>Select the 'Network Monitor Agent' and click 
+	on 'OK'.</para></listitem> 
+	
+	<listitem><para>Click 'OK' on the Network Control Panel.
+	</para></listitem> 
+	
+	<listitem><para>Insert the Windows NT Workstation 4.0 install 
+	CD when prompted.</para></listitem> 
+</itemizedlist>
+
+<para>
+Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.* 
+to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set 
+permissions as  you deem appropriate for your site. You will need 
+administrative rights on the NT box to run netmon.
+</para>
+
+<para>
+To install Netmon on a Windows 9x box install the network monitor agent 
+from the Windows 9x CD (\admin\nettools\netmon).  There is a readme 
+file located with the netmon driver files on the CD if you need 
+information on how to do this.  Copy the files from a working 
+Netmon installation.
+</para> 
+
+</sect1>
+
+<sect1>
+<title>Useful URL's</title>
+<itemizedlist>
+
+<listitem><para>Home of Samba site <ulink url="http://samba.org">
+      http://samba.org</ulink>. We have a mirror near you !</para></listitem>
+
+<listitem><para> The <emphasis>Development</emphasis> document 
+on the Samba mirrors might mention your problem. If so,
+it might mean that the developers are working on it.</para></listitem>
+
+<listitem><para>See how Scott Merrill simulates a BDC behavior at 
+       <ulink url="http://www.skippy.net/linux/smb-howto.html">
+       http://www.skippy.net/linux/smb-howto.html</ulink>. </para></listitem>
+
+<listitem><para>Although 2.0.7 has almost had its day as a PDC, David Bannon will
+       keep the 2.0.7 PDC pages at <ulink url="http://bioserve.latrobe.edu.au/samba">
+       http://bioserve.latrobe.edu.au/samba</ulink> going for a while yet.</para></listitem>
+
+<listitem><para>Misc links to CIFS information 
+       <ulink url="http://samba.org/cifs/">http://samba.org/cifs/</ulink></para></listitem>
+
+<listitem><para>NT Domains for Unix <ulink url="http://mailhost.cb1.com/~lkcl/ntdom/">
+       http://mailhost.cb1.com/~lkcl/ntdom/</ulink></para></listitem>
+
+<listitem><para>FTP site for older SMB specs: 
+       <ulink url="ftp://ftp.microsoft.com/developr/drg/CIFS/">
+       ftp://ftp.microsoft.com/developr/drg/CIFS/</ulink></para></listitem>
+
+</itemizedlist>
+
+</sect1>
+
+<sect1>
+<title>Getting help from the mailing lists</title>
+
+<para>
+There are a number of Samba related mailing lists. Go to <ulink 
+url="http://samba.org">http://samba.org</ulink>, click on your nearest mirror
+and then click on <command>Support</command> and then click on <command>
+Samba related mailing lists</command>.
+</para>
+
+<para>
+For questions relating to Samba TNG go to
+<ulink url="http://www.samba-tng.org/">http://www.samba-tng.org/</ulink> 
+It has been requested that you don't post questions about Samba-TNG to the
+main stream Samba lists.</para>
+ 
+<para>
+If you post a message to one of the lists please observe the following guide lines :
+</para>
+
+<itemizedlist>
+
+<listitem><para> 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 time lines are 'best guess' and nothing more.
+</para></listitem>
+
+<listitem><para> Always mention what version of samba you are using and what 
+operating system its running under. You should probably list the
+relevant sections of your &smb.conf; file, at least the options 
+in [global] that affect PDC support.</para></listitem>
+
+<listitem><para>In addition to the version, if you obtained Samba via
+CVS mention the date when you last checked it out.</para></listitem>
+
+<listitem><para> Try and make your question clear and brief, lots of long, 
+convoluted questions get deleted before	they are completely read ! 
+Don't post html encoded messages (if you can select colour or font 
+size its html).</para></listitem>
+
+<listitem><para> If you run one of those nifty 'I'm on holidays' things when 
+you are away, make sure its configured	to not answer mailing lists.
+</para></listitem> 
+
+<listitem><para> Don't cross post. Work out which is the best list to post to 
+and see what happens, i.e. don't 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. 
+Often someone will see a message and thinking it would be better dealt 
+with on another, 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.  
+Please don't send the entire log but enough to give the context of the 
+error messages.</para></listitem>
+
+<listitem><para>(Possibly) If you have a complete netmon trace ( from the opening of 
+the pipe to the error ) you can send the *.CAP file as well.</para></listitem> 
+    
+<listitem><para>Please think carefully before attaching a document to an email.
+Consider pasting the relevant parts into the body of the message. The samba
+mailing lists go to a huge number of people, do they all need a copy of your 
+smb.conf in their attach directory?</para></listitem>
+
+</itemizedlist>
+
+</sect1>
+
+<sect1>
+<title>How to get off the mailinglists</title>
+
+<para>To have your name removed from a samba mailing list, go to the
+same place you went to to get on it. Go to <ulink 
+url="http://lists.samba.org/">http://lists.samba.org</ulink>, 
+click on your nearest mirror and then click on <command>Support</command> and 
+then click on <command> Samba related mailing lists</command>. Or perhaps see 
+<ulink url="http://lists.samba.org/mailman/roster/samba-ntdom">here</ulink>
+</para>
+
+<para>
+Please don't post messages to the list asking to be removed, you will just
+be referred to the above address (unless that process failed in some way...)
+</para>
+
+</sect1>
+
+</chapter>
diff --git a/docs/docbook/projdoc/Samba-PDC-HOWTO.sgml b/docs/docbook/projdoc/Samba-PDC-HOWTO.sgml
index a0927ec888..775e573aed 100644
--- a/docs/docbook/projdoc/Samba-PDC-HOWTO.sgml
+++ b/docs/docbook/projdoc/Samba-PDC-HOWTO.sgml
@@ -19,11 +19,6 @@ Samba as an NT4 or Win2k Primary Domain Controller
 </title>
 
 
-<!-- **********************************************************
-
-     Prerequisite Reading
-
-*************************************************************** -->
 <sect1>
 <title>Prerequisite Reading</title>
 
@@ -32,8 +27,7 @@ Before you continue reading in this chapter, please make sure
 that you are comfortable with configuring basic files services
 in smb.conf and how to enable and administer password 
 encryption in Samba.  Theses two topics are covered in the
-<ulink url="smb.conf.5.html"><filename>smb.conf(5)</filename></ulink> 
-manpage.
+&smb.conf; manpage.
 </para>
 
 
@@ -41,11 +35,6 @@ manpage.
 
 
 
-<!-- **********************************************************
-
-     Background Information
-
-*************************************************************** -->
 <sect1>
 <title>
 Background
@@ -160,12 +149,6 @@ concepts.
 </sect1>
 
 
-<!-- **********************************************************
-
-     Configuring the Samba PDC
-
-*************************************************************** -->
-
 <sect1>
 <title>Configuring the Samba Domain Controller</title>
 
@@ -173,12 +156,11 @@ concepts.
 The first step in creating a working Samba PDC is to 
 understand the parameters necessary in smb.conf. Here we
 attempt to explain the parameters that are covered in
-<ulink url="smb.conf.5.html"> the smb.conf
-man page</ulink>.
+the &smb.conf; man page.
 </para>
 
 <para>
-Here is an example <filename>smb.conf</filename> for acting as a PDC:
+Here is an example &smb.conf; for acting as a PDC:
 </para>
 
 <para><programlisting>
@@ -234,7 +216,7 @@ There are a couple of points to emphasize in the above configuration.
 <itemizedlist>
 	<listitem><para>
 	Encrypted passwords must be enabled.  For more details on how 
-	to do this, refer to <link linkend="passdb">ENCRYPTION.html</link>.
+	to do this, refer to <link linkend="passdb">the User Database chapter</link>.
 	</para></listitem>
 	
 	<listitem><para>
@@ -518,457 +500,123 @@ version of Windows.
 	(i.e., you must supply a Samba administrative account when
 	prompted).</para>
 </listitem>
+
+<listitem><para><emphasis>Samba</emphasis</para>
+	<para>Joining a samba client to a domain is documented in 
+	the <link linkend="domain-member">Domain Member</link> chapter.
+</para></listitem>
 </itemizedlist>
 
 </sect2>
 </sect1>
-<!-- **********************************************************
-
-     Common Problems
-
-*************************************************************** -->
 
 <sect1>
 <title>Common Problems and Errors</title>
 
+<sect2>
+<title>I cannot include a '$' in a machine name</title>
 <para>
+A 'machine name' in (typically) <filename>/etc/passwd</filename> 	
+of the machine name with a '$' appended. FreeBSD (and other BSD 
+systems?) won't create a user with a '$' in their name.
 </para>
-<itemizedlist>
-<listitem>
-	<para>
-	<emphasis>I cannot include a '$' in a machine name.</emphasis>
-	</para>
-    
-	<para>
-	A 'machine name' in (typically) <filename>/etc/passwd</filename> 	
-	of the machine name with a '$' appended. FreeBSD (and other BSD 
-	systems?) won't create a user with a '$' in their name.
-	</para>
-
-	<para>
-	The problem is only in the program used to make the entry, once 
-	made, it works perfectly. So create a user without the '$' and 
-	use <command>vipw</command> to edit the entry, adding the '$'. Or create 
-	the whole entry with vipw if you like, make sure you use a 
-	unique User ID !
-	</para>
-</listitem>
-  
-<listitem>
-	<para>
-	<emphasis>I get told "You already have a connection to the Domain...." 
-	or "Cannot join domain, the credentials supplied conflict with an 
-	existing set.." when creating a machine trust account.</emphasis>
-	</para>
-
-	<para>
-	This happens if you try to create a machine trust account from the 
-	machine itself and already have a connection (e.g. mapped drive) 
-	to a share (or IPC$) on the Samba PDC.  The following command
-	will remove all network drive connections:
-	</para>
-
-	<para>
-	<prompt>C:\WINNT\></prompt> <command>net use * /d</command>
-	</para>
-
-	<para>
-	Further, if the machine is a already a 'member of a workgroup' that 
-	is the same name as the domain you are joining (bad idea) you will 
-	get this message.  Change the workgroup name to something else, it 
-	does not matter what, reboot, and try again.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-	<emphasis>The system can not log you on (C000019B)....</emphasis>
-	</para>
-
-	<para>I joined the domain successfully but after upgrading 
-	to a newer version of the Samba code I get the message, "The system 
-	can not log you on (C000019B), Please try again or consult your 
-	system administrator" when attempting to logon.
-	</para>
-
-	<para>
-	This occurs when the domain SID stored in the secrets.tdb database
-	is changed. The most common cause of a change in domain SID is when
-	the domain name and/or the server name (netbios name) is changed.
- 	The only way to correct the problem is to restore the original domain 
-	SID or remove the domain client from the domain and rejoin. The domain
-	SID may be reset using either the smbpasswd or rpcclient utilities.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-	<emphasis>The machine trust account for this computer either does not 
-	exist or is not accessible.</emphasis>
-	</para>
-
-	<para>
-	When I try to join the domain I get the message "The machine account 
-	for this computer either does not exist or is not accessible". What's 
-	wrong?
-	</para>
-
-	<para>
-	This problem is caused by the PDC not having a suitable machine trust account. 
-	If you are using the <parameter>add user script</parameter> method to create 
-	accounts then this would indicate that it has not worked. Ensure the domain 
-	admin user system is working.
-	</para>
-
-	<para>
-	Alternatively if you are creating account entries manually then they 
-	have not been created correctly. Make sure that you have the entry 
-	correct for the machine trust account in smbpasswd file on the Samba PDC. 
-	If you added the account using an editor rather than using the smbpasswd 
-	utility, make sure that the account name is the machine NetBIOS name 
-	with a '$' appended to it ( i.e. computer_name$ ). There must be an entry 
-	in both /etc/passwd and the smbpasswd file. Some people have reported 
-	that inconsistent subnet masks between the Samba server and the NT 
-	client have caused this problem.   Make sure that these are consistent 
-	for both client and server.
-	</para>
-</listitem>
-
-<listitem>
-	<para>
-	<emphasis>When I attempt to login to a Samba Domain from a NT4/W2K workstation,
-	I get a message about my account being disabled.</emphasis>
-	</para>
-
-	<para>
-	This problem is caused by a PAM related bug in Samba 2.2.0.  This bug is 
-	fixed in 2.2.1.  Other symptoms could be unaccessible shares on 
-	NT/W2K member servers in the domain or the following error in your smbd.log:
-	passdb/pampass.c:pam_account(268) PAM: UNKNOWN ERROR for User: %user%
-	</para>
- 
-	<para>
-	At first be ensure to enable the useraccounts with <command>smbpasswd -e 
-	%user%</command>, this is normally done, when you create an account.
-	</para>
-
-	<para>
-	In order to work around this problem in 2.2.0, configure the 
-	<parameter>account</parameter> control flag in 
-	<filename>/etc/pam.d/samba</filename> file as follows:
-	</para> 
-
-	<para><programlisting>
-	account required        pam_permit.so
-	</programlisting></para>
-
-	<para>
-	If you want to remain backward compatibility to samba 2.0.x use
-	<filename>pam_permit.so</filename>, it's also possible to use 
-	<filename>pam_pwdb.so</filename>. There are some bugs if you try to 
-	use <filename>pam_unix.so</filename>, if you need this, be ensure to use
-	the most recent version of this file.
-	</para>
-</listitem>
-</itemizedlist>
-
-</sect1>
-
-<!-- **********************************************************
-
-     Getting Help
-
-*************************************************************** -->
-
-
-<sect1>
-<title>What other help can I get? </title>
 
 <para>
-There are many sources of information available in the form 
-of mailing lists, RFC's and documentation.  The docs that come 
-with the samba distribution contain very good explanations of 
-general SMB topics such as browsing.</para> 
-
-<itemizedlist>
-<listitem>
-	<para>
-	<emphasis>What are some diagnostics tools I can use to debug the domain logon 
-	process and where can I	find them?</emphasis>
-	</para>
-
-   <para>
-	One of the best diagnostic tools for debugging problems is Samba itself.  
-	You can use the -d option for both smbd and nmbd to specify what 
-	'debug level' at which to run.  See the man pages on smbd, nmbd  and 
-	smb.conf for more information on debugging options.  The debug 
-	level can range from 1 (the default) to 10 (100 for debugging passwords).
-	</para>
-	
-	<para>
-	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 smbd / nmbd process.  In order to attach gdb to an smbd 
-	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, on the first time you join the domain) to 
-	generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation 
-	maintains an open connection, and therefore there will be an smbd 
-	process running (assuming that you haven't set a really short smbd 
-	idle timeout)  So, in between pressing ctrl alt delete, and actually 
-	typing in your password, you can gdb attach and continue.
-	</para>
-
-	<para>
-	Some useful samba commands worth investigating:
-	</para>
-	
-	<itemizedlist>
-		<listitem><para>testparam | more</para></listitem>
-		<listitem><para>smbclient -L //{netbios name of server}</para></listitem>
-	</itemizedlist>
-    
-	<para>
-	An SMB enabled version of tcpdump is available from 
-	<ulink url="http://www.tcpdump.org/">http://www.tcpdup.org/</ulink>.
-	Ethereal, another good packet sniffer for Unix and Win32
-	hosts, can be downloaded from <ulink 
-	url="http://www.ethereal.com/">http://www.ethereal.com</ulink>.
-	</para>
-	
-	<para>
-	For tracing things on the Microsoft Windows NT, Network Monitor 
-	(aka. netmon) is available on the Microsoft Developer Network CD's, 
-	the Windows NT Server install CD and the SMS CD's.  The version of 
-	netmon that ships with SMS allows for dumping packets between any two 
-	computers (i.e. placing the network interface in promiscuous mode).  
-	The version on the NT Server install CD will only allow monitoring 
-	of network traffic directed to the local NT box and broadcasts on the 
-	local subnet.  Be aware that Ethereal can read and write netmon 
-	formatted files.
-	</para>
-</listitem>
-
-
-<listitem>
-	<para>
-	<emphasis>How do I install 'Network Monitor' on an NT Workstation 
-	or a Windows 9x box?</emphasis>
-	</para>
-
-	<para>
-	Installing netmon on an NT workstation requires a couple 
-	of steps.  The following are 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 version of 
-	Windows NT / Netmon.  You will need both the Microsoft Windows 
-	NT Server 4.0 Install CD and the Workstation 4.0 Install CD.
-	</para> 
-
-	<para>
-	Initially you will need to install 'Network Monitor Tools and Agent' 
-	on the NT Server.  To do this 
-	</para>
-
-	<itemizedlist>
-		<listitem><para>Goto Start - Settings - Control Panel - 
-		Network - Services - Add </para></listitem>
-		
-		<listitem><para>Select the 'Network Monitor Tools and Agent' and 
-		click on 'OK'.</para></listitem> 
-		
-		<listitem><para>Click 'OK' on the Network Control Panel.
-		</para></listitem> 
-		
-		<listitem><para>Insert the Windows NT Server 4.0 install CD 
-		when prompted.</para></listitem> 
-	</itemizedlist>
-
-	<para>
-	At this point the Netmon files should exist in 
-	<filename>%SYSTEMROOT%\System32\netmon\*.*</filename>.    
-	Two subdirectories exist as well, <filename>parsers\</filename> 
-	which contains the necessary DLL's for parsing the netmon packet 
-	dump, and <filename>captures\</filename>.
-	</para>
-
-	<para>
-	In order to install the Netmon tools on an NT Workstation, you will 
-	first need to install the 'Network  Monitor Agent' from the Workstation 
-	install CD.
-	</para>
-
-	<itemizedlist>
-		<listitem><para>Goto Start - Settings - Control Panel - 
-		Network - Services - Add</para></listitem> 
-
-		<listitem><para>Select the 'Network Monitor Agent' and click 
-		on 'OK'.</para></listitem> 
-		
-		<listitem><para>Click 'OK' on the Network Control Panel.
-		</para></listitem> 
-		
-		<listitem><para>Insert the Windows NT Workstation 4.0 install 
-		CD when prompted.</para></listitem> 
-	</itemizedlist>
-
-
-	<para>
-	Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.* 
-	to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set 
-	permissions as  you deem appropriate for your site. You will need 
-	administrative rights on the NT box to run netmon.
-	</para>
-
-	<para>
-	To install Netmon on a Windows 9x box install the network monitor agent 
-	from the Windows 9x CD (\admin\nettools\netmon).  There is a readme 
-	file located with the netmon driver files on the CD if you need 
-	information on how to do this.  Copy the files from a working 
-	Netmon installation.
-	</para> 
-</listitem>
-
-
-
-
-<listitem>
-	<para>
-	The following is a list if helpful URLs and other links:
-	</para>
-
-	<itemizedlist>
-
- 	<listitem><para>Home of Samba site <ulink url="http://samba.org">
-        http://samba.org</ulink>. We have a mirror near you !</para></listitem>
-
-	<listitem><para> The <emphasis>Development</emphasis> document 
-	on the Samba mirrors might mention your problem. If so,
-	it might mean that the developers are working on it.</para></listitem>
- 
-	<listitem><para>See how Scott Merrill simulates a BDC behavior at 
-        <ulink url="http://www.skippy.net/linux/smb-howto.html">
-        http://www.skippy.net/linux/smb-howto.html</ulink>. </para></listitem>
-
-	<listitem><para>Although 2.0.7 has almost had its day as a PDC, David Bannon will
-        keep the 2.0.7 PDC pages at <ulink url="http://bioserve.latrobe.edu.au/samba">
-        http://bioserve.latrobe.edu.au/samba</ulink> going for a while yet.</para></listitem>
-
-	<listitem><para>Misc links to CIFS information 
-        <ulink url="http://samba.org/cifs/">http://samba.org/cifs/</ulink></para></listitem>
-
-	<listitem><para>NT Domains for Unix <ulink url="http://mailhost.cb1.com/~lkcl/ntdom/">
-        http://mailhost.cb1.com/~lkcl/ntdom/</ulink></para></listitem>
-
-	<listitem><para>FTP site for older SMB specs: 
-        <ulink url="ftp://ftp.microsoft.com/developr/drg/CIFS/">
-        ftp://ftp.microsoft.com/developr/drg/CIFS/</ulink></para></listitem>
-
-	</itemizedlist>
-</listitem>
-</itemizedlist>
-
-
-<itemizedlist>
-<listitem>
-	<para>
-	<emphasis>How do I get help from the mailing lists?</emphasis>
-	</para>
-
-	<para>
-	There are a number of Samba related mailing lists. Go to <ulink 
-	url="http://samba.org">http://samba.org</ulink>, click on your nearest mirror
-	and then click on <command>Support</command> and then click on <command>
-	Samba related mailing lists</command>.
-	</para>
-
-	<para>
-	For questions relating to Samba TNG go to
-	<ulink url="http://www.samba-tng.org/">http://www.samba-tng.org/</ulink> 
-	It has been requested that you don't post questions about Samba-TNG to the
-	main stream Samba lists.</para>
-	 
-	<para>
-	If you post a message to one of the lists please observe the following guide lines :
-	</para>
-
-	<itemizedlist>
+The problem is only in the program used to make the entry, once 
+made, it works perfectly. So create a user without the '$' and 
+use <command>vipw</command> to edit the entry, adding the '$'. Or create 
+the whole entry with vipw if you like, make sure you use a 
+unique User ID !
+</para>
+</sect2>
 
-	<listitem><para> 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 time lines are 'best guess' and nothing more.
-		</para></listitem>
+<sect2>
+<title>I get told "You already have a connection to the Domain...." 
+or "Cannot join domain, the credentials supplied conflict with an 
+existing set.." when creating a machine trust account.</title>
 
-	<listitem><para> Always mention what version of samba you are using and what 
-		operating system its running under. You should probably list the
-        relevant sections of your smb.conf file, at least the options 
-        in [global] that affect PDC support.</para></listitem>
+<para>
+This happens if you try to create a machine trust account from the 
+machine itself and already have a connection (e.g. mapped drive) 
+to a share (or IPC$) on the Samba PDC.  The following command
+will remove all network drive connections:
+</para>
 
-    <listitem><para>In addition to the version, if you obtained Samba via
-        CVS mention the date when you last checked it out.</para></listitem>
+<para>
+<prompt>C:\WINNT\></prompt> <command>net use * /d</command>
+</para>
 
-	<listitem><para> Try and make your question clear and brief, lots of long, 
-		convoluted questions get deleted before	they are completely read ! 
-		Don't post html encoded messages (if you can select colour or font 
-		size its html).</para></listitem>
+<para>
+Further, if the machine is a already a 'member of a workgroup' that 
+is the same name as the domain you are joining (bad idea) you will 
+get this message.  Change the workgroup name to something else, it 
+does not matter what, reboot, and try again.
+</para>
+</sect2>
 
-	<listitem><para> If you run one of those nifty 'I'm on holidays' things when 
-		you are away, make sure its configured	to not answer mailing lists.
-		</para></listitem> 
+<sect2>
+<title>The system can not log you on (C000019B)....</title>
 
-	<listitem><para> Don't cross post. Work out which is the best list to post to 
-		and see what happens, i.e. don't 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. 
-		Often someone will see a message and thinking it would be better dealt 
-		with on another, will forward it on for you.</para></listitem>
+<para>I joined the domain successfully but after upgrading 
+to a newer version of the Samba code I get the message, "The system 
+can not log you on (C000019B), Please try again or consult your 
+system administrator" when attempting to logon.
+</para>
 
-    <listitem><para>You might include <emphasis>partial</emphasis>
-        log files written at a debug level set to as much as 20.  
-        Please don't send the entire log but enough to give the context of the 
-        error messages.</para></listitem>
+<para>
+This occurs when the domain SID stored in the secrets.tdb database
+is changed. The most common cause of a change in domain SID is when
+the domain name and/or the server name (netbios name) is changed.
+The only way to correct the problem is to restore the original domain 
+SID or remove the domain client from the domain and rejoin. The domain
+SID may be reset using either the smbpasswd or rpcclient utilities.
+</para>
+</sect2>
 
-    <listitem><para>(Possibly) If you have a complete netmon trace ( from the opening of 
-        the pipe to the error ) you can send the *.CAP file as well.</para></listitem> 
+<sect2>
+<title>The machine trust account for this computer either does not 
+exist or is not accessible.</title>
 
-    <listitem><para>Please think carefully before attaching a document to an email.
-        Consider pasting the relevant parts into the body of the message. The samba
-        mailing lists go to a huge number of people, do they all need a copy of your 
-        smb.conf in their attach directory?</para></listitem>
+<para>
+When I try to join the domain I get the message "The machine account 
+for this computer either does not exist or is not accessible". What's 
+wrong?
+</para>
 
-	</itemizedlist>
-</listitem>
+<para>
+This problem is caused by the PDC not having a suitable machine trust account. 
+If you are using the <parameter>add user script</parameter> method to create 
+accounts then this would indicate that it has not worked. Ensure the domain 
+admin user system is working.
+</para>
 
+<para>
+Alternatively if you are creating account entries manually then they 
+have not been created correctly. Make sure that you have the entry 
+correct for the machine trust account in smbpasswd file on the Samba PDC. 
+If you added the account using an editor rather than using the smbpasswd 
+utility, make sure that the account name is the machine NetBIOS name 
+with a '$' appended to it ( i.e. computer_name$ ). There must be an entry 
+in both /etc/passwd and the smbpasswd file. Some people have reported 
+that inconsistent subnet masks between the Samba server and the NT 
+client have caused this problem.   Make sure that these are consistent 
+for both client and server.
+</para>
+</sect2>
 
-<listitem>
-	<para>
-	<emphasis>How do I get off the mailing lists?</emphasis>
-	</para>
+<sect2>
+<title>When I attempt to login to a Samba Domain from a NT4/W2K workstation,
+I get a message about my account being disabled.</title>
 
-	<para>To have your name removed from a samba mailing list, go to the
-	same place you went to to get on it. Go to <ulink 
-	url="http://lists.samba.org/">http://lists.samba.org</ulink>, 
-	click on your nearest mirror and then click on <command>Support</command> and 
-	then click on <command> Samba related mailing lists</command>. Or perhaps see 
-	<ulink url="http://lists.samba.org/mailman/roster/samba-ntdom">here</ulink>
-	</para>
+<para>
+At first be ensure to enable the useraccounts with <command>smbpasswd -e 
+%user%</command>, this is normally done, when you create an account.
+</para>
 
-	<para>
-	Please don't post messages to the list asking to be removed, you will just
-	be referred to the above address (unless that process failed in some way...)
-	</para>
-</listitem>
-</itemizedlist>
+</sect2>
 
 </sect1>
 
-
-<!-- **********************************************************
-
-     Windows 9x domain control
-
-*************************************************************** -->
 <sect1>
 <title>Domain Control for Windows 9x/ME</title>
 
diff --git a/docs/docbook/projdoc/samba-doc.sgml b/docs/docbook/projdoc/samba-doc.sgml
index 6ed6e1a717..c6ef1c108c 100644
--- a/docs/docbook/projdoc/samba-doc.sgml
+++ b/docs/docbook/projdoc/samba-doc.sgml
@@ -33,6 +33,7 @@
 <!ENTITY NT4Migration SYSTEM "NT4Migration.sgml">
 <!ENTITY SWAT SYSTEM "SWAT.sgml">
 <!ENTITY Trusts SYSTEM "InterdomainTrusts.sgml">
+<!ENTITY problems SYSTEM "Problems.sgml">
 ]>
 
 <book id="Samba-HOWTO-Collection">
@@ -129,12 +130,13 @@ for various environments.
 
 <part id="Appendixes">
 <title>Appendixes</title>
-&SWAT;
+&Compiling;
 &NT4Migration;
-&SPEED;
 &Portability;
 &Other-Clients;
-&Compiling;
-&BUGS;
+&SWAT;
+&SPEED;
 &Diagnosis;
+&problems;
+&BUGS;
 </part>