Comment 4 for bug 214041

Not a firewall issue. I can fix the timeout simply by granting permission on the NFS server.

Here is a testing scenario.

== Permission Denied ==
Linux NFS server
exportfs localhost:/home/olsonl
/home/olsonl localhost(ro,wdelay,root_squash)

Hardy NFS client
sudo mount s12:/home/olsonl /mnt
mount.nfs: Connection timed out
(see attached packet trace)

Gutsy NFS client
sudo mount s12:/home/olsonl tmp
mount.nfs: s12:/home/olsonl failed, reason given by server: Permission denied

== Same server and clients, granted permission ==
the very same Linux NFS server
exportfs fungus:/home/olsonl
exportfs gutsy:/home/olsonl
/home/olsonl fungus.sosstaffing.com(ro,wdelay,root_squash)
/home/olsonl gutsy.sosstaffing.com(ro,wdelay,root_squash)

Hardy NFS client
sudo mount s12:/home/olsonl /mnt
<succeeded instantly>

Gutsty NFS client
sudo mount s12:/home/olsonl tmp
<succeeded instantly>

This is very clearly not a firewall issue. There is no firewall or NAT at all between these points.