1825693 Members
3201 Online
109686 Solutions
New Discussion

Re: NFs MOUnting

 
donne007
Regular Advisor

NFs MOUnting

I,m trying to Mount the NFs Volume From a NFS server, after Ensuring thtat the NFs Server& clents are runnig and The Mounting Idr is exported with anaon permission and adding the Nfs Client Ip and username .
But In a Different subnet over a Vpn Wan Link , when i try to mountthe NFs Client throws an error "RPC timed Out "
So i checked and found the rpc services are runnig .. is it Because the port 111-rpc-tcp may be blocked on the firewall.. will opening the port for this particular Ip(nfs Client) to access will Solve My problem.
could any one update me on this ..
Thanx In ADvance ..
regards
ASif
3 REPLIES 3
Wodisch
Honored Contributor

Re: NFs MOUnting

Hello Asif,

since you mentioned a WAN connection, try to use the NFS-mount options "rsize=1024,wsize=1024". The default of 8192 bytes is way too high for a WAN link - every single-bit failure causes ALL 8192 bytes to be re-transmitted, which is a killer for your WAN link (and hence you get timeouts).
1024 bytes is still high for some WAN connections, but samller packet sizes kill NFS...
Do you really need NFS over WAN? How about using FTP or even better RSYNC:
http://rsync.samba.org

HTH,
Wodisch
sven verhaegen
Respected Contributor

Re: NFs MOUnting

I surely hope you are talking about NFS/TCP implementation as NFS over WAN in UDP environments isn't supported at all due to the timeout constrains , if it is TCP them you would have to look wether the link is fast enough and perhaps look at the timeout values for the NFS itself within the mount command (see the man pages of mount_nfs), there is a very good cookbook on nfs setup available on this website

http://docs.hp.com

...knowing one ignores a greath many things is the first step to wisdom...
U.SivaKumar_2
Honored Contributor

Re: NFs MOUnting

hi,
Use NFS over TCP in firewall environments as UDP creates a lot of problems in firewall environments.
The server should have NFS over TCP running.
The entry for nfsd 2049/tcp should be present in /etc/services
Open port 2049 TCP in the firewall. And in the client side , use mount command with -proto option with tcp as argument.
regards,
U.SivaKumar
Innovations are made when conventions are broken