James Carlson wrote:
You shouldn't need to. The system is supposed to switch between NFS
versions (4, 3, 2) as needed. I suspect that something else is amiss.
In theory it works great. In practice, it does not work at all.
I've seen this same problem for years, with every Solaris version I've
tried >= 10 against all of our Linux NFS servers (mostly various
Ubuntu versions). Getting {Open}Solaris to work as an NFS client for
Linux machines is a horrible mess.
<....>
NFS_CLIENT_VERSMAX=3 should do it.
Exactly.
In my experience, some linuxes seems to have partial support for
NFSv4 (nfs4 support in the nlockmgr, but not in nfsd) and
this tricks {Open}Solaris into trying to mount via NFSv4.
So I always set NFS_CLIENT_VERSMAX=3 on any Solaris box I
install.
Also, recent OpenSolaris gets tricked by another linux bug,
in that the linux NFS server offers to accept sec=none or sec=sys.
Rather than taking the strongest one, Solaris follows the spec
and takes the first one (sec=none). This causes a mount to
succeed, but all of a user's files to be owned by nobody.
Hence you can't write to your files, files are created with
the wrong uid, etc. The workaround for this is to edit
/etc/nfssec.conf and comment out this line:
#none 0 - - - # AUTH_NONE
The Solaris NFS devs have communicated with the Linux community
and gotten them fix the bug that causes sec=none to be
offered first, but this does not magically patch the zillions
of broken linux NFS servers out there...
Sigh
Drew
_______________________________________________
networking-discuss mailing list
[email protected]
