Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!apple!olivea!samsung!munnari.oz.au!uluru5!danielce
From: danielce@ecr.mu.oz.au (Daniel Ake Massimo Paolo Carosone)
Newsgroups: comp.protocols.nfs
Subject: Re: nfsping
Keywords: nfsping, pc-nfs
Message-ID: <5793@munnari.oz.au>
Date: 18 Oct 90 00:26:50 GMT
References: <8781@ncar.ucar.edu> <2919@jaytee.East.Sun.COM>
Sender: news@cs.mu.oz.au
Distribution: usa
Lines: 10

In article <2919@jaytee.East.Sun.COM>, geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) writes:
> NFSPING issues a null RPC call to the mount daemon on the target
> system. Therefore you should get a reply if the system is an NFS
> server. (Most systems only start the mount daemon if /etc/exports
> is present.) NFSPING is actually a wrapper for 
>  "rpcinfo -u <target> <mountprog>"


Ah! This explains why a PC cannot NFSPING itself! This caused a great deal
of confusion and mess originally..