On Sun, Dec 28, 2003 at 09:20:41PM +0900, Rob wrote:>
> Hi,
>
> I am running two FreeBSD-Stable PCs.
>
> One is an NFS server and the other NFS client. Everything used to
> work fine until recently. I suspect that either the new kernel is the
> problem (although there are no complaints on the stable mailing list)
> or the network administration has changed some things.
>
> The server is on 147.46.44.183 with following /etc/exports:
> /usr/ports -maproot=root 147.47.254.184
> /home/entertainment -ro 147.47.254.184
>
> The server boots with rc.conf:
> nfs_reserved_port_only="YES"
> portmap_enable="YES"
> nfs_server_enable="YES"
> mountd_flags="-r"
>
> The client boots with rc.conf:
> nfs_reserved_port_only="YES"
> nfs_client_enable="YES"
>
> On the client (147.47.254.184) I do not get the proper response on:
> $ showmount -e 147.46.44.183
> RPC: Port mapper failure
> showmount: can't do exports rpc
>
> Doing a mount_nfs on the client, gives the same port mapper failure.
>
> Portmap is running on the server; it is not on the client, but
> that should be OK here, right?
>
> I am at a total loss, since I have no idea how to investigate further
> what is actually going wrong. What could be a reason for the RPC Port
> mapper failure? How else can I test the port mapper's functunality?
You can try to check if nfsd and portmap really started on server:
sockstat | grep portmap
and
sockstat | grep nfsd
-ip
--
"Well," Brahma said, "even after ten thousand explanations, a
fool is
no wiser, but an intelligent man requires only two thousand five
hundred."
-- The Mahabharata.