To: Gerald C. Simmons <firstname.lastname@example.org>
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
Date: 07/15/1998 14:12:12
> Hummingbird is using port 2049 for mounting drives. I am currently
> using the -n option for mountd.
Uh-oh. I think there's a little confusion here.
There are two RPC protocols involved, which can loosely be called MOUNT
and NFS. The NFS protocol is the workhorse, but it has a bit of a
chicken-and-egg problem in that it needs a thing called a filehandle to
do anything, but provides no way to get a filehandle without already
having one. The MOUNT protocol resolves this, by mapping a pathname to
a "first" filehandle.
Port 2049 is normally the port used for NFS, largely for historical
reasons. But the servers for *both* protocols can potentially demand
that the client use a "reserved" port. Using -n to mountd will affect
whether the daemon demands that the MOUNT protocol be run with a
"reserved" port on the client, equivalent to the -noresvmnt option in
the exports file, but (as I read the manpage) applying to all exported
filesystems. I don't see any way to get a similarly global analog of
You might try listing the exported filesystem with both -noresvport and
-noresvmnt in the exports database on the NetBSD machine and see if
that helps any, though it sounds as though your current problem may no
longer have anything to do with "reserved" ports.
7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B