RPC: Port mapper failure - Unable to receive: errno 113 (No route to host) The 2019 Stack Overflow Developer Survey Results Are InNFS Mounting over WAN which portsmount to nfs server failed, system error: no route to hostssh ubuntu to android : No route to hostRoute everything through VPN except SSH on Port 22Problems with postfix/dovecot unable to receive mailbind failure, address in use: Unable to use a TCP port for both source and destination?Able to ping my host but getting no route to hostsudo: unable to resolve host dhcppc1gpg: keyserver receive failed: Server indicated a failureMount nfs hangs client
Did any laptop computers have a built-in 5 1/4 inch floppy drive?
Why can't devices on different VLANs, but on the same subnet, communicate?
Cooking pasta in a water boiler
Loose spokes after only a few rides
What is this business jet?
Why not take a picture of a closer black hole?
Is it possible for absolutely everyone to attain enlightenment?
Correct punctuation for showing a character's confusion
How to type a long/em dash `—`
Can you cast a spell on someone in the Ethereal Plane, if you are on the Material Plane and have the True Seeing spell active?
Are spiders unable to hurt humans, especially very small spiders?
How to translate "being like"?
Dropping list elements from nested list after evaluation
writing variables above the numbers in tikz picture
Is it a good practice to use a static variable in a Test Class and use that in the actual class instead of Test.isRunningTest()?
How do I free up internal storage if I don't have any apps downloaded?
Inverse Relationship Between Precision and Recall
How to obtain a position of last non-zero element
Why isn't the circumferential light around the M87 black hole's event horizon symmetric?
What is the motivation for a law requiring 2 parties to consent for recording a conversation
Worn-tile Scrabble
Is it ok to offer lower paid work as a trial period before negotiating for a full-time job?
Is it safe to harvest rainwater that fell on solar panels?
How to display lines in a file like ls displays files in a directory?
RPC: Port mapper failure - Unable to receive: errno 113 (No route to host)
The 2019 Stack Overflow Developer Survey Results Are InNFS Mounting over WAN which portsmount to nfs server failed, system error: no route to hostssh ubuntu to android : No route to hostRoute everything through VPN except SSH on Port 22Problems with postfix/dovecot unable to receive mailbind failure, address in use: Unable to use a TCP port for both source and destination?Able to ping my host but getting no route to hostsudo: unable to resolve host dhcppc1gpg: keyserver receive failed: Server indicated a failureMount nfs hangs client
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I am trying to mount hdfs on my local machine(ubuntu) using nfs by following the below link:--
https://www.cloudera.com/documentation/enterprise/5-2-x/topics/cdh_ig_nfsv3_gateway_configure.html#xd_583c10bfdbd326ba--6eed2fb8-14349d04bee--7ef4
So,at my machine I installed nfs-common using:-
sudo apt-get install nfs-common
Then,before mounting I have ran these commands:-
rpcinfo -p 192.168.170.52
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 48435 status
100024 1 tcp 54261 status
100005 1 udp 4242 mountd
100005 2 udp 4242 mountd
100005 3 udp 4242 mountd
100005 1 tcp 4242 mountd
100005 2 tcp 4242 mountd
100005 3 tcp 4242 mountd
100003 3 tcp 2049 nfs
showmount -e 192.168.170.52
Export list for 192.168.170.52:
/ *
after that i tried mounting the hdfs using:--
sudo mount -t nfs -o vers=3,proto=tcp,nolock 192.168.170.52:/ /mnt/hdfs_mount/
But i was getting this error:---
mount.nfs: mount system call failed
Then i googled for the problem and installed nfs-kernel-server,portmap using
sudo apt-get install nfs-kernel-server portmap
After executing the above command,the output for:---
rpcinfo -p 192.168.170.52
is:--
192.168.170.52: RPC: Port mapper failure - Unable to receive: errno 113 (No route to host)
and for
showmount -e 192.168.170.52
is:---
clnt_create: RPC: Port mapper failure - Unable to receive: errno 113 (No route to host)
Also the output for:--
sudo service nfs start
comes out to be:--
Failed to start nfs.service: Unit nfs.service not found.
Please help me with this.
ubuntu mount apt nfs hadoop
add a comment |
I am trying to mount hdfs on my local machine(ubuntu) using nfs by following the below link:--
https://www.cloudera.com/documentation/enterprise/5-2-x/topics/cdh_ig_nfsv3_gateway_configure.html#xd_583c10bfdbd326ba--6eed2fb8-14349d04bee--7ef4
So,at my machine I installed nfs-common using:-
sudo apt-get install nfs-common
Then,before mounting I have ran these commands:-
rpcinfo -p 192.168.170.52
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 48435 status
100024 1 tcp 54261 status
100005 1 udp 4242 mountd
100005 2 udp 4242 mountd
100005 3 udp 4242 mountd
100005 1 tcp 4242 mountd
100005 2 tcp 4242 mountd
100005 3 tcp 4242 mountd
100003 3 tcp 2049 nfs
showmount -e 192.168.170.52
Export list for 192.168.170.52:
/ *
after that i tried mounting the hdfs using:--
sudo mount -t nfs -o vers=3,proto=tcp,nolock 192.168.170.52:/ /mnt/hdfs_mount/
But i was getting this error:---
mount.nfs: mount system call failed
Then i googled for the problem and installed nfs-kernel-server,portmap using
sudo apt-get install nfs-kernel-server portmap
After executing the above command,the output for:---
rpcinfo -p 192.168.170.52
is:--
192.168.170.52: RPC: Port mapper failure - Unable to receive: errno 113 (No route to host)
and for
showmount -e 192.168.170.52
is:---
clnt_create: RPC: Port mapper failure - Unable to receive: errno 113 (No route to host)
Also the output for:--
sudo service nfs start
comes out to be:--
Failed to start nfs.service: Unit nfs.service not found.
Please help me with this.
ubuntu mount apt nfs hadoop
Where did you installnfs-kernel-server portmapper
? On the client or on the server? As the first output ofrpcinfo -p 192.168.170.52
andshowmount -e 192.168.170.52
suggests, portmapper and nfs server were already running on the server.
– ridgy
Jun 28 '17 at 15:03
@ridgy on the client
– Bhavya Jain
Jun 29 '17 at 4:20
The client only needsnfs-common
installed.portmapper
andnfs-kernel-server
has to be installed on the server, but that already has been done. Maybe it is not OK to export the root filesystem (I never tried that, because it is unusual). Try exporting any other directory to see if it works then.
– ridgy
Jun 29 '17 at 21:49
The output for "rpcinfo -p 192.168.170.52" and "showmount -e 192.168.170.52" should be same on the client as it was before installing "nfs-kernel-server and portmap" because I have not modified anything on server side.
– Bhavya Jain
Jul 3 '17 at 7:23
add a comment |
I am trying to mount hdfs on my local machine(ubuntu) using nfs by following the below link:--
https://www.cloudera.com/documentation/enterprise/5-2-x/topics/cdh_ig_nfsv3_gateway_configure.html#xd_583c10bfdbd326ba--6eed2fb8-14349d04bee--7ef4
So,at my machine I installed nfs-common using:-
sudo apt-get install nfs-common
Then,before mounting I have ran these commands:-
rpcinfo -p 192.168.170.52
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 48435 status
100024 1 tcp 54261 status
100005 1 udp 4242 mountd
100005 2 udp 4242 mountd
100005 3 udp 4242 mountd
100005 1 tcp 4242 mountd
100005 2 tcp 4242 mountd
100005 3 tcp 4242 mountd
100003 3 tcp 2049 nfs
showmount -e 192.168.170.52
Export list for 192.168.170.52:
/ *
after that i tried mounting the hdfs using:--
sudo mount -t nfs -o vers=3,proto=tcp,nolock 192.168.170.52:/ /mnt/hdfs_mount/
But i was getting this error:---
mount.nfs: mount system call failed
Then i googled for the problem and installed nfs-kernel-server,portmap using
sudo apt-get install nfs-kernel-server portmap
After executing the above command,the output for:---
rpcinfo -p 192.168.170.52
is:--
192.168.170.52: RPC: Port mapper failure - Unable to receive: errno 113 (No route to host)
and for
showmount -e 192.168.170.52
is:---
clnt_create: RPC: Port mapper failure - Unable to receive: errno 113 (No route to host)
Also the output for:--
sudo service nfs start
comes out to be:--
Failed to start nfs.service: Unit nfs.service not found.
Please help me with this.
ubuntu mount apt nfs hadoop
I am trying to mount hdfs on my local machine(ubuntu) using nfs by following the below link:--
https://www.cloudera.com/documentation/enterprise/5-2-x/topics/cdh_ig_nfsv3_gateway_configure.html#xd_583c10bfdbd326ba--6eed2fb8-14349d04bee--7ef4
So,at my machine I installed nfs-common using:-
sudo apt-get install nfs-common
Then,before mounting I have ran these commands:-
rpcinfo -p 192.168.170.52
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 48435 status
100024 1 tcp 54261 status
100005 1 udp 4242 mountd
100005 2 udp 4242 mountd
100005 3 udp 4242 mountd
100005 1 tcp 4242 mountd
100005 2 tcp 4242 mountd
100005 3 tcp 4242 mountd
100003 3 tcp 2049 nfs
showmount -e 192.168.170.52
Export list for 192.168.170.52:
/ *
after that i tried mounting the hdfs using:--
sudo mount -t nfs -o vers=3,proto=tcp,nolock 192.168.170.52:/ /mnt/hdfs_mount/
But i was getting this error:---
mount.nfs: mount system call failed
Then i googled for the problem and installed nfs-kernel-server,portmap using
sudo apt-get install nfs-kernel-server portmap
After executing the above command,the output for:---
rpcinfo -p 192.168.170.52
is:--
192.168.170.52: RPC: Port mapper failure - Unable to receive: errno 113 (No route to host)
and for
showmount -e 192.168.170.52
is:---
clnt_create: RPC: Port mapper failure - Unable to receive: errno 113 (No route to host)
Also the output for:--
sudo service nfs start
comes out to be:--
Failed to start nfs.service: Unit nfs.service not found.
Please help me with this.
ubuntu mount apt nfs hadoop
ubuntu mount apt nfs hadoop
asked Jun 28 '17 at 9:41
Bhavya JainBhavya Jain
2101311
2101311
Where did you installnfs-kernel-server portmapper
? On the client or on the server? As the first output ofrpcinfo -p 192.168.170.52
andshowmount -e 192.168.170.52
suggests, portmapper and nfs server were already running on the server.
– ridgy
Jun 28 '17 at 15:03
@ridgy on the client
– Bhavya Jain
Jun 29 '17 at 4:20
The client only needsnfs-common
installed.portmapper
andnfs-kernel-server
has to be installed on the server, but that already has been done. Maybe it is not OK to export the root filesystem (I never tried that, because it is unusual). Try exporting any other directory to see if it works then.
– ridgy
Jun 29 '17 at 21:49
The output for "rpcinfo -p 192.168.170.52" and "showmount -e 192.168.170.52" should be same on the client as it was before installing "nfs-kernel-server and portmap" because I have not modified anything on server side.
– Bhavya Jain
Jul 3 '17 at 7:23
add a comment |
Where did you installnfs-kernel-server portmapper
? On the client or on the server? As the first output ofrpcinfo -p 192.168.170.52
andshowmount -e 192.168.170.52
suggests, portmapper and nfs server were already running on the server.
– ridgy
Jun 28 '17 at 15:03
@ridgy on the client
– Bhavya Jain
Jun 29 '17 at 4:20
The client only needsnfs-common
installed.portmapper
andnfs-kernel-server
has to be installed on the server, but that already has been done. Maybe it is not OK to export the root filesystem (I never tried that, because it is unusual). Try exporting any other directory to see if it works then.
– ridgy
Jun 29 '17 at 21:49
The output for "rpcinfo -p 192.168.170.52" and "showmount -e 192.168.170.52" should be same on the client as it was before installing "nfs-kernel-server and portmap" because I have not modified anything on server side.
– Bhavya Jain
Jul 3 '17 at 7:23
Where did you install
nfs-kernel-server portmapper
? On the client or on the server? As the first output of rpcinfo -p 192.168.170.52
and showmount -e 192.168.170.52
suggests, portmapper and nfs server were already running on the server.– ridgy
Jun 28 '17 at 15:03
Where did you install
nfs-kernel-server portmapper
? On the client or on the server? As the first output of rpcinfo -p 192.168.170.52
and showmount -e 192.168.170.52
suggests, portmapper and nfs server were already running on the server.– ridgy
Jun 28 '17 at 15:03
@ridgy on the client
– Bhavya Jain
Jun 29 '17 at 4:20
@ridgy on the client
– Bhavya Jain
Jun 29 '17 at 4:20
The client only needs
nfs-common
installed. portmapper
and nfs-kernel-server
has to be installed on the server, but that already has been done. Maybe it is not OK to export the root filesystem (I never tried that, because it is unusual). Try exporting any other directory to see if it works then.– ridgy
Jun 29 '17 at 21:49
The client only needs
nfs-common
installed. portmapper
and nfs-kernel-server
has to be installed on the server, but that already has been done. Maybe it is not OK to export the root filesystem (I never tried that, because it is unusual). Try exporting any other directory to see if it works then.– ridgy
Jun 29 '17 at 21:49
The output for "rpcinfo -p 192.168.170.52" and "showmount -e 192.168.170.52" should be same on the client as it was before installing "nfs-kernel-server and portmap" because I have not modified anything on server side.
– Bhavya Jain
Jul 3 '17 at 7:23
The output for "rpcinfo -p 192.168.170.52" and "showmount -e 192.168.170.52" should be same on the client as it was before installing "nfs-kernel-server and portmap" because I have not modified anything on server side.
– Bhavya Jain
Jul 3 '17 at 7:23
add a comment |
1 Answer
1
active
oldest
votes
I was testing this issue on CentOS 7. When you encounter such a problem you have to dig deeply.
The problem:
clnt_create: RPC: Port mapper failure - Unable to receive: errno 113 (No route to host)
is related to firewall. The command showmount -e IP_server
shows all mounts that are available on server. This command works fine, but you have to be careful which port to open. It does not get through the firewall if only port 2049
has been opened. If the firewall on the NFS server has been configured to let NFS traffic get in, it will still block the showmount
command. To test if you disable firewall on server you should get rid of this issue.
So those ports should be open on server:
firewall-cmd --permanent --add-service=rpc-bind
firewall-cmd --permanent --add-service=mountd
firewall-cmd --permanent --add-port=2049/tcp
firewall-cmd --permanent --add-port=2049/udp
firewall-cmd --reload
Additional test 2049/NFS port for availability.
semanage port -l | grep 2049
- returns SELinux context and the service namenetstat -tulpen | grep 2049
I am unable to verify your solution as I have now opted for a completly different method.But I appreciate your effort.Thanks
– Bhavya Jain
Aug 1 '17 at 18:35
this method worked for me on suse linux. thanks!
– portforwardpodcast
Feb 21 '18 at 19:13
Can confirm, this works for me on Redhat.
– AllisonC
May 1 '18 at 12:24
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f373880%2frpc-port-mapper-failure-unable-to-receive-errno-113-no-route-to-host%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I was testing this issue on CentOS 7. When you encounter such a problem you have to dig deeply.
The problem:
clnt_create: RPC: Port mapper failure - Unable to receive: errno 113 (No route to host)
is related to firewall. The command showmount -e IP_server
shows all mounts that are available on server. This command works fine, but you have to be careful which port to open. It does not get through the firewall if only port 2049
has been opened. If the firewall on the NFS server has been configured to let NFS traffic get in, it will still block the showmount
command. To test if you disable firewall on server you should get rid of this issue.
So those ports should be open on server:
firewall-cmd --permanent --add-service=rpc-bind
firewall-cmd --permanent --add-service=mountd
firewall-cmd --permanent --add-port=2049/tcp
firewall-cmd --permanent --add-port=2049/udp
firewall-cmd --reload
Additional test 2049/NFS port for availability.
semanage port -l | grep 2049
- returns SELinux context and the service namenetstat -tulpen | grep 2049
I am unable to verify your solution as I have now opted for a completly different method.But I appreciate your effort.Thanks
– Bhavya Jain
Aug 1 '17 at 18:35
this method worked for me on suse linux. thanks!
– portforwardpodcast
Feb 21 '18 at 19:13
Can confirm, this works for me on Redhat.
– AllisonC
May 1 '18 at 12:24
add a comment |
I was testing this issue on CentOS 7. When you encounter such a problem you have to dig deeply.
The problem:
clnt_create: RPC: Port mapper failure - Unable to receive: errno 113 (No route to host)
is related to firewall. The command showmount -e IP_server
shows all mounts that are available on server. This command works fine, but you have to be careful which port to open. It does not get through the firewall if only port 2049
has been opened. If the firewall on the NFS server has been configured to let NFS traffic get in, it will still block the showmount
command. To test if you disable firewall on server you should get rid of this issue.
So those ports should be open on server:
firewall-cmd --permanent --add-service=rpc-bind
firewall-cmd --permanent --add-service=mountd
firewall-cmd --permanent --add-port=2049/tcp
firewall-cmd --permanent --add-port=2049/udp
firewall-cmd --reload
Additional test 2049/NFS port for availability.
semanage port -l | grep 2049
- returns SELinux context and the service namenetstat -tulpen | grep 2049
I am unable to verify your solution as I have now opted for a completly different method.But I appreciate your effort.Thanks
– Bhavya Jain
Aug 1 '17 at 18:35
this method worked for me on suse linux. thanks!
– portforwardpodcast
Feb 21 '18 at 19:13
Can confirm, this works for me on Redhat.
– AllisonC
May 1 '18 at 12:24
add a comment |
I was testing this issue on CentOS 7. When you encounter such a problem you have to dig deeply.
The problem:
clnt_create: RPC: Port mapper failure - Unable to receive: errno 113 (No route to host)
is related to firewall. The command showmount -e IP_server
shows all mounts that are available on server. This command works fine, but you have to be careful which port to open. It does not get through the firewall if only port 2049
has been opened. If the firewall on the NFS server has been configured to let NFS traffic get in, it will still block the showmount
command. To test if you disable firewall on server you should get rid of this issue.
So those ports should be open on server:
firewall-cmd --permanent --add-service=rpc-bind
firewall-cmd --permanent --add-service=mountd
firewall-cmd --permanent --add-port=2049/tcp
firewall-cmd --permanent --add-port=2049/udp
firewall-cmd --reload
Additional test 2049/NFS port for availability.
semanage port -l | grep 2049
- returns SELinux context and the service namenetstat -tulpen | grep 2049
I was testing this issue on CentOS 7. When you encounter such a problem you have to dig deeply.
The problem:
clnt_create: RPC: Port mapper failure - Unable to receive: errno 113 (No route to host)
is related to firewall. The command showmount -e IP_server
shows all mounts that are available on server. This command works fine, but you have to be careful which port to open. It does not get through the firewall if only port 2049
has been opened. If the firewall on the NFS server has been configured to let NFS traffic get in, it will still block the showmount
command. To test if you disable firewall on server you should get rid of this issue.
So those ports should be open on server:
firewall-cmd --permanent --add-service=rpc-bind
firewall-cmd --permanent --add-service=mountd
firewall-cmd --permanent --add-port=2049/tcp
firewall-cmd --permanent --add-port=2049/udp
firewall-cmd --reload
Additional test 2049/NFS port for availability.
semanage port -l | grep 2049
- returns SELinux context and the service namenetstat -tulpen | grep 2049
edited Apr 8 at 9:45
fra-san
2,1021721
2,1021721
answered Aug 1 '17 at 14:44
Dragos AlexeDragos Alexe
12615
12615
I am unable to verify your solution as I have now opted for a completly different method.But I appreciate your effort.Thanks
– Bhavya Jain
Aug 1 '17 at 18:35
this method worked for me on suse linux. thanks!
– portforwardpodcast
Feb 21 '18 at 19:13
Can confirm, this works for me on Redhat.
– AllisonC
May 1 '18 at 12:24
add a comment |
I am unable to verify your solution as I have now opted for a completly different method.But I appreciate your effort.Thanks
– Bhavya Jain
Aug 1 '17 at 18:35
this method worked for me on suse linux. thanks!
– portforwardpodcast
Feb 21 '18 at 19:13
Can confirm, this works for me on Redhat.
– AllisonC
May 1 '18 at 12:24
I am unable to verify your solution as I have now opted for a completly different method.But I appreciate your effort.Thanks
– Bhavya Jain
Aug 1 '17 at 18:35
I am unable to verify your solution as I have now opted for a completly different method.But I appreciate your effort.Thanks
– Bhavya Jain
Aug 1 '17 at 18:35
this method worked for me on suse linux. thanks!
– portforwardpodcast
Feb 21 '18 at 19:13
this method worked for me on suse linux. thanks!
– portforwardpodcast
Feb 21 '18 at 19:13
Can confirm, this works for me on Redhat.
– AllisonC
May 1 '18 at 12:24
Can confirm, this works for me on Redhat.
– AllisonC
May 1 '18 at 12:24
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f373880%2frpc-port-mapper-failure-unable-to-receive-errno-113-no-route-to-host%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Where did you install
nfs-kernel-server portmapper
? On the client or on the server? As the first output ofrpcinfo -p 192.168.170.52
andshowmount -e 192.168.170.52
suggests, portmapper and nfs server were already running on the server.– ridgy
Jun 28 '17 at 15:03
@ridgy on the client
– Bhavya Jain
Jun 29 '17 at 4:20
The client only needs
nfs-common
installed.portmapper
andnfs-kernel-server
has to be installed on the server, but that already has been done. Maybe it is not OK to export the root filesystem (I never tried that, because it is unusual). Try exporting any other directory to see if it works then.– ridgy
Jun 29 '17 at 21:49
The output for "rpcinfo -p 192.168.170.52" and "showmount -e 192.168.170.52" should be same on the client as it was before installing "nfs-kernel-server and portmap" because I have not modified anything on server side.
– Bhavya Jain
Jul 3 '17 at 7:23