samba - Feb 2002 - generating error message on smbclient -L apollo

Hello,

When I run the 'smbclient -L apollo' command at the UNIX prompt a I get
an
error.

I have gone as far as I can in this DIAGNOSIS.txt file.   Does anyone have
any thoughts on what may be causing my problem ?

I have made my comments to the DIAGNOSIS.txt file via '---- davidw
{comment}' so you can see what I've done to date.


Also, I thought I'd pass on the output from the log.smbd file as it may
yield some insight.

% cat log.smbd

[2002/02/12 16:35:03, 1] smbd/server.c:main(689)
  smbd version 2.2.2 started.
  Copyright Andrew Tridgell 1992-1998
[2002/02/12 16:35:49, 0] lib/access.c:check_access(320)
  Denied connection from  (10.64.0.45)
[2002/02/12 16:35:49, 1] smbd/process.c:process_smb(852)
  Connection denied from 10.64.0.45
[2002/02/12 16:35:49, 0] smbd/connection.c:yield_connection(62)
  yield_connection: tdb_delete for name  failed with error Record does not
exist.
[2002/02/12 16:35:49, 0] lib/access.c:check_access(320)

Thanks


David Williams


==============================================================================================
>!=>!== DIAGNOSIS.txt for Samba release 2.2.0-alpha3 24 Mar 2001
>!=>Contributor:   Andrew Tridgell
>Updated:       November 1, 1999
>Subject:       DIAGNOSING YOUR SAMBA SERVER
>==========================================================================>
>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
>then it is probably working fine.
>
>You should do ALL the tests, in the order shown. I have tried to
>carefully choose them so later tests only use capabilities verified in
>the earlier tests.
>
>If you send me an email saying "it doesn't work" and you have
not
>followed this test procedure then you should not be surprised if I
>ignore your email.
>
>
>ASSUMPTIONS
Hello,

When I run the 'smbclient -L apollo' command at the UNIX prompt a I get
an
error.

I have gone as far as I can in this DIAGNOSIS.txt file.   Does anyone have
any thoughts on what may be causing my problem ?

I have made my comments to the DIAGNOSIS.txt file via '---- davidw
{comment}' so you can see what I've done to date.


Also, I thought I'd pass on the output from the log.smbd file as it may
yield some insight.

% cat log.smbd

[2002/02/12 16:35:03, 1] smbd/server.c:main(689)
  smbd version 2.2.2 started.
  Copyright Andrew Tridgell 1992-1998
[2002/02/12 16:35:49, 0] lib/access.c:check_access(320)
  Denied connection from  (10.64.0.45)
[2002/02/12 16:35:49, 1] smbd/process.c:process_smb(852)
  Connection denied from 10.64.0.45
[2002/02/12 16:35:49, 0] smbd/connection.c:yield_connection(62)
  yield_connection: tdb_delete for name  failed with error Record does not
exist.
[2002/02/12 16:35:49, 0] lib/access.c:check_access(320)

Thanks


David Williams


==============================================================================================
>!=>!== DIAGNOSIS.txt for Samba release 2.2.0-alpha3 24 Mar 2001
>!=>Contributor:   Andrew Tridgell
>Updated:       November 1, 1999
>Subject:       DIAGNOSING YOUR SAMBA SERVER
>==========================================================================>
>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
>then it is probably working fine.
>
>You should do ALL the tests, in the order shown. I have tried to
>carefully choose them so later tests only use capabilities verified in
>the earlier tests.
>
>If you send me an email saying "it doesn't work" and you have
not
>followed this test procedure then you should not be surprised if I
>ignore your email.
>
>
>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
>PC is running windows for workgroups with a recent copy of the
>microsoft tcp/ip stack. Alternatively, your PC may be running Windows
>95 or Windows NT (Workstation or Server).
>
>The procedure is similar for other types of clients.
>
>I also assume you know the name of an available share in your
>smb.conf. I will assume this share is called "tmp". You can add a
>"tmp" share like by adding the following to smb.conf:
>
>[tmp]
> comment = temporary files
> path = /tmp
> read only = yes
>
>
>THESE TESTS ASSUME VERSION 2.0.6 OR LATER OF THE SAMBA SUITE. SOME
>COMMANDS SHOWN DID NOT EXIST IN EARLIER VERSIONS
>
>Please pay attention to the error messages you receive. If any error
message
>reports that your server is being unfriendly you should first check that
you
>IP name resolution is correctly set up. eg: Make sure your /etc/resolv.conf
>file points to name servers that really do exist.
>
>Also, if you do not have DNS server access for name resolution please check
>that the settings for your smb.conf file results in "dns proxy =
no". The
>best way to check this is with "testparm smb.conf"
 
----davidw : DNS working properly
 
>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
>configuration file is faulty.
>
>Note:  Your smb.conf file may be located in: /etc
>       Or in:   /usr/local/samba/lib
>
 
---davidw : smb.conf in place.
 
 >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
>software is not correctly installed.
>
>Note that you will need to start a "dos prompt" window on the PC
to
>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.
>
>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.)
>
 
------davidw : ping works in -both- directions
 
>
>TEST 3:
>-------
>
>Run the command "smbclient -L BIGSERVER" on the unix box. You
>should get a list of available shares back.
>
 
