No samba, but 139 is already in use?

Chowroc · 07-07-2005, 01:59 AM

I didn't start samba, but the port 139 has been in use, what's that wrong?

Code:

tcp        0      0 192.168.0.11:139        0.0.0.0:*               LISTEN

And when I start samba, I can get:

Code:

[2005/07/07 14:29:24, 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

How can I know which program or process is using that port?

Thank you.

bathory · 07-07-2005, 02:03 AM

Run:

Code:

fuser -v -n tcp 139

Chowroc · 07-07-2005, 02:07 AM

Yes, I know what's wrong. Thank you very much.