Andreas Nilsson wrote: > I have a share exported on GNU/Linux-box (Gentoo) and as described mounting > that share on my OSOL snv_111a fails. > > It fails even if I specify -o vers=3,sec=sys. If i however specify -o vers=2 > it works. > > If i edit the export to include sec=sys on the server it works perfectly. > >
Hi Andreas, What you are seeing is the correct behavior. Looks like your earlier share on Linux box was exporting filesystem with only ANON mode. Hence OSOL client was not able to mount even with explicit "-o vers=3,sec=sys" mount command. I am not really sure as to how this worked with "-o vers=2"? Can you please send across a snoop output and "nfsstat -m" output on the client for both v3 and v2 mounts? > For my setup i can live with this, but if i bring the OSOL computer to > another network where i do not control the nfs server it will be very > annoying not being able to mount the shares. > Please see work arounds posted on this thread by FrankB, you don't have to have control the server: <snip> 3) on the solaris client side, comment out the 'none' entry from the list of supported security flavours in /etc/nfssec.conf or 4) on the solaris client side, explicitely perform the mount with a security flavour specified other then sec=none <end snip> OSOL client was earlier broken and was quietly sending SYS authentication flavor even for ANON flavors. It is now fixed and what you are seeing is the correct behavior. However, there is a discussion to change OSOL client now and to make it more intelligent than just picking the first mode from the list of security modes returned by Server. Regards, -Vallish
