>> If not, does the -c (amd's `noconn') option apply to this situation?  

> Well, that's a good question.

> If I read the man page, I would say "No":

>      -c      For UDP mount points, do not do a connect(2).  This must be used
>              for servers that do not reply to requests from the standard NFS
>              port number 2049.

> I can't believe that I'd need this with a Solaris NFS server, which I
> know damn well listens on port 2049.

Well, (a) that doesn't mean it _replies_ from port 2049, and (b) the
manpage description, while true, is incomplete: -c must be used when
mounting servers that don't reply from the <addr,port> address the
request is sent to.  If the server has two IP addresses and you send
packets to one and get replies from the other, you will need -c.  (This
is, unfortunately, relatively common behavior for multi-homed machines
when you mount by an address other than the one the server routes
packets to you out via.)

> Secondly, I have *no* problem doing NFS mounts from the SPARCserver
> to the NetBSD/SPARC machine, without using "noconn" at all.  Explain
> that one ...

Heh.  Short of picking apart a packet trace, I have no idea.

					der Mouse

			       mouse@rodents.montreal.qc.ca
		     01 EE 31 F6 BB 0C 34 36  00 F3 7C 5A C1 A0 67 1D