---- davidw : IT FAILS HERE !
 
%smbclient -L apollo
added interface ip=10.64.0.45 bcast=10.64.1.255, nmask=255.255.254.0
session request to APOLLO failed (Not listenint for calling name)
session request to *SMBSERVER failed (Not listening for calling name)

You are in luck. This comes from the RecentFAQ doc in text docs.  You can
find these things by greping through the text files.

Joel


Not listening for calling name
 =============================
 > Session request failed (131,129) with myname=HOBBES
destname=CALVIN
 > Not listening for calling name

 If you get this when talking to a Samba box then it means that your
 global "hosts allow" or "hosts deny" settings are causing
the Samba
 server to refuse the connection.

 Look carefully at your "hosts allow" and "hosts deny" lines
in the
 global section of smb.conf.

 It can also be a problem with reverse DNS lookups not functioning
 correctly, leading to the remote host identity not being able to
 be confirmed, but that is less likely.  

on Tue, Feb 12, 2002 at 05:29:47PM -0800, Dave Williams
wrote:
> Hello,
> 
> >TEST 3:
> >-------
> >
> >Run the command "smbclient -L BIGSERVER" on the unix box. You
> >should get a list of available shares back.
> >
>  
> ---- davidw : IT FAILS HERE !
>  
> %smbclient -L apollo
> added interface ip=10.64.0.45 bcast=10.64.1.255, nmask=255.255.254.0
> session request to APOLLO failed (Not listenint for calling name)
> session request to *SMBSERVER failed (Not listening for calling name)

You are using a different netmask in those two hosts allow
statements. Could that account for it?

Joel

On Tue, Feb 12, 2002 at 06:50:47PM -0800, Dave Williams
wrote:
> 
> Thanks Joel,
> 
> The docs said to do the following :
> 
> hosts deny = ALL
> hosts allow = 10.64.0.45/35 127.0.0.1
> 
> But ... it kept failing.   However, when I did this  :
> 
> hosts deny = NONE
> hosts allow = 10.64.0.45/23 127.0.0.1
> 
> It got past it.  Weird, but it works.   
> 
> Thanks
> 
> -David W.
> 
>
=========================================================================>
> -----Original Message-----
> From: Joel Hammer [mailto:Joel@HammersHome.com]
> Sent: Tuesday, February 12, 2002 6:04 PM
> To: Dave Williams; samba@lists.samba.org
> Subject: Re: [Samba] generating error message on smbclient -L apollo
> 
> 
> You are in luck. This comes from the RecentFAQ doc in text docs.  You can
> find these things by greping through the text files.
> 
> Joel
> 
> 
> Not listening for calling name
>  =============================> 
>  > Session request failed (131,129) with myname=HOBBES
> destname=CALVIN
>  > Not listening for calling name
> 
>  If you get this when talking to a Samba box then it means that your
>  global "hosts allow" or "hosts deny" settings are
causing the Samba
>  server to refuse the connection.
> 
>  Look carefully at your "hosts allow" and "hosts deny"
lines in the
>  global section of smb.conf.
> 
>  It can also be a problem with reverse DNS lookups not functioning
>  correctly, leading to the remote host identity not being able to
>  be confirmed, but that is less likely.  
> 
> on Tue, Feb 12, 2002 at 05:29:47PM -0800, Dave Williams wrote:
> > Hello,
> > 
> > >TEST 3:
> > >-------
> > >
> > >Run the command "smbclient -L BIGSERVER" on the unix
box. You
> > >should get a list of available shares back.
> > >
> >  
> > ---- davidw : IT FAILS HERE !
> >  
> > %smbclient -L apollo
> > added interface ip=10.64.0.45 bcast=10.64.1.255, nmask=255.255.254.0
> > session request to APOLLO failed (Not listenint for calling name)
> > session request to *SMBSERVER failed (Not listening for calling name)

Here is my global. I seem not to have a hosts deny statement! I don't need
it because this daemon only listens to my internal interface NIC, and I have
a firewall that keeps out unwanted visitors. Without the hosts deny
statement, I am not really sure if I need the hosts allow statement, but, it
works.

Joel

On Tue, Feb 12, 2002 at 07:22:16PM -0800, Dave Williams wrote:
# Global parameters
[global]
	encrypt passwords = yes
	netbios name = HAMMER2
	interfaces = 192.168.0.2 
	security = SHARE
	log level = 3 
	wins server = jhammer6
	guest account = ftp
	hosts allow = 192.168. 24.182.146.18  127.0.0.1 127.0.0.2 
	strict sync = Yes
	veto files = /*.eml/*.nws/riched20.dll/
        veto files = /*.{*}/            
> 
> Must be typo as both were set to netmask of 23.
> 
> The problem (which has since been corrected) appeared to be with
> the line ...
> 
> hosts deny = ALL
> 
> Once I changed it to ...
> 
> hosts deny = NONE
> 
> It worked.   The crazy thing about it, though, was that the docs themselves
> specifically stated to set up 'hosts deny = ALL', then to specify
your
> 'hosts allow = {list of IP addresses}'.
> 
> Did you specify a 'hosts deny = ALL' followed by a line that listed
your IP
> addresses, or did you do it a different way ?
> 
>