Hi guys.... i m stuck at a point in which i want to mount a nfs using tcp based connection... i have configured firewall to allow portmapper(tcp 111), nfs (tcp 2049) mountd(tcp 791) and is on a machine running rhel 5 .. however wen i try to mount this directory (the name is tempnfs) the mounting fails from another boxs running open suse 11 and cent OS4 using the command

mount -t nfs -o tcp 192.168.1.3:/tempnfs /mnt/tempdir
the mounting fails and the message "internal error" is displayed... the exit status using echo $? is 32.....

but if i flush the iptables firewall the mounting is successful with 0 exit status.... what should i do...???

The nfs server runs rhel 5 and has ip 192.168.1.3
the client with opensuse installed has ip 192.168.1.2
the client with centos installed on it has ip 192.168.1.4



Thanks in advance

First make sure that NFS is actually running on port 2049; the default is to grab a high-numbered port I think (this may depend on your distro'). Also, make sure that it's using TCP, as it's possible that you've only opened the TCP port on the firewall, and if configured to use UDP the packets may block.

I found this quite informative: http://lists.freebsd.org/pipermail/f...ne/049995.html

I use a generic way to figure out those blocks, when just looking at the rules (especially if they are somewhat complex) doesn't show anything obvious.

I posted this a long time ago
http://www.linuxquestions.org/questi...54#post3105554
If you set this up, you can actually see which packets get dropped.

See if that helps you. (My bet: It's not port 2049 -- the portmapper assigns a random free port. It often assigns the first free one in the range, but there are no guarantees.)

Good luck,
mlp

its definitely port 2049 because when redhat included the column of NFS4 in system-config-securitylevel-tui..... they made sure dat nfs bind itself on port 2049 tcp and udp... moreover the rpcinfo -p command also agrres dat nfs is running on port 2049 in both tcp and udp modes

Might sound crazy to ask but have you opened 2049 to UDP then? You have only said it's been opened to TCP what I believe should work, but I usually test things like these just in case.

didnt do that sir..... bt do these things work?????