From owner-freebsd-current Tue Apr 8 10:31:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA19763 for current-outgoing; Tue, 8 Apr 1997 10:31:53 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA19758 for ; Tue, 8 Apr 1997 10:31:50 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id SAA07524; Tue, 8 Apr 1997 18:31:21 +0100 (BST) Date: Tue, 8 Apr 1997 18:31:21 +0100 (BST) From: Doug Rabson To: Justen Stepka cc: Paulo Menezes , current@freebsd.org Subject: Re: nfs problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 8 Apr 1997, Justen Stepka wrote: > > > On Tue, 8 Apr 1997, Paulo Menezes wrote: > > > > > Hi, > > > > After last rebuild of the nfs server running 2.2.1 (ctm 226), the clients > > are unable to use mounted fs. > > They seem to be able to mount the fs but can do nothing with it. > > On the server I have the following messages > > > > NFS request from unprivileged port (193.136.205.41:1236) > > NFS request from unprivileged port (193.136.205.41:1236) > > NFS request from unprivileged port (193.136.205.41:1236) > > NFS request from unprivileged port (193.136.205.41:1236) > > NFS request from unprivileged port (193.136.205.41:1327) > > NFS request from unprivileged port (193.136.205.41:1327) > > NFS request from unprivileged port (193.136.205.41:1327) > > > > Is this a known problem, or it is just a gift I received. > > I got the same problem and I screamed :). All that you need to do is use > mountd -n on the server. FreeBSD doesn't use secure ports by default and > this make allow the non secure port request. > FreeBSD-current now uses secure ports by default. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891