In your /etc/exports try give the access to entire network - 192.168.1.0 and observe.
This is my /etc/exports:
/home/SDB1 192.168.1.0(ro,async,no_su
/home/Sources 192.168.1.0(ro,async,no_su
Main Topics
Browse All TopicsI am trying to set up NFS. But it's not working correctly.
This is my /etc/exports:
/home/SDB1 192.168.1.100(ro,async,no_
/home/Sources 192.168.1.100(ro,async,no_
This is my /etc/fstab at the client:
192.168.1.102:/home/SDB1 /home/NFS1 nfs defaults 0 0
192.168.1.102:/home/Source
Also tried:
mount -t nfs -o defaults 192.168.1.102:/home/Source
I get the error:
mount: wrong fs type, bad option, bad superblock on 192.168.1.102:/home/Source
missing codepage or helper program, or other error
(for several filesystems (e.g. nfs, cifs) you might
need a /sbin/mount.<type> helper program)
In some cases useful info is found in syslog - try
dmesg | tail or so
All firewalls are taken down, there are read rights for everyone on the share point and down the tree. Portmaps, nfs-common and nfs-kernel-server is installed. Nfs has been restarted after /etc/exports edit, without errors.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
What distribution of Linux are you running? Are you sure you have the utilities/kernel module to mount NFS shares? In Ubuntu/Debian I believe the package is nfs-common - ie: apt-get install nfs-common.
Have you checked the logs on the NFS server? If it were a permission problem in your exports file you would see something like:
"failed, reason given by server: Permission denied" on the client
and something like:
"refused mount request" on the server
I forgot to install nfs on the client :) (but it was all installed and ready on the server)
At the end of the installation, the system tries to start netatalk but fails:
Starting Netatalk services (this will take a while): nbp_rgstr: Connection went over timelimit
Can't register Deb-i86a:Workstation@*
I then try:
Deb-i86a:~# mount -t nfs -o ro 192.168.1.102:/home/Source
mount.nfs: 192.168.1.102:/home/Source
All the other setup is done as suggested by the experts in this thread.
Logs on the client:
user.log:Nov 7 19:04:17 Deb-i86a if-up.d/mountnfs[eth7]: if-up.d/mountnfs[eth7]: lock /var/run/network/mountnfs exist, not mounting
user.log:Nov 7 19:04:17 Deb-i86a if-up.d/mountnfs[eth4]: if-up.d/mountnfs[eth4]: lock /var/run/network/mountnfs exist, not mounting
syslog:Nov 7 19:04:17 Deb-i86a if-up.d/mountnfs[eth7]: if-up.d/mountnfs[eth7]: lock /var/run/network/mountnfs exist, not mounting
syslog:Nov 7 19:04:17 Deb-i86a if-up.d/mountnfs[eth4]: if-up.d/mountnfs[eth4]: lock /var/run/network/mountnfs exist, not mounting
syslog:Nov 7 19:04:45 Deb-i86a kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
syslog:Nov 7 19:04:45 Deb-i86a kernel: NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
syslog:Nov 7 19:06:30 Deb-i86a nfsd[3197]: nfssvc: Input/output error
Logs on the server:
Nothing special.
The client runs Debian GNU/Linux 5.0 \n \l with 256 Mb memory as a virtual machine in terminal text based mode only. No GUI.
I'm not 100% sure about what georgekraj posted - I've always put a subnet mask on my Linux exports declarations if I wanted to open it up to a subnet. This behavior could be different across different platforms - ie: solaris, linux, etc. ie:
/home/SDB1 192.168.1.0/24(ro,async,no
/home/Sources 192.168.1.0/24(ro,async,no
What is the server running? If it's Debian/Ubuntu look at /var/log/daemon.log - if the client is getting a permission denied error somewhere on the server the mount request should be logged
To get things to work, I;
*installed nfs on the client also
*allowed the whole subnet to connect, whe exporting the filesystem vi /etc/exports. Hence:
/home/Sources 192.168.1.0/24(ro,async,no
*mounted the share on the client as read only and nolock. If I tried to mount it just with read only, I got this error:
mount.nfs: rpc.statd is not running but is required for remote locking.
Either use '-o nolock' to keep locks local, or start statd.
Please comment further if you wish.
Business Accounts
Answer for Membership
by: medveddPosted on 2009-11-07 at 05:36:15ID: 25766267
You're exporting filesystems as ro, but trying to mount them as rw. s /home/NFS2
Try mount -t nfs -o ro 192.168.1.102:/home/Source