...

...

...

...

On Wed, 22 Nov 2006 16:43:20 -0800, "Learmonth, Peter" Peter.Learmonth@netapp.com said:

Check out options ip.fastpath.enable. It's in the man pages. Peter

Thanks, Peter. We tried that but it didn't work for us.

However, a friend of mine found a solution. If I specify the option "-o proto=tcp" in the mount command the problem is solved.

We found out that by default Fedora tries to use NFS over UDP. When it has to ask the filer's portmapper for the NFS UDP port it sends a UDP packet and receives a UDP response comming from a different interface.

When we specify the option "proto=tcp" for the mount command, it connects to the portmapper via TCP and asks the for the NFS TCP port. Since it's a TCP connection, the filer must use the same interface to send the response packets.

What's interesting is that the "proto=tcp" option affects not only the protocol NFS uses but also the protocol the mount command uses to talk to the portmapper.

I investigated why my Ubuntu machine doesn't have this problem. It asks for NFS over TCP by default.

Thank you all for thinking about the problem.

Gustavo.