From owner-freebsd-questions@FreeBSD.ORG Wed Aug 20 21:26:31 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25DCC16A4BF for ; Wed, 20 Aug 2003 21:26:31 -0700 (PDT) Received: from lakemtao01.cox.net (lakemtao01.cox.net [68.1.17.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AD4343FA3 for ; Wed, 20 Aug 2003 21:26:28 -0700 (PDT) (envelope-from rjhjr@cox.net) Received: from kongemord.krig.net ([68.100.111.121]) by lakemtao01.cox.net (InterMail vM.5.01.06.04 201-253-122-130-104-20030726) with SMTP id <20030821042628.GDGF5378.lakemtao01.cox.net@kongemord.krig.net> for ; Thu, 21 Aug 2003 00:26:28 -0400 Received: by kongemord.krig.net (sSMTP sendmail emulation); Thu, 21 Aug 2003 00:26:27 -0400 From: "Bob Hall" Date: Thu, 21 Aug 2003 00:26:27 -0400 To: FreeBSD Questions List Message-ID: <20030821042626.GA433@kongemord.krig.net> Mail-Followup-To: FreeBSD Questions List Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-IMAPbase: 1061250701 5 X-UID: 5 Subject: Interpreting Samba messages X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Aug 2003 04:26:31 -0000 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