samba - May 2002 - smbclient, bug?

Hi,

Is this a bug?

By mistake, I was trying to connect to a samba server using
smbclient... but the samba server did not allow my client to
connect to the server, because of a "hosts allow" restriction.

I can understand smbclient reporting the first error:

  session request to ALKONOST failed (Not listening for calling name)

but, what is this "second" error,

  session request to *SMBSERVER failed (Not listening for calling name)


Where is this " *SMBSERVER " coming from ??? Something I can't
explain...


Here's the output with debug info.
> ./smbclient -L \\alkonost
INFO: Debug class all level = 10   (pid 394 from pid 394)
added interface ip=10.2.101.74 bcast=10.2.101.255 nmask=255.255.255.0
session request to ALKONOST failed (Not listening for calling name)
session request to *SMBSERVER failed (Not listening for calling name)


Thank you,
Pierre B.

On Wed, 22 May 2002, Pierre Belanger wrote:
> Hi,
> 
> Is this a bug?
> 
> By mistake, I was trying to connect to a samba server using
> smbclient... but the samba server did not allow my client to
> connect to the server, because of a "hosts allow" restriction.
> 
> I can understand smbclient reporting the first error:
> 
>   session request to ALKONOST failed (Not listening for calling name)
> 
> but, what is this "second" error,
> 
>   session request to *SMBSERVER failed (Not listening for calling name)
It is a built in default netbios name that SMB server use sometimes.










cheers, jerry
 ---------------------------------------------------------------------
 Hewlett-Packard                                     http://www.hp.com
 SAMBA Team                                       http://www.samba.org
 --                                            http://www.plainjoe.org
 "Sam's Teach Yourself Samba in 24 Hours" 2ed.      ISBN
0-672-32269-2
 --"I never saved anything for the swim back." Ethan Hawk in Gattaca--