From f0e282ebf3e459c559bfc08f3e21fdebb2515621 Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Thu, 16 Jan 2003 02:20:27 +0000 Subject: * merge fixes for SGML syntax errors (does no one ever regenerate the docs?) * regenerate the docs * add some files from SAMBA_3_0 (This used to be commit 1af74785f334bd84b2d62e7fc2975f9477386acb) --- docs/htmldocs/diagnosis.html | 67 ++++++++++++-------------------------------- 1 file changed, 18 insertions(+), 49 deletions(-) (limited to 'docs/htmldocs/diagnosis.html') diff --git a/docs/htmldocs/diagnosis.html b/docs/htmldocs/diagnosis.html index eaa550dc30..a7b2e59436 100644 --- a/docs/htmldocs/diagnosis.html +++ b/docs/htmldocs/diagnosis.html @@ -5,7 +5,8 @@ >Diagnosing your samba server

Chapter 27. Diagnosing your samba server

Chapter 26. Diagnosing your samba server

27.1. Introduction

26.1. Introduction

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 @@ -95,9 +92,7 @@ CLASS="SECT1" >

27.2. Assumptions

26.2. Assumptions

In all of the tests it is assumed you have a Samba server called BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.

27.3. Tests

26.3. Tests

27.3.1. Test 1

26.3.1. Test 1

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 @@ -163,9 +154,7 @@ CLASS="SECT2" >

27.3.2. Test 2

26.3.2. Test 2

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 @@ -189,9 +178,7 @@ CLASS="SECT2" >

27.3.3. Test 3

26.3.3. Test 3

Run the command "smbclient -L BIGSERVER" on the unix box. You should get a list of available shares back.

27.3.4. Test 4

26.3.4. Test 4

Run the command "nmblookup -B BIGSERVER __SAMBA__". You should get the IP address of your Samba server back.

27.3.5. Test 5

26.3.5. Test 5

run the command

27.3.6. Test 6

26.3.6. Test 6

Run the command

27.3.7. Test 7

26.3.7. Test 7

Run the command

27.3.8. Test 8

26.3.8. Test 8

On the PC type the command

27.3.9. Test 9

26.3.9. Test 9

Run the command

27.3.10. Test 10

26.3.10. Test 10

Run the command

27.3.11. Test 11

26.3.11. Test 11

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 @@ -573,9 +544,7 @@ CLASS="SECT1" >

27.4. Still having troubles?

26.4. Still having troubles?

Try the mailing list or newsgroup, or use the ethereal utility to sniff the problem. The official samba mailing list can be reached at -- cgit