On 5 Apr 2016 17:46, "Rick Stevens" <ricks@xxxxxxxxxxxxxx> wrote:
>
> On 04/05/2016 08:49 AM, John J. McDonough wrote:
>>
>> I have a small server that offers a number of directories over NFS. I
>> am running a virtual machine on another physical machine.
>>
>> When I try to mount an NFS directory on the VM, the NFS server refuses,
>> claiming a bad port. Successive tries result in different reported
>> port numbers.
>>
>> What is going on? Is there some sort of virtio setting I am missing?
>> NFS works fine to the machine hosting the VM, but not to another
>> machine.
>
>
> It rather depends on the NFS client implementation. For example, a
> normal NFS mount will fail if the client is a Mac because the Mac's
> client won't use reserved ports unless you specifically give it an
> "-o resvport" option. This is more or less the opposite of Linux (which
> uses reserved ports by default).
>
> My suggestion is to try the mount on the VM clients and try the "-o resvport" option, just in case:
>
> mount -o resvport,rw nfsserver:/export /mountpoint
>
> and see what you get.
Don't further NFS3 has a bunch of randomly chosen ports that you need to configure or figure out and let through the firewall... NFS3 was hell for that.
Ensure you are definitely using NFS4 so that you only need TCP/2049
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: http://lists.fedoraproject.org/admin/lists/users@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
