[Samba] 'Not listening for calling name'

[Joel Hammer]

Here is an old post I have in my files. This may relate to your problem.
Also, have you tried the -R option to smbclient to try to isolate the
problem?

Joel

============Previous "Solution"=====================
Subject: Re: Not listening for calling name
I managed to reproduce your error.
I don't know if this is your problem but I can reproduce it if I configure
my DNS improperly. ( I use BIND).
If I have an entry for battelship1 in my named.local file, say:
battlelship1  86400   IN      A       192.168.1.2
but don't have any such ip address in my  192.168.1 file, then this error is
reported by smbclient.
IT IS IMPORTANT to note the ping 192.168.1.2 and ping battleship1 work just
fine despite this DNS configuration error.
Also, if I have no entry for battlelship1 in named.local but have an entry
for 192.168.1.2 in my 192.168.1 file, and try:
smbclient -L 192.168.1.2
I get the same error message.
Joel
P.S. Don't worry. I wasn't spending any time trying to solve your problem. I
was spending time trying to arrange subnet browsing and finally
misconfigured my DNS so badly I got this error message.
=========Previous poster's complaint===================
On Wed, Sep 12, 2001 at 08:24:01PM +0100, root wrote:
> # ./smbclient -L battleship1 -d 4
> added interface ip=192.168.0.1 bcast=192.168.0.255 nmask=255.255.255.0
> Client started (version 2.2.1a).
> resolve_lmhosts: Attempting lmhosts lookup for name battleship1<0x20>
> startlmhosts: Can't open lmhosts file /usr/local/samba/lib/lmhosts. Error
> was
> No such file or directory
> resolve_hosts: Attempting host lookup for name battleship1<0x20>
> Connecting to 192.168.0.1 at port 139
> session request to BATTLESHIP1 failed (Not listening for calling name)
> resolve_lmhosts: Attempting lmhosts lookup for name battleship1<0x20>
> startlmhosts: Can't open lmhosts file /usr/local/samba/lib/lmhosts. Error
> was
> No such file or directory
> resolve_hosts: Attempting host lookup for name battleship1<0x20>
> Connecting to 192.168.0.1 at port 139
> session request to *SMBSERVER failed (Not listening for calling name)
>                                                                       
===============Current poster's problem======================
On Wed, Jul 10, 2002 at 10:56:47AM +0100, Vicky Clarke wrote:
> At 11:13 09/07/2002 -0700, Herb Lewis wrote:
> >You should probably be typing
> >
> >smbclient //samba/art
> >
> >since you specified the netbios name of the machine to be samba.
> >If the name samba is not in your /etc/hosts file (or DNS) you
> >would need to add the "-I wild" switch (assuming the DNS name
> >of your machine was wild
> 
> Nope, not even with the IP address:
> 
> smbclient //samba/art -I 172.17.1.3
> added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
> added interface ip=172.17.1.3 bcast=172.17.3.255 nmask=255.255.252.0
> session request to SAMBA failed (Not listening for calling name)
> session request to *SMBSERVER failed (Not listening for calling name)
> 
> I'm starting to think it must be something to do with my weird DNS setup 
> after all.
> 
> Vicky
> 
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba