[Samba] bind failed on port 139
meyrick at hedge-analytics.com
Fri Apr 11 21:33:55 GMT 2003
-----BEGIN PGP SIGNED MESSAGE-----
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"
[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
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=126.96.36.199 bcast=188.8.131.52 nmask=255.255.255.0
Domain=[FAMILY] OS=[Unix] Server=[Samba 2.2.5]
- - - I can successfully ping localhost, my own fully qualified
host.domain.name (Ariel.Hedge-analytics.co.uk) & IP address (184.108.40.206).
- - - From the client I can ping the server on IP address (220.127.116.11) but
CANNOT ping using the fully qualified domain name
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.
- - --
-----BEGIN PGP SIGNATURE-----
Comment: trusted mail
-----END PGP SIGNATURE-----
More information about the samba