Red Hat Bugzilla – Bug 151107
nfs client should try both udp and tcp protocols
Last modified: 2007-11-30 17:11:01 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050308 Firefox/1.0.1 Fedora/1.0.1-5
Description of problem:
"mount -a" failed when I tried to mount an NFS mount from an AS2.1 server. Someone told me that the default protocol has changed from udp to tcp. The old server only accepts udp connections, so I was getting a failure message that the server was down. Adding "udp" to the mount options made things work, but shouldn't that be automatic? In otherwords, the new client should try tcp first and then fall back to udp, the old default.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. attempt to mount an NFS mount from an AS2.1 server
Actual Results: Got "server down" message.
Expected Results: Mount should have succeeded.
The workaround is to add udp to the mount options.
*** This bug has been marked as a duplicate of 150775 ***