[Samba] 'Not listening for calling name'

[Van Sickler, Jim]

> -----Original Message-----
> From: Vicky Clarke [mailto:vclarke at frontier.co.uk]
> Sent: Tuesday, July 09, 2002 10:21 AM
> To: samba at lists.samba.org
> Subject: [Samba] 'Not listening for calling name'
> 
> 
> 
> I'm having a strange problem with samba, 2.2.3a running on an 
> out-of-the-box SuSE 8.0 system. This is the first time I've set it up 
> (hence the dumb questions I was asking on here a day or two 
> ago). I've now 
> worked my way through diagnosis.txt and a couple of odd 
> netBIOS issues with 
> the NT4 PDC, and at last I have some shares set up that my 
> Windows client 
> can use quite happily. However smbclient on the local machine 
> comes up with 
> the following error:
> 
> wild:~ # smbclient //wild/art -U username%password
> 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 WILD failed (Not listening for calling name)
> session request to *SMBSERVER failed (Not listening for calling name)
> 
> smbd and nmbd are running as daemons; this is my smb.conf:
> 
> [global]
>          netbios name = SAMBA
>          workgroup = DOMAIN1
>          os level = 2
>          wins server = 172.17.1.2
>          hosts allow = 172.17.1.2 172.17.3. 127.
<snip>

If you're using 172.17.1.x, 172.17.2.x, 172.17.3.x
should this read:

          hosts allow = 172.17.1. 172.17.2. 172.17.3. 127.

It seems like you're not allowing all of the subnets
with the original entry.

Jim