From owner-freebsd-questions Wed Jan 5 11: 6:42 2000 Delivered-To: freebsd-questions@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id 5805015459 for ; Wed, 5 Jan 2000 11:06:30 -0800 (PST) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.9.3) id OAA16923; Wed, 5 Jan 2000 14:10:18 -0500 (EST) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <200001051910.OAA16923@cc942873-a.ewndsr1.nj.home.com> Subject: Re: [Allan Strand ] natd coexisting with rpc.statd+nfs In-Reply-To: <86g0wc1k94.fsf@linum.cofc.edu> from Allan Strand at "Jan 5, 2000 12:49:43 pm" To: stranda@cofc.edu (Allan Strand) Date: Wed, 5 Jan 2000 14:10:18 -0500 (EST) Cc: zeus@tetronsoftware.com (Gene Harris), freebsd-questions@FreeBSD.ORG Reply-To: cjclark@home.com X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Allan Strand wrote, > Gene Harris writes: > > > To debug this, disable NFS from your rc.conf. Kill any > > mountd and nfsd processes. Then, as root, start mountd > > manually and then nfsd 4. Check rpcinfo -p to make sure the > > processes are running. You should be able to connect to > > your exports at this point. > > I did so and the first thing I noticed was that rpcinfo -p hangs. > if I include the hostname then it runs and only the portmapper entries > are showing: > > rpcinfo -p myhostname > program vers proto port > 100000 2 tcp 111 portmapper > 100000 2 udp 111 portmapper > > Both nfsd and mountd show up as processes at this point. > > > > > Also, are you using tcp_wrappers? If so, you will need to > > check hosts.allow and hosts.deny for a portmap: entry. > > Based on the error message you are getting, the nfs and > > mount daemons aren't working. rpc.statd has nothing to do > > with serving up exports. > > The results above certainly confirm this diagnosis > > Any suggestions on where to go from here? Check the loopback device is not misconfigured. You should see, % ifconfig lo0 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 If this is not what you see, see the errata for FreeBSD 3.3, http://www.freebsd.org/releases/3.3R/errata.html -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message