TCP port issues for NFSv3 and NFSv4


NFSv3 requires dynamic ports between the NFS server and client which can cause problems getting through your firewall.



You could instead mount using the "vers=4" flag to use NFSv4 since NFSv4 only uses port TCP port 2049 for communication.

QuantaStor support NFSv3 and NFSv4 mounting from clients by default, no changes need to be applied for NFSv4 client access.

Note: you will need to verify that TCP port 2049 is open in the firewall between the client and server network?


This would also let you simplify your mount commands:
# osnsys:/export/nas4 /Volumes/nas4 nfs w,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=,mountvers=3,mountport=34507,mountproto=tcp,local_lock=none,addr= 0 0

Below is an example shorter mount entry using NFSv4
# osnsys:/export/nas4 /Volumes/nas4 nfs rw,relatime,vers=4,rsize=32768,wsize=32768,namlen=255,hard 0 0

Note: We typically do not recommend the use of hard mounts as they require a reboot of the client to recover from in the event of a network outage.


Additional details can be found at this link:



Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk