samba - Feb 1999 - 'Not listening for calling name' error

Greetings!

I'm new to Samba and am having problems getting Samba V1.9.18p10
(RedHat V5.2) to respond to a login request. It's got to be something
simple that I've overlooked - it should work out of the box?

When testing a connection from the console using smbclient -L host123
I get the following (IP nos. and hostname changed):

--------------------------------------------------------------------
Added interface ip=XX.XX.180.22 bcast=XX.XX.180.255 nmask=255.255.255.0
Session request failed (131,129) with myname=HOST123 destname=HOST123
Not listening for calling name
Try to connect as another name (instead of HOST123)
You may find the -n option useful for this
--------------------------------------------------------------------

I can find no referance to setting up allowable 'calling names'.

'testparm' doesn't report any errors.

'smbd' and 'nmbd' are, of course, running.

The Samba server does not show up in 'Find -> Computer -> [hostname/IP
no]'
on a 'doz95 PC on the same network.

I'd appreciate any possible suggestions.

Regards

David

--
               *** be scene not herd ***

David Taylor                     Fac. of Biomedical & Health Sciences
IT Co-ordinator                  RMIT (Bundoora Campus)
mailto://david@rmit.edu.au       Melbourne  Australia.

On Wed, Feb 10 David Taylor wrote:
> I'm new to Samba and am having problems getting Samba V1.9.18p10
> (RedHat V5.2) to respond to a login request. It's got to be something
> simple that I've overlooked - it should work out of the box?
The bundled RedHat configurations definitely do _not_ work out of the box,
because of RH IP configuration idiocy. My RH5.0 system set itself up to
broadcast a request for a DNS server whenever it needed a hostname absent
from /etc/hosts. Of course, there _isn't_ a DNS server on my network (and
on most other SOHO nets I'd imagine) so large parts of TCP/IP broke,
including samba. I fixed this by removing /etc/resolv.conf. The RH Samba
setup doesn't seem to use keepalive packets either - result, if you reboot
your W95 system, Samba doesn't always realise it and netbios name
resolution screws up (enabling the socket option SO_KEEPALIVE and adding
'keep alive = 60' in smb.conf seemed to fix things for me).

Getting a complex Samba setup to work can be a complete pain in the bum,
even if the basic configuration is correct. I suggest you start by trying
to share the /tmp directory with as much security disabled as possible.
When this works, get ready to learn about all the interesting methods of
password encryption M$ uses.

Anybody who buys a RH distibution expecting not to do any Unix system admin
is in for a very nasty shock.

Best regards, Paul


Paul Sherwin Consulting
22 Monmouth Road, Oxford OX1 4TD, UK
Phone +44 (0)1865 721438
Fax +44 (0)1865 434331
Pager +44 (0)7666 797228