NFS over TCP not available from (My server ip) - network is unreachable & permission denied
I am trying to boot linux mint from a server I set up in virtualbox. Server is running in linux mint, and the client that I'm testing on (also virtualbox) is disk-less and booting over network. After splash screen vmlinuz and initrd are received correctly, until I get the following error:
Any info on what might be going wrong?
virtualbox nfs dhcp tftp
asked Dec 13 '15 at 15:43
mythicmythic
1436
add a comment |
I am trying to boot linux mint from a server I set up in virtualbox. Server is running in linux mint, and the client that I'm testing on (also virtualbox) is disk-less and booting over network. After splash screen vmlinuz and initrd are received correctly, until I get the following error:
Any info on what might be going wrong?
virtualbox nfs dhcp tftp
asked Dec 13 '15 at 15:43
mythicmythic
1436
172.23.104.0 seems like an address for an entire network, not for a specific server. What config files have that address?
– Mark Plotnick
Dec 13 '15 at 16:10
@MarkPlotnick I have two interfaces. eth0 on NAT and eth1 on internal network. eth1 is on address 172.23.104.0 with netmask 255.255.255.128. I am using dnsmasq and the config files that has that adress is the default config file that I have in /srv/tftp/pxelinux.cfg
– mythic
Dec 13 '15 at 16:19
add a comment |
I am trying to boot linux mint from a server I set up in virtualbox. Server is running in linux mint, and the client that I'm testing on (also virtualbox) is disk-less and booting over network. After splash screen vmlinuz and initrd are received correctly, until I get the following error:
Any info on what might be going wrong?
virtualbox nfs dhcp tftp
asked Dec 13 '15 at 15:43
mythicmythic
1436
I am trying to boot linux mint from a server I set up in virtualbox. Server is running in linux mint, and the client that I'm testing on (also virtualbox) is disk-less and booting over network. After splash screen vmlinuz and initrd are received correctly, until I get the following error:
Any info on what might be going wrong?
virtualbox nfs dhcp tftp
virtualbox nfs dhcp tftp
asked Dec 13 '15 at 15:43
mythicmythic
1436
asked Dec 13 '15 at 15:43
mythicmythic
1436
asked Dec 13 '15 at 15:43
mythicmythic
1436
asked Dec 13 '15 at 15:43
mythicmythic
1436
asked Dec 13 '15 at 15:43
mythicmythic
1436
1436
172.23.104.0 seems like an address for an entire network, not for a specific server. What config files have that address?
– Mark Plotnick
Dec 13 '15 at 16:10
@MarkPlotnick I have two interfaces. eth0 on NAT and eth1 on internal network. eth1 is on address 172.23.104.0 with netmask 255.255.255.128. I am using dnsmasq and the config files that has that adress is the default config file that I have in /srv/tftp/pxelinux.cfg
– mythic
Dec 13 '15 at 16:19
add a comment |
172.23.104.0 seems like an address for an entire network, not for a specific server. What config files have that address?
– Mark Plotnick
Dec 13 '15 at 16:10
@MarkPlotnick I have two interfaces. eth0 on NAT and eth1 on internal network. eth1 is on address 172.23.104.0 with netmask 255.255.255.128. I am using dnsmasq and the config files that has that adress is the default config file that I have in /srv/tftp/pxelinux.cfg
– mythic
Dec 13 '15 at 16:19
172.23.104.0 seems like an address for an entire network, not for a specific server. What config files have that address?
– Mark Plotnick
Dec 13 '15 at 16:10
172.23.104.0 seems like an address for an entire network, not for a specific server. What config files have that address?
– Mark Plotnick
Dec 13 '15 at 16:10
@MarkPlotnick I have two interfaces. eth0 on NAT and eth1 on internal network. eth1 is on address 172.23.104.0 with netmask 255.255.255.128. I am using dnsmasq and the config files that has that adress is the default config file that I have in /srv/tftp/pxelinux.cfg
– mythic
Dec 13 '15 at 16:19
@MarkPlotnick I have two interfaces. eth0 on NAT and eth1 on internal network. eth1 is on address 172.23.104.0 with netmask 255.255.255.128. I am using dnsmasq and the config files that has that adress is the default config file that I have in /srv/tftp/pxelinux.cfg
– mythic
Dec 13 '15 at 16:19
add a comment |
1 Answer
1
active
oldest
votes
As Mark Plotnick pointed out, the most likely cause for this error is network misconfiguration: your eth1 interface has been configured with the invalid address 172.23.104.0.
Unfortunately, this was not my case. I was trying to make a Raspberry Pi 3 boot from NFS and my network, hosts and NFS shares were configured correctly. After having seen a whole range of obscure errors like:
Begin: Retrying nfs mount ... short read: 24 < 28
NFS over TCP not available from [Server IP address]
pmap_getmaps.c: rpc problem: RPC: Authentication error; why = Client credential too weak
mount: RPC: Remote system error - Connection refused
I finally found the answer here (but it was also at hand here).
There was no mismatch between NFSv3 and NFSv4 in nfsd.ko module in the RPI3 kernel tree, nor it was a problem of architecture or whatever. It was simply a matter of allowing RPCs coming from my test subnetwork inside /etc/hosts.allow, like this:
#> cat /etc/hosts.allow
rpcbind mountd nfsd statd lockd rquotad : 127.0.0.1 192.168.1.0/24 10.250.0.0/16
answered Feb 23 '18 at 13:10
AvioAvio
3741610
add a comment |
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%2f249094%2fnfs-over-tcp-not-available-from-my-server-ip-network-is-unreachable-permis%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
As Mark Plotnick pointed out, the most likely cause for this error is network misconfiguration: your eth1 interface has been configured with the invalid address 172.23.104.0.
Unfortunately, this was not my case. I was trying to make a Raspberry Pi 3 boot from NFS and my network, hosts and NFS shares were configured correctly. After having seen a whole range of obscure errors like:
Begin: Retrying nfs mount ... short read: 24 < 28
NFS over TCP not available from [Server IP address]
pmap_getmaps.c: rpc problem: RPC: Authentication error; why = Client credential too weak
mount: RPC: Remote system error - Connection refused
I finally found the answer here (but it was also at hand here).
There was no mismatch between NFSv3 and NFSv4 in nfsd.ko module in the RPI3 kernel tree, nor it was a problem of architecture or whatever. It was simply a matter of allowing RPCs coming from my test subnetwork inside /etc/hosts.allow, like this:
#> cat /etc/hosts.allow
rpcbind mountd nfsd statd lockd rquotad : 127.0.0.1 192.168.1.0/24 10.250.0.0/16
answered Feb 23 '18 at 13:10
AvioAvio
3741610
add a comment |
As Mark Plotnick pointed out, the most likely cause for this error is network misconfiguration: your eth1 interface has been configured with the invalid address 172.23.104.0.
Unfortunately, this was not my case. I was trying to make a Raspberry Pi 3 boot from NFS and my network, hosts and NFS shares were configured correctly. After having seen a whole range of obscure errors like:
Begin: Retrying nfs mount ... short read: 24 < 28
NFS over TCP not available from [Server IP address]
pmap_getmaps.c: rpc problem: RPC: Authentication error; why = Client credential too weak
mount: RPC: Remote system error - Connection refused
I finally found the answer here (but it was also at hand here).
There was no mismatch between NFSv3 and NFSv4 in nfsd.ko module in the RPI3 kernel tree, nor it was a problem of architecture or whatever. It was simply a matter of allowing RPCs coming from my test subnetwork inside /etc/hosts.allow, like this:
#> cat /etc/hosts.allow
rpcbind mountd nfsd statd lockd rquotad : 127.0.0.1 192.168.1.0/24 10.250.0.0/16
answered Feb 23 '18 at 13:10
AvioAvio
3741610
add a comment |
As Mark Plotnick pointed out, the most likely cause for this error is network misconfiguration: your eth1 interface has been configured with the invalid address 172.23.104.0.
Unfortunately, this was not my case. I was trying to make a Raspberry Pi 3 boot from NFS and my network, hosts and NFS shares were configured correctly. After having seen a whole range of obscure errors like:
Begin: Retrying nfs mount ... short read: 24 < 28
NFS over TCP not available from [Server IP address]
pmap_getmaps.c: rpc problem: RPC: Authentication error; why = Client credential too weak
mount: RPC: Remote system error - Connection refused
I finally found the answer here (but it was also at hand here).
There was no mismatch between NFSv3 and NFSv4 in nfsd.ko module in the RPI3 kernel tree, nor it was a problem of architecture or whatever. It was simply a matter of allowing RPCs coming from my test subnetwork inside /etc/hosts.allow, like this:
#> cat /etc/hosts.allow
rpcbind mountd nfsd statd lockd rquotad : 127.0.0.1 192.168.1.0/24 10.250.0.0/16
answered Feb 23 '18 at 13:10
AvioAvio
3741610
As Mark Plotnick pointed out, the most likely cause for this error is network misconfiguration: your eth1 interface has been configured with the invalid address 172.23.104.0.
Unfortunately, this was not my case. I was trying to make a Raspberry Pi 3 boot from NFS and my network, hosts and NFS shares were configured correctly. After having seen a whole range of obscure errors like:
Begin: Retrying nfs mount ... short read: 24 < 28
NFS over TCP not available from [Server IP address]
pmap_getmaps.c: rpc problem: RPC: Authentication error; why = Client credential too weak
mount: RPC: Remote system error - Connection refused
I finally found the answer here (but it was also at hand here).
There was no mismatch between NFSv3 and NFSv4 in nfsd.ko module in the RPI3 kernel tree, nor it was a problem of architecture or whatever. It was simply a matter of allowing RPCs coming from my test subnetwork inside /etc/hosts.allow, like this:
#> cat /etc/hosts.allow
rpcbind mountd nfsd statd lockd rquotad : 127.0.0.1 192.168.1.0/24 10.250.0.0/16
answered Feb 23 '18 at 13:10
AvioAvio
3741610
answered Feb 23 '18 at 13:10
AvioAvio
3741610
answered Feb 23 '18 at 13:10
AvioAvio
3741610
answered Feb 23 '18 at 13:10
AvioAvio
3741610
3741610
add a comment |
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%2f249094%2fnfs-over-tcp-not-available-from-my-server-ip-network-is-unreachable-permis%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
172.23.104.0 seems like an address for an entire network, not for a specific server. What config files have that address?
– Mark Plotnick
Dec 13 '15 at 16:10
@MarkPlotnick I have two interfaces. eth0 on NAT and eth1 on internal network. eth1 is on address 172.23.104.0 with netmask 255.255.255.128. I am using dnsmasq and the config files that has that adress is the default config file that I have in /srv/tftp/pxelinux.cfg
– mythic
Dec 13 '15 at 16:19