From ff78c3bf5c3a73cf90f6517d9b2d6b8c12d22d68 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Tue, 18 Feb 2003 22:14:04 +0000 Subject: Regenerate (This used to be commit 1ab5a3b17feb677425bb1071357c3dbabcc46c7e) --- docs/htmldocs/diagnosis.html | 67 ++++++++++++++++++++++++++++++++------------ 1 file changed, 49 insertions(+), 18 deletions(-) (limited to 'docs/htmldocs/diagnosis.html') diff --git a/docs/htmldocs/diagnosis.html b/docs/htmldocs/diagnosis.html index a7b2e59436..0c71043074 100644 --- a/docs/htmldocs/diagnosis.html +++ b/docs/htmldocs/diagnosis.html @@ -5,8 +5,7 @@ >Diagnosing your samba server

Chapter 26. Diagnosing your samba server

Chapter 24. Diagnosing your samba server

26.1. Introduction

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

26.2. Assumptions

24.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.

26.3. Tests

24.3. Tests

26.3.1. Test 1

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

26.3.2. Test 2

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

26.3.3. Test 3

24.3.3. Test 3

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

26.3.4. Test 4

24.3.4. Test 4

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

26.3.5. Test 5

24.3.5. Test 5

run the command

26.3.6. Test 6

24.3.6. Test 6

Run the command

26.3.7. Test 7

24.3.7. Test 7

Run the command

26.3.8. Test 8

24.3.8. Test 8

On the PC type the command

26.3.9. Test 9

24.3.9. Test 9

Run the command

26.3.10. Test 10

24.3.10. Test 10

Run the command

26.3.11. Test 11

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

26.4. Still having troubles?

24.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