I am trying to mount the nfs server but its saying permission denied. I first tried to do it by autofs it was not mounting then I tried the mount command as :

#mount cu4:/4u1/ cl1

The response it gave is

mount: cu4:/4u1/ failed, reason given by server: Permission denied

I am not able to find out the problem. I found related thread on the net saying to export the name of the machine and I changed the /etc/exports. Name of the comp and the name in /etc/exporst are same now. But still the problem remains.

Please help

Can you post the relevant line from your /etc/exports ?

I am able to mount the nfs files system now using mount command, but not abe to do it with autofs.

Why dont you put those entries in /etc/fstab ...Your nfs directory will be automatically mounted at the time of system startup...

--amit

I want to use autofs since using it is more cleaner than using /etc/fstab perhaps, as I found on some site (I may be wrong) . My /etc/auto.matser has following line

/misc /etc/auto.misc --timeout=60

and /etc/auto.misc has following

4u1 -rw,soft,intr cu4:/4u1
#kernel -ro,soft,intr ftp.kernel.org:/pub/linux
#cd -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom

# the following entries are samples to pique your imagination
#boot -fstype=ext2 :/dev/hda1
#floppy -fstype=auto :/dev/fd0
#floppy -fstype=ext2 :/dev/fd0
#e2floppy -fstype=ext2 :/dev/fd0
#jaz -fstype=ext2 :/dev/sdc1
#removable -fstype=ext2 :/dev/hdd
cdrom -fstype=iso9660,ro :/dev/cdrom

I havent come across any such thing that could prove that using autofs is cleaner than using /etc/fstab..

Anyways, u can try the following

/etc/auto.master

/misc /etc/auto.misc --timeout=60

and in /etc/auto.misc, add another line at the end

* --fstype=ext3 <ip-address or hostname of nfs server>:/shared/folder &

After that

chkconfig autofs on

service autofs start

Regarding error at the time of manual mounting, do the following to troubleshoot...

1. Ping your nfs server from the client machine to check network.
2. Try stopping the iptables firewall to see if that is the reason.
3. Check if the 'portmap ' service is running on the server..
service portmap status

I hope that helps..

--amit