Solaris

Hi all, new here.

I'm attempting to mount an NFS share I've created on a 2012r2 esx VM on my solaris 10 vm, I'm using the following command:

Code:

mount 2012box:/sharename /mnt

and I get the following result:

Code:

nfs mount: mount: /mnt: Operation not supported

Both vms can ping one another by IP and name, and as far as I can tell the network is clear between them.
The settings for the NFS share are as follows:

Remote path: 2012box:/sharename
Authentication: No server authentication (AUTH_SYS)
Enable unmapped user access
Allow anonymous access
Share permissions: All Machines-Read/Write-Root acess allowed-ANSI
NTFS permissions: Anonymous logon and Everyone have full control and allow

Any help is extremly appreciated!

UPDATE:
I've run

Code:

snoop

on my server as I send the mount request and noticed there was a

Code:

NFS4ERR_MINOR_VERS_MISMATCH

, this seems to be coming from the 2012R2 box?

Let's ensure that the NFS handle is being published
What says:

Code:

# showmount <ip address>

Are you sure that there are no userid/passwd credentials required?

The error implies that there may be a NFS version mismatch.

Try specifying the NFS version (2, 3 or 4) on the mount command. Try each of them.

Code:

showmount -e server

--
Try to force a version 3 mount; see

Code:

man mount_nfs

The share looks to be available

Code:

 
# showmount -e
export list for x.x.x.x:
/sharename (everyone)

Forcing to mount on a lower nfs version now comes up with:

Code:

 
# mount 2012box:/sharename /mnt
nfs mount: 2012box: : RPC: Program not registered
nfs mount: retrying: /mnt

And it gets stuck like that, snoops shows this happening over and over while it's stuck:

Code:

 
solaris10vm -> 2012box.fqdn.com PORTMAP C GETPORT prog=100005 (MOUNT) vers=3 proto=UDP
 
2012box.fqdn.com -> solaris10vm PORTMAP R GETPORT port=0

And due to flooding nobody else will be coming in today...

---------- Post updated at 09:49 AM ---------- Previous update was at 09:37 AM ----------

Haha! Fixed!

On the 2012box under server manager > tools > services for NFS > server for NFS > properties I changed the transport protocol to UDP.

So it was a combination of the the version mismatch between Solaris 10's NFS 4 and 2012R2's NFS 4.1 and the wrong Transport Protocol (by default TCP+UDP)!