Interpreting Samba messages
Bob Hall
rjhjr at cox.net
Wed Aug 20 21:26:31 PDT 2003
I get the following messages at startup;
Aug 20 23:59:46 kongemord nmbd[284]: [2003/08/20 23:59:46, 0] nmbd/asyncdns.c:st
art_async_dns(148)
Aug 20 23:59:46 kongemord nmbd[284]: started asyncdns process 286
Aug 20 23:59:46 kongemord nmbd[284]: [2003/08/20 23:59:46, 0] lib/util_sock.c:op
en_socket_in(804)
Aug 20 23:59:46 kongemord nmbd[284]: bind failed on port 137 socket_addr = 0.0
.0.0.
Aug 20 23:59:46 kongemord nmbd[284]: Error = Address already in use
I would get similar messages for smbd, but I've configured it to bind
only to the internal interface.
sockstat shows
root nmbd 361 0 udp4 *:137 *:*
...
root inetd 203 5 udp4 *:137 *:*
(My firewall blocks external CIFS connections, BTW.)
Samba works fine, so this doesn't seem to be a problem. But I'm
puzzled, probably because I don't know much about this. I'm guessing
that the error message occurs because inetd got to the port first.
But I thought that binding to a port was a prerequesite for listening
at the port. So if binding failed, why is nmbd listening at *:137?
And why are both nmdb and inetd listening at the same port? I
thought you could have only one process listening at a port.
Bob Hall
More information about the freebsd-questions
mailing list