From owner-freebsd-stable Sun Apr 13 14:02:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA24050 for stable-outgoing; Sun, 13 Apr 1997 14:02:18 -0700 (PDT) Received: from pegasus.com (pegasus.com [140.174.243.13]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA24045 for ; Sun, 13 Apr 1997 14:02:14 -0700 (PDT) Received: by pegasus.com (8.6.8/PEGASUS-2.2) id LAA03487; Sun, 13 Apr 1997 11:00:39 -1000 Date: Sun, 13 Apr 1997 11:00:39 -1000 From: richard@pegasus.com (Richard Foulk) Message-Id: <199704132100.LAA03487@pegasus.com> In-Reply-To: Michael Ranner "Re: NFS: Problem with portmap (fwd)" (Apr 13, 11:53am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: rmike@sbox.tu-graz.ac.at, Guido van Rooij Subject: Re: NFS: Problem with portmap (fwd) Cc: freebsd-stable@FreeBSD.ORG Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk } > You should get pcnfs or something like that. } } That means, if I run the nfs client software from FTP Software, I will } get this problem, right? I have to check this, but I think you are right. } } It is possible, that the error on "rpcinfo -b nfs 2" (even on localhost) } only appears after a mount from the FTP inc client. I rebooted the } machine and tried "rpcinfo -b nfs 2" and there was no error message, but } there was no try to mount from the PC before. Check into Samba, (cdrom.com:/pub/FreeBSD/packages*/All/samba*) it takes up less space on the pc and works quite well. I've used pcnfs a lot in the past, but I prefer Samba. Richard