Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 18 Jul 2016 16:55:38 +0200
From:      Niklaas Baudet von Gersdorff <stdin@niklaas.eu>
To:        freebsd-questions@freebsd.org
Subject:   RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed out
Message-ID:  <20160718145538.GD2783@box-hlm-03.niklaas.eu>

next in thread | raw e-mail | index | archive | help

--UlVJffcvxoiEqYs2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

When I try to mount a NFS share of my provider with

  mount -t nfs -o tcp,nfsv3,nolockd my.provider.tld:/the/shared/directory /mnt/mountpoint

the share won't mount. Instead I get the following error after a while:

  [tcp] stor2.tilaa.nl:/stor2/clients/15337/1: RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed out

My provider requests to use nfsv3 and nolockd that's why I define these options.

In /etc/rc.conf I have

	rpcbind_enable="YES"
	nfs_client_enable="YES"

And I started both with

	service rpcbind start
  service nfsclient start

The funny thing is that I can telnet to both 111 and 2049 without
any problems. In addition there are no relevant outgoing/incoming
packages being blocked in pflog0.

`rpcinfo -p my.provider.tld` gives

   program vers proto   port  service
    100000    4   tcp    111  rpcbind
    100000    3   tcp    111  rpcbind
    100000    2   tcp    111  rpcbind
    100000    4   udp    111  rpcbind
    100000    3   udp    111  rpcbind
    100000    2   udp    111  rpcbind
    100000    4 local    111  rpcbind
    100000    3 local    111  rpcbind
    100000    2 local    111  rpcbind
    100005    1   udp    839  mountd
    100005    3   udp    839  mountd
    100005    1   tcp    839  mountd
    100005    3   tcp    839  mountd
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs

However `showmount -e my.provider.tld` gives

  RPC: Port mapper failure
  showmount: can't do mountdump rpc

after a while.

This seems really strange to me because I have no problems to
reach the server via telnet. Does anyone have an idea what could
be causing this?

Any help is very much appreciated.

    Niklaas

--UlVJffcvxoiEqYs2
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXjO3iAAoJEG2fODeJrIU/KUoP/17z0ZCqjDS0ekf8tqY184t1
TLUCHaOS5qMSXvooqtHLqBM+p7dJ1CePjrbaflMaNfs+l8XG5JLh3742TQdfACyk
UnTEOp5KhU005aXT95lVWs6yxEcYl+Iel4CoqTBKYTGy847AD0G+XThiCI6wCO13
i8IbOrpd6lJziBpYOAdYXg9cQy44oSe39DEm3eP4KrXnNkuvVykqK7Ye7cNg+dvq
nGrvxosjIe1/lL4ZNe6MwlERzsLH+RAhJ/DDCGh09JcaLcz+u13F9Gu9I3sG2HiX
cJDrMcnzfDwd7WfqwRnAToncwxu4CJ1v/N/h852t+ruuP6NP87n9j1Ghuh5M7D1S
1d6GUKhI+jqt9TQRrU0YU0YwBPP9h+CrXxgwRFGPQHtQTiqAbc2fOEoVwquqkTsF
UPWh1l5Hw1x3FYkEmn42zhpzdvd09zzpN6VKIdXhEMq3mKWvpWwvMfLkM3ueTgqf
B+1ydgieMQKFRMHt1WwzFMFaWV+lLMY596LLODG5X30ANEQzt64wwB5h7R2A0bda
mAC+wFHK0EZVUZbQpTWs1wD0YYNJupjT1L2n9rauCsOLDDRGc1XSMh5zLaqM4g8i
UCHXGjo+ZiVqeRQekqNBOOqj6uEPyN843n5A90Wb6VzK5gKhFjsItXBwadLm9BbL
SHAEkEuc1bJLSBDGxpCF
=LQt/
-----END PGP SIGNATURE-----

--UlVJffcvxoiEqYs2--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160718145538.GD2783>