johanmazel
Cadet
- Joined
- Jul 8, 2012
- Messages
- 6
I run FreeNAS 8.0.4 p3 on a computer with IP address 192.168.2.103.
I am trying to mount an NFS share on another computer with IP address 192.168.2.102.
I authorized 192.168.2.102 for the NFS share regarding directory /mnt/group_1/media.
And "showmount -e" gives:
Exports list on localhost:
/mnt/group_1/media 192.168.2.102
ls -al in /mnt/group_1 gives me:
total 7
drwxr-xr-x 4 root wheel 4 Nov 15 2011 .
drwxr-xr-x 4 root wheel 512 Jul 8 21:35 ..
drwxr-xr-x 2 www www 2 Nov 13 2011 .freenas
drwxr-xr-x 13 jmazel jmazel 16 Jul 8 21:31 media
The uid are consistent regarding the user jmazel on both machines.
And when I try to mount the directory with "sudo mount -vv -t nfs 192.168.2.103:/mnt/group_1/media /home/jmazel/NAS -o "nfsvers=3,proto=tcp"", I get:
mount.nfs: timeout set for Sun Jul 8 23:07:44 2012
mount.nfs: trying text-based options 'nfsvers=3,proto=tcp,addr=192.168.2.103'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.2.103 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=6
mount.nfs: trying 192.168.2.103 prog 100005 vers 3 prot TCP port 919
mount.nfs: portmap query failed: RPC: Timed out
The error seems to be linked with RPC.
On the FreeNAS machine, "rpcinfo -p 192.168.2.103' gives:
program no_version protocole no_port
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100000 4 7 111 portmapper
100000 3 7 111 portmapper
100000 2 7 111 portmapper
100005 1 udp 919 mountd
100005 3 udp 919 mountd
100005 1 tcp 919 mountd
100005 3 tcp 919 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100024 1 udp 888 status
100024 1 tcp 888 status
100021 0 udp 970 nlockmgr
100021 0 tcp 685 nlockmgr
100021 1 udp 970 nlockmgr
100021 1 tcp 685 nlockmgr
100021 3 udp 970 nlockmgr
100021 3 tcp 685 nlockmgr
100021 4 udp 970 nlockmgr
100021 4 tcp 685 nlockmgr
I have no idea whether rpcinfo results are good or not, and, whether the error actually comes from RPC.
Thanks in advance for your time.
I am trying to mount an NFS share on another computer with IP address 192.168.2.102.
I authorized 192.168.2.102 for the NFS share regarding directory /mnt/group_1/media.
And "showmount -e" gives:
Exports list on localhost:
/mnt/group_1/media 192.168.2.102
ls -al in /mnt/group_1 gives me:
total 7
drwxr-xr-x 4 root wheel 4 Nov 15 2011 .
drwxr-xr-x 4 root wheel 512 Jul 8 21:35 ..
drwxr-xr-x 2 www www 2 Nov 13 2011 .freenas
drwxr-xr-x 13 jmazel jmazel 16 Jul 8 21:31 media
The uid are consistent regarding the user jmazel on both machines.
And when I try to mount the directory with "sudo mount -vv -t nfs 192.168.2.103:/mnt/group_1/media /home/jmazel/NAS -o "nfsvers=3,proto=tcp"", I get:
mount.nfs: timeout set for Sun Jul 8 23:07:44 2012
mount.nfs: trying text-based options 'nfsvers=3,proto=tcp,addr=192.168.2.103'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.2.103 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=6
mount.nfs: trying 192.168.2.103 prog 100005 vers 3 prot TCP port 919
mount.nfs: portmap query failed: RPC: Timed out
The error seems to be linked with RPC.
On the FreeNAS machine, "rpcinfo -p 192.168.2.103' gives:
program no_version protocole no_port
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100000 4 7 111 portmapper
100000 3 7 111 portmapper
100000 2 7 111 portmapper
100005 1 udp 919 mountd
100005 3 udp 919 mountd
100005 1 tcp 919 mountd
100005 3 tcp 919 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100024 1 udp 888 status
100024 1 tcp 888 status
100021 0 udp 970 nlockmgr
100021 0 tcp 685 nlockmgr
100021 1 udp 970 nlockmgr
100021 1 tcp 685 nlockmgr
100021 3 udp 970 nlockmgr
100021 3 tcp 685 nlockmgr
100021 4 udp 970 nlockmgr
100021 4 tcp 685 nlockmgr
I have no idea whether rpcinfo results are good or not, and, whether the error actually comes from RPC.
Thanks in advance for your time.