Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!usenet.coe.montana.edu!news.u.washington.edu!carson.u.washington.edu!ganter From: ganter@carson.u.washington.edu (Mark Ganter) Subject: Re: mountd/portmap/NFS problem Message-ID: <1992Nov6.181052.10725@u.washington.edu> Sender: news@u.washington.edu (USENET News System) Organization: University of Washington References: <1992Nov5.175351.26079@cs.brown.edu> <1992Nov6.050651.8709@fcom.cc.utah.edu> Date: Fri, 6 Nov 1992 18:10:52 GMT Lines: 45 terry@cs.weber.edu (A Wizard of Earth C) writes: >In article <1992Nov5.175351.26079@cs.brown.edu>, lr@cs.brown.edu (Luigi Rizzo) writes: >|> >|> It must be something trivial but... I installed 386bsd 0.1 on a >|> 486-33 with IDE drive, we8013-clone ethernet with no problems. >|> Everything including the network seems to work (at least, ftp, telnet, >|> rsh work fine and quickly in both directions). However, when I try to >|> boot with the nfs-related stuff enabled (portmap, mountd etc.) mountd >|> hangs without being able to register with portmap. If I press ^C on the >|> console during boot, things proceed more or less regul;arly and the >|> system comes up (the only thing is, mountd takes most of CPU time). >|> Other things (nfsd, nfsiod) apparently register correctly (as shown by >|> using rpcinfo from another machine). Now, I cannot either NFS-mount >|> the 386 disk from another machine (clearly because mountd does not >|> work, the error message is >|> >|> nfs_mount: bsd386a:/ server not responding: rpc program not registered >|> >|> or mount other disks on the 386bsd machine. (this time the error >|> message is >|> >|> Bad MNT RPC: RPC: Authentication error; why = Invalid client credential >|> >|> >|> I haven't installed the crypt routines or any of the patches yet, >|> because from the descriptions I have it's not clear which ones >|> apply to my problem. Any help from the net ? >Install the NFS and mount patches at the very least. You seem to be running >into the overlap and reserved port problems. Terry & Luigi, I had the same problem recently. I chased it down to an export problem on the file system thatbsd was trying to mount. My memory on the net says "386bsd doesn't do secure NFS mount". Is that true? I changed my /etc/exports file of the "host system" from: /users dragon to: /users and everything now works fine! Just my $0.02 worth ...Mark Mark Ganter/Univ of Washington/Dept of Mech Engr/FU-10/Seattle, WA 98195 USA ganter@u.washington.edu