summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSamba Release Account <samba-bugs@samba.org>1997-08-26 07:56:00 +0000
committerSamba Release Account <samba-bugs@samba.org>1997-08-26 07:56:00 +0000
commit35df7e54b0eeb26ecdf2f64a288cd449c9652131 (patch)
treef151708cba1390465d899da6d6d8b67b80f51f27
parentb4fd930264d2b87bd97becd415bf5821d2ff0395 (diff)
downloadsamba-35df7e54b0eeb26ecdf2f64a288cd449c9652131.tar.gz
samba-35df7e54b0eeb26ecdf2f64a288cd449c9652131.tar.bz2
samba-35df7e54b0eeb26ecdf2f64a288cd449c9652131.zip
Advice about firewalls (step 1) and tcp wrappers (step 8). Dan
(This used to be commit e470dd55612558ae6f308c0a871e3c01e7dea4f7)
-rw-r--r--docs/textdocs/DIAGNOSIS.txt11
1 files changed, 10 insertions, 1 deletions
diff --git a/docs/textdocs/DIAGNOSIS.txt b/docs/textdocs/DIAGNOSIS.txt
index 5f20f61031..11eb91b2ff 100644
--- a/docs/textdocs/DIAGNOSIS.txt
+++ b/docs/textdocs/DIAGNOSIS.txt
@@ -69,7 +69,12 @@ run ping.
If you get a message saying "host not found" or similar then your DNS
software or /etc/hosts file is not correctly setup. It is possible to
run samba without DNS entries for the server and client, but I assume
-you do have correct entries for the remainder of these tests.
+you do have correct entries for the remainder of these tests.
+
+Another reason why ping might fail is if your host is running firewall
+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:
@@ -208,6 +213,10 @@ same fixes apply as they did for the "smbclient -L" test above. In
particular, make sure your "hosts allow" line is correct (see the man
pages)
+If you get "specified computer is not receiving requests" or similar
+it probably means that the host is not contactable via tcp services.
+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: