From owner-freebsd-questions@FreeBSD.ORG Mon Jun 13 17:50:07 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FCD116A41C for ; Mon, 13 Jun 2005 17:50:07 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail26.sea5.speakeasy.net (mail26.sea5.speakeasy.net [69.17.117.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28D3A43D55 for ; Mon, 13 Jun 2005 17:50:06 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 12588 invoked from network); 13 Jun 2005 17:50:06 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail26.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 13 Jun 2005 17:50:06 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 12AB030; Mon, 13 Jun 2005 13:50:05 -0400 (EDT) Sender: lowell@be-well.ilk.org To: munn To: freebsd-questions@freebsd.org References: <42ADB097.8070703@umd.edu> From: Lowell Gilbert Date: 13 Jun 2005 13:50:04 -0400 In-Reply-To: <42ADB097.8070703@umd.edu> Message-ID: <4464wicfjn.fsf@be-well.ilk.org> Lines: 15 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Subject: Re: NFS question X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2005 17:50:07 -0000 munn writes: > I am trying to NFS connect to a server machine using mount_nfs. I get > the following message > > RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive. An > 'identical' machine connects without a message and the mount works. > > Does anybody know what the message means and how to make it go away? > > All machines are running 5.4-STABLE Stable as of when? There was a bug in -STABLE last week which could explain this. If you updated the problematic machine last week, do it again now.