From 50c54ae56f8e50efcdcf72b54b9aeef6201499ac Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Sat, 5 Apr 2003 07:42:29 +0000 Subject: Merging HEAD to 3.0.0 (This used to be commit 0160a8c1ea1aefbbbaaeeccb8f3ab3487d588df2) --- docs/docbook/projdoc/Diagnosis.sgml | 80 ++++++++++++++----------------------- 1 file changed, 29 insertions(+), 51 deletions(-) (limited to 'docs/docbook/projdoc/Diagnosis.sgml') diff --git a/docs/docbook/projdoc/Diagnosis.sgml b/docs/docbook/projdoc/Diagnosis.sgml index 1e2e6d7598..2a771c23d1 100644 --- a/docs/docbook/projdoc/Diagnosis.sgml +++ b/docs/docbook/projdoc/Diagnosis.sgml @@ -1,19 +1,7 @@ - - AndrewTridgell - - Samba Team -
tridge@samba.org
- - - - JelmerVernooij - - Samba Team -
jelmer@samba.org
- - + &author.tridge; + &author.jelmer; Wed Jan 15 @@ -92,10 +80,11 @@ best way to check this is with "testparm smb.conf" -Tests +The tests + +Diagnosing your samba server - -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 @@ -106,11 +95,9 @@ configuration file is faulty. Note: Your smb.conf file may be located in: /etc/samba Or in: /usr/local/samba/lib - - - -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 @@ -135,11 +122,9 @@ software. You will need to relax the rules to let in the workstation in question, perhaps by allowing access from another subnet (on Linux this is done via the ipfwadm program.) - - - -Test 3 + + Run the command "smbclient -L BIGSERVER" on the unix box. You should get a list of available shares back. @@ -218,10 +203,9 @@ network interface IP Address / Broadcast Address / Subnet Mask settings are correct and that Samba has correctly noted these in the log.nmb file. - + - -Test 4 + Run the command "nmblookup -B BIGSERVER __SAMBA__". You should get the @@ -241,10 +225,9 @@ one-line script that contains the right parameters and run that from inetd. - + - -Test 5 + run the command nmblookup -B ACLIENT '*' @@ -259,10 +242,9 @@ If ACLIENT doesn't resolve via DNS then use the IP address of the client in the above test. - + - -Test 6 + Run the command nmblookup -d 2 '*' @@ -296,10 +278,9 @@ This test will probably fail if your subnet mask and broadcast address are not correct. (Refer to TEST 3 notes above). - + - -Test 7 + Run the command smbclient //BIGSERVER/TMP. You should @@ -369,10 +350,9 @@ especially check that the amount of free disk space shown is correct when you type dir. - + - -Test 8 + On the PC type the command net view \\BIGSERVER. You will @@ -429,10 +409,9 @@ Check to see if the host is running tcp wrappers, and if so add an entry in the hosts.allow file for your client (or subnet, etc.) - + - -Test 9 + Run the command net use x: \\BIGSERVER\TMP. You should @@ -456,10 +435,9 @@ and you have encrypt passwords = no in smb.conf - + - -Test 10 + Run the command nmblookup -M TESTGROUP where @@ -476,10 +454,9 @@ sure you have preferred master = yes to ensure that an election is held at startup. - + - -Test 11 + From file manager try to browse the server. Your samba server should @@ -495,7 +472,8 @@ smb.conf file, or enable encrypted passwords AFTER compiling in support for encrypted passwords (refer to the Makefile). - + + @@ -507,7 +485,7 @@ sniff the problem. The official samba mailing list can be reached at samba@samba.org. To find out more about samba and how to subscribe to the mailing list check out the samba web page at -http://samba.org/samba +http://samba.org/samba/ -- cgit