From ca5759f796b153f702669942f7e01e498cc1170f Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Tue, 15 Oct 2002 18:14:31 +0000 Subject: make html (This used to be commit 39034207567c363a257f0aebd8ef22f15d98f451) --- docs/htmldocs/diagnosis.html | 93 +++++++++++++++++++------------------------- 1 file changed, 41 insertions(+), 52 deletions(-) (limited to 'docs/htmldocs/diagnosis.html') diff --git a/docs/htmldocs/diagnosis.html b/docs/htmldocs/diagnosis.html index 9cab114e49..5ddf6b7a49 100644 --- a/docs/htmldocs/diagnosis.html +++ b/docs/htmldocs/diagnosis.html @@ -8,13 +8,10 @@ NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.77">PrevNext 
Chapter 2. Diagnosing your samba serverChapter 23. Diagnosing your samba server

2.1. Introduction

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

2.2. Assumptions

23.2. Assumptions

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 @@ -140,17 +133,17 @@ CLASS="SECT1" >

2.3. Tests

23.3. Tests

2.3.1. Test 1

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

2.3.2. Test 2

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

2.3.3. Test 3

23.3.3. Test 3

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

2.3.4. Test 4

23.3.4. Test 4

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

2.3.5. Test 5

23.3.5. Test 5

run the command

2.3.6. Test 6

23.3.6. Test 6

Run the command

2.3.7. Test 7

23.3.7. Test 7

Run the command

2.3.8. Test 8

23.3.8. Test 8

On the PC type the command

2.3.9. Test 9

23.3.9. Test 9

Run the command

2.3.10. Test 10

23.3.10. Test 10

Run the command

2.3.11. Test 11

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

2.4. Still having troubles?

23.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 @@ -618,7 +611,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" >PrevHomeNext How to Install and Test SAMBASamba and other CIFS clientsIntegrating MS Windows networks with Samba