Often, when you get the port 139 already in use error, another process
is watching that port and won't allow another process to play.
What do you see with:
netstat -an | grep 139 ?
Some kernels allow netstat -apn, which also shows the listening process.
The guilty process is often (x)inetd.
Joel
On Mon, Nov 25, 2002 at 02:58:13PM -0700, george auchampaugh
wrote:> HI,
>
> I am running Red Hat 7.2 on a PC. Until today I have been able to start
> smb. Now I am no longer able to start smb. When I start it with
> /etc/rc.d/init.d/smb start it say OK. However, when I execute
> /etc/rc.d/init.d/smb status it says that smbd is stopped, but nmbd is
> running. If I execute smbstatus it says "Failed to open byte range
> locking database, Can't initialize locking module - exiting." If I
look
> in the /var/log/samba/smbd.log it says "lib/util_sock.c:
> open_socket_in (824) bind failed on port 139 socket_addr=0.0.0.0
> (Address already in use).
>
> I have recently worked on the audio card and modem. I'm not sure if smb
> was working after installing modem.
>
> What gives? How do I correct problem?
>
> George
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: http://lists.samba.org/mailman/listinfo/samba