>Diagnosing your samba server</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
CLASS="CHAPTER"
><H1
><A
-NAME="DIAGNOSIS"
-></A
->Chapter 27. Diagnosing your samba server</H1
+NAME="DIAGNOSIS">Chapter 26. Diagnosing your samba server</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN3437"
-></A
->27.1. Introduction</H1
+NAME="AEN3378">26.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
><H1
CLASS="SECT1"
><A
-NAME="AEN3442"
-></A
->27.2. Assumptions</H1
+NAME="AEN3383">26.2. Assumptions</H1
><P
>In all of the tests it is assumed you have a Samba server called
BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.</P
><H1
CLASS="SECT1"
><A
-NAME="AEN3452"
-></A
->27.3. Tests</H1
+NAME="AEN3393">26.3. Tests</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN3454"
-></A
->27.3.1. Test 1</H2
+NAME="AEN3395">26.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
><H2
CLASS="SECT2"
><A
-NAME="AEN3460"
-></A
->27.3.2. Test 2</H2
+NAME="AEN3401">26.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
><H2
CLASS="SECT2"
><A
-NAME="AEN3466"
-></A
->27.3.3. Test 3</H2
+NAME="AEN3407">26.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
><H2
CLASS="SECT2"
><A
-NAME="AEN3481"
-></A
->27.3.4. Test 4</H2
+NAME="AEN3422">26.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
><H2
CLASS="SECT2"
><A
-NAME="AEN3486"
-></A
->27.3.5. Test 5</H2
+NAME="AEN3427">26.3.5. Test 5</H2
><P
>run the command <B
CLASS="COMMAND"
><H2
CLASS="SECT2"
><A
-NAME="AEN3492"
-></A
->27.3.6. Test 6</H2
+NAME="AEN3433">26.3.6. Test 6</H2
><P
>Run the command <B
CLASS="COMMAND"
><H2
CLASS="SECT2"
><A
-NAME="AEN3500"
-></A
->27.3.7. Test 7</H2
+NAME="AEN3441">26.3.7. Test 7</H2
><P
>Run the command <B
CLASS="COMMAND"
><H2
CLASS="SECT2"
><A
-NAME="AEN3526"
-></A
->27.3.8. Test 8</H2
+NAME="AEN3467">26.3.8. Test 8</H2
><P
>On the PC type the command <B
CLASS="COMMAND"
><H2
CLASS="SECT2"
><A
-NAME="AEN3543"
-></A
->27.3.9. Test 9</H2
+NAME="AEN3484">26.3.9. Test 9</H2
><P
>Run the command <B
CLASS="COMMAND"
><H2
CLASS="SECT2"
><A
-NAME="AEN3551"
-></A
->27.3.10. Test 10</H2
+NAME="AEN3492">26.3.10. Test 10</H2
><P
>Run the command <B
CLASS="COMMAND"
><H2
CLASS="SECT2"
><A
-NAME="AEN3557"
-></A
->27.3.11. Test 11</H2
+NAME="AEN3498">26.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
><H1
CLASS="SECT1"
><A
-NAME="AEN3562"
-></A
->27.4. Still having troubles?</H1
+NAME="AEN3503">26.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