|
Fedora 14 NFS connection
Hi Forum, I seems to thrown every lock.stock, barrel and sink to get connected with Fedora 14 TWO boxes. Since we switching from RH5 to Fedora 14 (cheap and free)' SELinux currently disabled on both client and server. The files /etc/host.allow and /etc/host.deny are unmodified on both machine client n server. The make up of /etc/hosts For SERVER Code:
127.0.0.1 localhost.localdomain localhost localhost4====== Code:
127.0.0.1 localhost.localdomain localhost localhost4============== I have following configuration of my /etc/exports file Code:
/home/mydir 192.168.1.*(fsid=0, rw, all_root_squash, async)Code:
Shutting down NFS mountd: [ OK ]The CLIENT =========== At client side simply enabled service as follow: Code:
root# service nfs restart (response received by)When I issue the command: Code:
root# mount.nfs 192.168.1.106:/home/mydir /mnt/tom -vWhen I try to do showmount: Code:
root#showmount -e 192.168.1.106I read entire Fedora Project forum for the answer but all avail. I wonder if any body have remedy for this problem, please guide me or put me in right direction. Thank you, Shy |
Fedora 14 support ended 2011-12-09. The first thing you should do is update to a current release, Fedora 18, to avoid the tens of thousands of issues that have been resolved since then.
|
Code:
mount.nfs 192.168.1.106:/home/mydir /mnt/tomYour hosts files have the names in the IPv6 entries for localhost. I don't know if this is proper. Code:
127.0.0.1 localhost.localdomain localhost localhost4You have 2 enties with fsid=0 in /etc/exports. Only one should be nfs-root. You should bind mount the directories to export over directories which are subdirectories of the nfs-root directory. E.G. /srv/nfs/mydir and /srv/nfs/mydir1. Then /srv/nfs/ will be the nfs-root with the fsid=0 entry in /etc/exports. On the client, the fstab entries will look like tomcat:mydir /mnt/mydir nfs tomcat:mydir1 /mnt/mydir1 nfs Notice how the nfsroot part isn't included, so you just use hostname:share instead of tomcat:/srv/nfs/tomcat. You can use options such as nosuid,noexec,ro on the bind mount options that aren't present for the from directory. Bind mounts allow you to also share a subdirectory with freer permissions without needing to grant others rx permissions to your HOME directory. There is a root_squash and an all_squash option. I don't think there is an all_root_squash option. Check the logs after a mount attempt fails. |
Same old problem...
I modified the /etc/hosts files at server and client which is now: Code:
127.0.0.1 localhost.localdomain localhost localhost4Code:
/home/reposit 192.168.1.*(rw,no_root_squash,sync)Code:
root# showmount -e 192.162.1.64Code:
root# mount -t nfs 192.168.1.64:/home/reposit /mnt -v ON BOTH Machine the user id IS SAME AS WITH ID 500 (same user name or login usernamd such as testuser exist) But mounting process under the root or su Thank you, |
Check if these ports are open:
Code:
111/tcp open rpcbindSince the server rejected the mount attempt, you should check it's logs as well. You posted the log entry from the client side. |
Same old problem... RESOLVED... SUCCESSFULLY
**************** RESOLVED SUCCESSFULLY ****************
FOLLOWING FIX SEEMS TO BE WORK FOR CONNECTION WITH TWO F14 BOXES. HI DROLLI it seems to be your solution made a correct fix of my long tormented problem!!! Thank you. Since I had similar login id and user names on both computers and very identical setup as development PC It seems to be the correction as follow: for the SERVER Code:
/home/reposit 192.168.1.0/255.255.255.0(rw, no_root_squash, sync)======= Code:
root# mount -t nfs 192.168.1.64:/home/reposit /mnt/eagle -v shy |
| All times are GMT -5. The time now is 06:14 PM. |