From 42efc1092dcb3042724e280c0bb18e813b3aac98 Mon Sep 17 00:00:00 2001
From: Jelmer Vernooij <jelmer@samba.org>
Date: Fri, 4 Oct 2002 16:36:40 +0000
Subject: Convert GOTCHAS to SGML (This used to be commit
 c48207ef0e219680d4e4102256c76189aaf73ebc)

---
 docs/htmldocs/diagnosis.html | 83 +++++++++++++++++++++++++++++++++-----------
 1 file changed, 62 insertions(+), 21 deletions(-)

(limited to 'docs/htmldocs/diagnosis.html')

diff --git a/docs/htmldocs/diagnosis.html b/docs/htmldocs/diagnosis.html
index e44474250d..9cab114e49 100644
--- a/docs/htmldocs/diagnosis.html
+++ b/docs/htmldocs/diagnosis.html
@@ -5,11 +5,10 @@
 >Diagnosing your samba server</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
 REL="HOME"
 TITLE="SAMBA Project Documentation"
-HREF="Samba-HOWTO.html"><LINK
+HREF="samba-project-documentation.html"><LINK
 REL="PREVIOUS"
 TITLE="How to Install and Test SAMBA"
 HREF="install.html"><LINK
@@ -70,13 +69,17 @@ WIDTH="100%"></DIV
 CLASS="CHAPTER"
 ><H1
 ><A
-NAME="DIAGNOSIS">Chapter 2. Diagnosing your samba server</H1
+NAME="DIAGNOSIS"
+></A
+>Chapter 2. Diagnosing your samba server</H1
 ><DIV
 CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN223">2.1. Introduction</H1
+NAME="AEN223"
+></A
+>2.1. Introduction</H1
 ><P
 >This file contains a list of tests you can perform to validate your
 Samba server. It also tells you what the likely cause of the problem
@@ -96,7 +99,9 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN228">2.2. Assumptions</H1
+NAME="AEN228"
+></A
+>2.2. Assumptions</H1
 ><P
 >In all of the tests I assume you have a Samba server called BIGSERVER
 and a PC called ACLIENT both in workgroup TESTGROUP. I also assume the
@@ -135,13 +140,17 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN238">2.3. Tests</H1
+NAME="AEN238"
+></A
+>2.3. Tests</H1
 ><DIV
 CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN240">2.3.1. Test 1</H2
+NAME="AEN240"
+></A
+>2.3.1. Test 1</H2
 ><P
 >In the directory in which you store your smb.conf file, run the command
 "testparm smb.conf". If it reports any errors then your smb.conf
@@ -161,7 +170,9 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN246">2.3.2. Test 2</H2
+NAME="AEN246"
+></A
+>2.3.2. Test 2</H2
 ><P
 >Run the command "ping BIGSERVER" from the PC and "ping ACLIENT" from
 the unix box. If you don't get a valid response then your TCP/IP
@@ -185,7 +196,9 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN252">2.3.3. Test 3</H2
+NAME="AEN252"
+></A
+>2.3.3. Test 3</H2
 ><P
 >Run the command "smbclient -L BIGSERVER" on the unix box. You
 should get a list of available shares back. </P
@@ -254,7 +267,9 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN267">2.3.4. Test 4</H2
+NAME="AEN267"
+></A
+>2.3.4. Test 4</H2
 ><P
 >Run the command "nmblookup -B BIGSERVER __SAMBA__". You should get the
 IP address of your Samba server back.</P
@@ -273,7 +288,9 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN272">2.3.5. Test 5</H2
+NAME="AEN272"
+></A
+>2.3.5. Test 5</H2
 ><P
 >run the command <B
 CLASS="COMMAND"
@@ -292,7 +309,9 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN278">2.3.6. Test 6</H2
+NAME="AEN278"
+></A
+>2.3.6. Test 6</H2
 ><P
 >Run the command <B
 CLASS="COMMAND"
@@ -324,7 +343,9 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN286">2.3.7. Test 7</H2
+NAME="AEN286"
+></A
+>2.3.7. Test 7</H2
 ><P
 >Run the command <B
 CLASS="COMMAND"
@@ -411,7 +432,9 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN312">2.3.8. Test 8</H2
+NAME="AEN312"
+></A
+>2.3.8. Test 8</H2
 ><P
 >On the PC type the command <B
 CLASS="COMMAND"
@@ -469,7 +492,9 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN329">2.3.9. Test 9</H2
+NAME="AEN329"
+></A
+>2.3.9. Test 9</H2
 ><P
 >Run the command <B
 CLASS="COMMAND"
@@ -484,14 +509,26 @@ and other config lines in smb.conf are correct.</P
 connect you as. To see if this is the problem add the line "user =
 USERNAME" to the [tmp] section of smb.conf where "USERNAME" is the
 username corresponding to the password you typed. If you find this
-fixes things you may need the username mapping option.</P
+fixes things you may need the username mapping option. </P
+><P
+>It might also be the case that your client only sends encrypted passwords 
+and you have <B
+CLASS="COMMAND"
+>encrypt passwords = no</B
+> in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>.
+Turn it back on to fix.</P
 ></DIV
 ><DIV
 CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN334">2.3.10. Test 10</H2
+NAME="AEN337"
+></A
+>2.3.10. Test 10</H2
 ><P
 >Run the command <B
 CLASS="COMMAND"
@@ -515,7 +552,9 @@ CLASS="SECT2"
 ><H2
 CLASS="SECT2"
 ><A
-NAME="AEN340">2.3.11. Test 11</H2
+NAME="AEN343"
+></A
+>2.3.11. Test 11</H2
 ><P
 >From file manager try to browse the server. Your samba server should
 appear in the browse list of your local workgroup (or the one you
@@ -541,7 +580,9 @@ CLASS="SECT1"
 ><H1
 CLASS="SECT1"
 ><A
-NAME="AEN345">2.4. Still having troubles?</H1
+NAME="AEN348"
+></A
+>2.4. Still having troubles?</H1
 ><P
 >Try the mailing list or newsgroup, or use the ethereal utility to
 sniff the problem. The official samba mailing list can be reached at
@@ -586,7 +627,7 @@ WIDTH="34%"
 ALIGN="center"
 VALIGN="top"
 ><A
-HREF="Samba-HOWTO.html"
+HREF="samba-project-documentation.html"
 ACCESSKEY="H"
 >Home</A
 ></TD
-- 
cgit