October 6, 201114 yr I do the following on 4.7 from one 4.7 server to another successfully, but this isn't working when connecting from a 4.7 server to a 5b12a server. (Tower1 is 4.7 and server1 is 5b12a) root@Tower1:/boot# mkdir /mnt/s1disk1 root@Tower1:/boot# mount -t nfs server1:/mnt/disk1/ /mnt/s1disk1 mount.nfs: mount to NFS server 'server1:/mnt/disk1/' failed: RPC Error: Program not registered What am I doing wrong??
October 6, 201114 yr What do you get when you type rpcinfo -p Check to see if another client can see the 5b server - type rpcinfo -p server where server is the IP address of the 5b server
October 6, 201114 yr Author Thanks, here is are the servers. Server1 192.168.1.106 5b12a Tower1 192.168.1.118 4.7 Tower2 192.168.1.139 4.7 The results from 5b12a server1: root@Server1:~# rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 52477 status 100024 1 tcp 40156 status 100021 1 udp 37109 nlockmgr 100021 3 udp 37109 nlockmgr 100021 4 udp 37109 nlockmgr 100021 1 tcp 36138 nlockmgr 100021 3 tcp 36138 nlockmgr 100021 4 tcp 36138 nlockmgr root@Server1:~# rpcinfo -p 192.168.1.118 program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 47582 status 100024 1 tcp 53650 status 100021 1 udp 45610 nlockmgr 100021 3 udp 45610 nlockmgr 100021 4 udp 45610 nlockmgr 100021 1 tcp 58105 nlockmgr 100021 3 tcp 58105 nlockmgr 100021 4 tcp 58105 nlockmgr 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100005 1 udp 39304 mountd 100005 1 tcp 38995 mountd 100005 2 udp 39304 mountd 100005 2 tcp 38995 mountd 100005 3 udp 39304 mountd 100005 3 tcp 38995 mountd root@Server1:~# rpcinfo -p 192.168.1.139 program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 59619 status 100024 1 tcp 42719 status 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100021 1 udp 54168 nlockmgr 100021 3 udp 54168 nlockmgr 100021 4 udp 54168 nlockmgr 100021 1 tcp 37353 nlockmgr 100021 3 tcp 37353 nlockmgr 100021 4 tcp 37353 nlockmgr 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100005 1 udp 39338 mountd 100005 1 tcp 58012 mountd 100005 2 udp 39338 mountd 100005 2 tcp 58012 mountd 100005 3 udp 39338 mountd 100005 3 tcp 58012 mountd The results from Tower1 running 4.7 calling the other 2 machines with 106 being the 5b12a machine. root@Tower1:/boot# rpcinfo -p 100024 1 udp 47582 status 100024 1 tcp 53650 status 100021 1 udp 45610 nlockmgr 100021 3 udp 45610 nlockmgr 100021 4 udp 45610 nlockmgr 100021 1 tcp 58105 nlockmgr 100021 3 tcp 58105 nlockmgr 100021 4 tcp 58105 nlockmgr 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100005 1 udp 39304 mountd 100005 1 tcp 38995 mountd 100005 2 udp 39304 mountd 100005 2 tcp 38995 mountd 100005 3 udp 39304 mountd 100005 3 tcp 38995 mountd root@Tower1:/boot# rpcinfo -p 192.168.1.106 program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 52477 status 100024 1 tcp 40156 status 100021 1 udp 37109 nlockmgr 100021 3 udp 37109 nlockmgr 100021 4 udp 37109 nlockmgr 100021 1 tcp 36138 nlockmgr 100021 3 tcp 36138 nlockmgr 100021 4 tcp 36138 nlockmgr root@Tower1:/boot# rpcinfo -p 192.168.1.139 program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 59619 status 100024 1 tcp 42719 status 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100021 1 udp 54168 nlockmgr 100021 3 udp 54168 nlockmgr 100021 4 udp 54168 nlockmgr 100021 1 tcp 37353 nlockmgr 100021 3 tcp 37353 nlockmgr 100021 4 tcp 37353 nlockmgr 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100005 1 udp 39338 mountd 100005 1 tcp 58012 mountd 100005 2 udp 39338 mountd 100005 2 tcp 58012 mountd 100005 3 udp 39338 mountd 100005 3 tcp 58012 mountd and from the other 4.7 machine Tower2: root@Tower2:~# rpcinfo -p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 59619 status 100024 1 tcp 42719 status 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100021 1 udp 54168 nlockmgr 100021 3 udp 54168 nlockmgr 100021 4 udp 54168 nlockmgr 100021 1 tcp 37353 nlockmgr 100021 3 tcp 37353 nlockmgr 100021 4 tcp 37353 nlockmgr 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100005 1 udp 39338 mountd 100005 1 tcp 58012 mountd 100005 2 udp 39338 mountd 100005 2 tcp 58012 mountd 100005 3 udp 39338 mountd 100005 3 tcp 58012 mountd root@Tower2:~# rpcinfo -p 192.168.1.106 program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 52477 status 100024 1 tcp 40156 status 100021 1 udp 37109 nlockmgr 100021 3 udp 37109 nlockmgr 100021 4 udp 37109 nlockmgr 100021 1 tcp 36138 nlockmgr 100021 3 tcp 36138 nlockmgr 100021 4 tcp 36138 nlockmgr root@Tower2:~# rpcinfo -p 192.168.1.118 program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 47582 status 100024 1 tcp 53650 status 100021 1 udp 45610 nlockmgr 100021 3 udp 45610 nlockmgr 100021 4 udp 45610 nlockmgr 100021 1 tcp 58105 nlockmgr 100021 3 tcp 58105 nlockmgr 100021 4 tcp 58105 nlockmgr 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100005 1 udp 39304 mountd 100005 1 tcp 38995 mountd 100005 2 udp 39304 mountd 100005 2 tcp 38995 mountd 100005 3 udp 39304 mountd 100005 3 tcp 38995 mountd
October 6, 201114 yr Server1 is visible to both servers.... have you tried: mount 192.168.1.106:/mnt/disk1 /mnt/s1disk1 Edit: but "mountd" is not on Server1 Restart nfs on Server1 what is the result from your Server1: showmount -e
October 6, 201114 yr Author Same result going directly to the ip address. Here is what I did edit the following was entered on the wrong machine root@Tower1:~# showmount -e Export list for Tower1: /mnt/disk4 * /mnt/disk3 * /mnt/disk2 * /mnt/disk1 * root@Tower1:~# /etc/rc.d/rc.nfsd restart | logger root@Tower1:~# showmount -e Export list for Tower1: /mnt/disk4 * /mnt/disk3 * /mnt/disk2 * /mnt/disk1 * root@Tower1:~# mkdir /mnt/s1disk1 mkdir: cannot create directory `/mnt/s1disk1': File exists root@Tower1:~# mount -t nfs server1:/mnt/disk1/ /mnt/s1disk1 mount.nfs: mount to NFS server 'server1:/mnt/disk1/' failed: RPC Error: Program not registered root@Tower1:~# Not sure if I restarted nfs correctly though.... Thanks so much for the tips....
October 6, 201114 yr enter this exactly without the -t or extra "/" mount 192.168.1.106:/mnt/disk1 /mnt/s1disk1
October 6, 201114 yr Author Here is what it give back: root@Tower1:~# mount 192.168.1.106:/mnt/disk1 /mnt/s1disk1 mount.nfs: access denied by server while mounting 192.168.1.106:/mnt/disk1 root@Tower1:~# I realized that i entered the nfs restart on the wrong machine..... dumb.... dumb.... When I did it right: root@Server1:~# showmount -e clnt_create: RPC: Program not registered root@Server1:~# showmount -e clnt_create: RPC: Program not registered root@Server1:~# /etc/rc.d/rc.nfsd restart Starting NFS server daemons: /usr/sbin/exportfs -r /usr/sbin/rpc.nfsd 8 /usr/sbin/rpc.mountd root@Server1:~# showmount -e Export list for Server1: root@Server1:~# I realized this and fixed it before I entered your command above.... Looks like a permissions issue now?? I have no users or security set up on server1 at all. Only the root account has a password, and there are no other users.
October 6, 201114 yr Now that the service is running, it looks like no nfs shares have been configured for Server1 Unfortunately I'm not on a 5Beta server to know how to create the exports...
October 6, 201114 yr Author It looks like NFS was enabled, but I reenabled it from the menu. Had to restart NFS again though. Still getting root@Tower1:~# mount 192.168.1.106:/mnt/disk1 /mnt/s1disk1 mount.nfs: access denied by server while mounting 192.168.1.106:/mnt/disk1 root@Tower1:~#
October 6, 201114 yr You'll need to export the disk shares via nfs...<unfortunately I'm not running a 5.0Beta server. Is this how you enable/disable exports of the disk share? Click the Main tab, then the disk number. From there you can disable export of a certain disk. NFS with some restrictions http://lime-technology.com/forum/index.php?topic=7047.msg68278#msg68278 The problem with NFS is that there is no user authentication. Therefore, NFS has these restrictions with each of the security modes: - if share Export is 'No' then share can't be accessed at all - security mode 'Public': any NFS client can read/write the share (this is mapped to user 'nobody' as with Samba guest access). - security mode 'Secure': any NFS client can read the share, no NFS client can write the share. In other words, share appears to be read-only to all NFS clients. - security mode 'Private': any NFS client with uid/gid matching a user on the server will be able to read/write any share. It is not possible to restrict which users have only readonly access, so it's not really private in this sense. Use this with caution.
October 7, 201114 yr Author It appears that the problem is that ver 5 has NFS turned off by default, and I couldn't find out how it was turned on. Once I figured out that you just click the disk on the main screen, and you can set the export via SMB and via NFS from there, it was real easy.
Archived
This topic is now archived and is closed to further replies.