From 3878085eca35d5c3b08761f61281de0b1b49ce2d Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Tue, 1 Jul 2003 22:58:52 +0000 Subject: regenerate docs (This used to be commit cc02d3bc170fe5c8c4474156edb6c83720a47aa0) --- docs/htmldocs/diagnosis.html | 25 ++++++++++++------------- 1 file changed, 12 insertions(+), 13 deletions(-) (limited to 'docs/htmldocs/diagnosis.html') diff --git a/docs/htmldocs/diagnosis.html b/docs/htmldocs/diagnosis.html index 97e7dead1b..ff3099ac72 100644 --- a/docs/htmldocs/diagnosis.html +++ b/docs/htmldocs/diagnosis.html @@ -1,5 +1,4 @@ - -Chapter 33. The samba checklist
Chapter 33. The samba checklist
Prev Part V. Troubleshooting Next

Chapter 33. The samba checklist

Andrew Tridgell

Samba Team

Jelmer R. Vernooij

The Samba Team

Wed Jan 15

Table of Contents

Introduction
Assumptions
The tests
Still having troubles?

Introduction

+Chapter 33. The Samba checklist

Chapter 33. The Samba checklist
Prev Part V. Troubleshooting Next

Chapter 33. The Samba checklist

Andrew Tridgell

Samba Team

Jelmer R. Vernooij

The Samba Team

Wed Jan 15

Table of Contents

Introduction
Assumptions
The tests
Still having troubles?

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 @@ -14,7 +13,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.

@@ -31,8 +30,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.

@@ -55,7 +54,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. @@ -123,7 +122,7 @@ the following smb.conf file entries: bind interfaces only = Yes

    In the above, no allowance has been made for any session requests that -will automatically translate to the loopback adaptor address 127.0.0.1. +will automatically translate to the loopback adapter address 127.0.0.1. To solve this problem change these lines to: 

     	hosts deny = ALL
@@ -146,7 +145,7 @@ to start smbd as a daemon, it can avoid a lot o
 And yet another possible cause for failure of this test is when the subnet mask
 and / or broadcast address settings are incorrect. Please check that the
 network interface IP Address / Broadcast Address / Subnet Mask settings are
-correct and that Samba has correctly noted these in the log.nmb file.
+correct and that Samba has correctly noted these in the log.nmbd file.

  2. Run the command nmblookup -B BIGSERVER __SAMBA__. You should get the IP address of your Samba server back. @@ -171,7 +170,7 @@ Run the command nmblookup -d 2 '*'

    This time we are trying the same as the previous test but are trying it via a broadcast to the default broadcast address. A number of -Netbios/TCPIP hosts on the network should respond, although Samba may +NetBIOS / TCP/IP hosts on the network should respond, although Samba may not catch all of the responses in the short time it listens. You should see got a positive name query response messages from several hosts. @@ -206,7 +205,7 @@ name then the service "tmp"

    If it says bad password then the likely causes are:

    1. - you have shadow passords (or some other password system) but didn't + you have shadow passwords (or some other password system) but didn't compile in support for them in smbd

    2. your valid users configuration is incorrect @@ -236,10 +235,10 @@ to choose one of them): fixup the nmbd installation

    3. add the IP address of BIGSERVER to the wins server box in the - advanced tcp/ip setup on the PC. + advanced TCP/IP setup on the PC.

    4. enable windows name resolution via DNS in the advanced section of - the tcp/ip setup + the TCP/IP setup

    5. add BIGSERVER to your lmhosts file on the PC.

    @@ -298,6 +297,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.

Prev Up Next
Part V. Troubleshooting Home Chapter 34. Analysing and solving samba problems
-- cgit