From ca9384623054fde64510edfbee3fc291f1d09fb9 Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Wed, 16 Jul 2003 05:42:10 +0000 Subject: Documentation Update for Beta3. (This used to be commit a88dc502cb3b6b2d905106675f50680bf22e2cfa) --- docs/htmldocs/diagnosis.html | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) (limited to 'docs/htmldocs/diagnosis.html') diff --git a/docs/htmldocs/diagnosis.html b/docs/htmldocs/diagnosis.html index ff3099ac72..473f5e6985 100644 --- a/docs/htmldocs/diagnosis.html +++ b/docs/htmldocs/diagnosis.html @@ -1,4 +1,5 @@ -Chapter 33. The Samba checklist

Chapter 33. The Samba checklist

Andrew Tridgell

Samba Team

Jelmer R. Vernooij

The Samba Team

Wed Jan 15

Introduction

+ +Chapter 33. The Samba checklist

Chapter 33. The Samba checklist

Andrew Tridgell

Samba Team

Jelmer R. Vernooij

The Samba Team

Wed Jan 15

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 is if it fails any one of these steps. If it passes all these tests @@ -13,7 +14,7 @@ to solve a problem. If you send one of the samba mailing lists an email saying "it doesn't work" and you have not followed this test procedure then you should not be surprised if your email is ignored. -

Assumptions

+

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.

@@ -30,8 +31,8 @@ following to smb.conf: path = /tmp read only = yes -

-

Note

+ +

Note

These tests assume version 3.0 or later of the samba suite. Some commands shown did not exist in earlier versions.

@@ -54,7 +55,7 @@ depending on how or if you specified logging in your smb.co

If you make changes to your smb.conf file while going through these test, don't forget to restart smbd and nmbd. -

The tests

Procedure 33.1. Diagnosing your samba server

  1. +

The tests

Procedure 33.1. Diagnosing your samba server

  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 configuration file is faulty. @@ -297,6 +298,6 @@ capability and is in user level security mode. In this case either set password server = Windows_NT_Machine in your smb.conf file, or make sure encrypted passwords is set to "yes". -

Still having troubles?

Read the chapter on +

Still having troubles?

Read the chapter on Analysing and Solving Problems.

-- cgit