From owner-freebsd-stable@FreeBSD.ORG  Sun Dec 28 04:20:48 2003
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5732A16A4CF
	for <freebsd-stable@freebsd.org>;
	Sun, 28 Dec 2003 04:20:48 -0800 (PST)
Received: from sis1.snu.ac.kr (sis1.snu.ac.kr [147.46.10.36])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1C85443D48
	for <freebsd-stable@freebsd.org>;
	Sun, 28 Dec 2003 04:20:45 -0800 (PST)
	(envelope-from nospam@users.sourceforge.net)
Received: from users.sourceforge.net ([147.46.44.183])
	by sis1.snu.ac.kr (8.12.10/8.12.10) with ESMTP id hBSCI61i242662
	for <freebsd-stable@freebsd.org>; Sun, 28 Dec 2003 21:18:06 +0900
Message-ID: <3FEECA99.4030603@users.sourceforge.net>
Date: Sun, 28 Dec 2003 21:20:41 +0900
From: Rob <nospam@users.sourceforge.net>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031104
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: NFS problem: "RPC: Port mapper failure"
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Dec 2003 12:20:48 -0000


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?

Thanks,
Rob.