[Samba] bind failed on port 139

[Meyrick Chapman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,
I have recently installed SuSE 8.1. Previously this workstation ran SuSE 7.2 
with Samba server without problems. Since the latest installation inet.d 
loads nmbd on boot but smbd fails. 

testparm /etc/samba/smb.conf  returns "Loaded sevices file is OK"

Log files
/var/log/samba/log.smbd shows: 

[2003/04/09 20:48:41, 0] lib/util_sock.c:open_socket_in(804)
  bind failed on port 139 socket_addr = 0.0.0.0.
  Error = Address already in use

nmblookup query to server results in following:

The only service listed in /etc/services to bind to port 139 is as follows: 
netbios-ssn	139/tcp		# NETBIOS Session Service
netbios-ssn	139/udp		# NETBIOS Session Service

/etc/inet.d shows:
entry in the inet.d file shows as follows
netbios-ssn stream tcp nowait root /usr/sbin/smbd smbd
netbios-ns dgram udp wait root /usr/sbin/nmbd nmbd

Smbclient confirms the server setup is correct as follows: 
Ariel:/home/meyrick # smbclient '\\Ariel\TMP'
added interface ip=62.190.243.241 bcast=62.190.243.255 nmask=255.255.255.0
Password:
Domain=[FAMILY] OS=[Unix] Server=[Samba 2.2.5]
smb: \>

Network
- - - I can successfully ping localhost, my own fully qualified 
host.domain.name (Ariel.Hedge-analytics.co.uk) & IP address (62.190.243.241). 
- - - From the client I can ping the server on IP address (62.190.243.241) but 
CANNOT ping using the fully qualified domain name 
(Ariel.hedge-analytics.co.uk) 

I have changed nothing on the client PC since installation of SuSE 8.1, so 
settings on the newly installed SuSE 8.1 probably at fault. Hostname & 
domain name are correctly set in the client PC running Windows 98. 

Thanks for your help. 

- - -- 
 Meyrick Chapman

-----BEGIN PGP SIGNATURE-----
Comment: trusted mail

iD8DBQE+lzTJKNEcTU/K/ggRAmIgAJ4/eiI+gY0PFeNybT3quLKK1tfWpACeMG+3
p5psqvuYaA/CFs8XT9F5bWA=
=LHOu
-----END PGP SIGNATURE-----