From 2e2a5d50eb0fcbfdab14e56d6150a1bd35d57f28 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Wed, 13 Nov 2002 15:34:49 +0000 Subject: Some more doc updates: - make - update status of docs document - move security_level to 'type of installation' part (This used to be commit 11ad39398e077c3901e63f31bcc6efb223854357) --- docs/htmldocs/diagnosis.html | 66 ++++++++++++++++++++++---------------------- 1 file changed, 33 insertions(+), 33 deletions(-) (limited to 'docs/htmldocs/diagnosis.html') diff --git a/docs/htmldocs/diagnosis.html b/docs/htmldocs/diagnosis.html index 976197c3bb..eaa550dc30 100644 --- a/docs/htmldocs/diagnosis.html +++ b/docs/htmldocs/diagnosis.html @@ -11,7 +11,7 @@ TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html">Chapter 26. Diagnosing your samba serverChapter 27. Diagnosing your samba server

26.1. Introduction

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

26.2. Assumptions

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

27.3. Tests

26.3.1. Test 1

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

26.3.2. Test 2

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

26.3.3. Test 3

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

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

27.3.5. Test 5

run the command

26.3.6. Test 6

27.3.6. Test 6

Run the command

26.3.7. Test 7

27.3.7. Test 7

Run the command

26.3.8. Test 8

27.3.8. Test 8

On the PC type the command

26.3.9. Test 9

27.3.9. Test 9

Run the command

26.3.10. Test 10

27.3.10. Test 10

Run the command

26.3.11. Test 11

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

26.4. Still having troubles?

27.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 @@ -641,7 +641,7 @@ WIDTH="34%" ALIGN="center" VALIGN="top" >Up