📖 ~1 min read
Table of contents
Symptom & Impact
mount.nfs reports access denied by server or permission denied during mount.
Environment & Reproduction
Server export restrictions, firewalld rules, SELinux labels, or wrong client CIDR.
Root Cause Analysis
On server: exportfs -v; on client: showmount -e and mount command output.
Quick Triage
Ensure nfs-server is running and required NFS services are allowed in firewalld.
Step-by-Step Diagnosis
Capture client-side denial output and server-side export listing.

Solution – Primary Fix
Capture updated /etc/exports rule and successful remount.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
Update /etc/exports with correct client subnet and options; run sudo exportfs -rav.
Verification & Acceptance Criteria
Allow services: sudo firewall-cmd –permanent –add-service=nfs && sudo firewall-cmd –reload.
Rollback Plan
Mount again: sudo mount -t nfs4 :/share /mnt/share.
Prevention & Hardening
Confirm read/write behavior and persistent mount via /etc/fstab test using mount -a.
Related Errors & Cross-Refs
Use explicit export ACLs and test changes from a staging client before production rollout.
Related tutorial: View the step-by-step tutorial for rhel-9.
View all rhel-9 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
Revert /etc/exports to previous backup and refresh with exportfs -rav.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.