Bug 151107 - nfs client should try both udp and tcp protocols
Summary: nfs client should try both udp and tcp protocols
Keywords:
Status: CLOSED DUPLICATE of bug 150775
Alias: None
Product: Fedora
Classification: Fedora
Component: nfs-utils
Version: rawhide
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-14 22:46 UTC by Thomas Fitzsimmons
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-03-24 10:58:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Thomas Fitzsimmons 2005-03-14 22:46:11 UTC
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):
nfs-utils-1.0.7-1

How reproducible:
Always

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.


Additional info:

The workaround is to add udp to the mount options.

Comment 1 Joe Orton 2005-03-24 10:58:17 UTC

*** This bug has been marked as a duplicate of 150775 ***


Note You need to log in before you can comment on or make changes to this bug.