NFS over TCP not available from (My server ip) - network is unreachable & permission deniedPXE boot with...

Compute Manhattan distance from origin given a set of left-right-step directions

What does the multimeter dial do internally?

Separate a column into its components based on another table

What are the effects of abstaining from eating a certain flavor?

Why do airports remove/realign runways?

How do ballistic trajectories work in a ring world?

Gory anime with pink haired girl escaping an asylum

Is there a formal/better word than "skyrocket" for the given context?

What was the significance of Spider-Man: Far From Home being an MCU Phase 3 film instead of a Phase 4 film?

Who goes first? Person disembarking bus or the bicycle?

Findminimum of Integral

run bash scripts in folder all at the same time

Other Space Shuttle O-ring failures

Is this really the Saturn V computer only, or are there other systems here as well?

How many Jimmys can fit?

stuck {in/at} beta

Blocks from @ jafe

How do I explain that I don't want to maintain old projects?

My previous employer committed a severe violation of the law and is also being sued by me. How do I explain the situation to future employers?

Delete elements less than the last largest element

US citizen traveling with Peruvian passport

Draw a diagram with rectangles

What is the relationship between external and internal composition in a cartesian closed category?

How to evaluate the performance of open source solver?



NFS over TCP not available from (My server ip) - network is unreachable & permission denied


PXE boot with NFS: /sbin/init: No such file or directoryPXE boot chaining to hardcoded TFTP server?NFS: failed to create MNT RPC client status = -101Built the kernel with NFS support but not getting /dev/nfscopy files from tftp serverCan't boot Kali-linux in Virtualbox (Elementary OS host)NFS rootfs booting fails silently on ARM imx53 boardWhy is /boot empty on nfsboot nfs host, when files exist on booted client?Oracle Linux won't mount CentOS NFS share, but Arch willLinux Mint on Virtual Box Display Bug






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







2















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:



error



Any info on what might be going wrong?










share|improve this question














bumped to the homepage by Community 59 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • 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


















2















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:



error



Any info on what might be going wrong?










share|improve this question














bumped to the homepage by Community 59 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • 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














2












2








2








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:



error



Any info on what might be going wrong?










share|improve this question














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:



error



Any info on what might be going wrong?







virtualbox nfs dhcp tftp






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 13 '15 at 15:43









mythicmythic

1536 bronze badges




1536 bronze badges





bumped to the homepage by Community 59 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 59 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • 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











  • @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










1 Answer
1






active

oldest

votes


















0














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






share|improve this answer


























    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
    });


    }
    });














    draft saved

    draft discarded


















    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









    0














    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






    share|improve this answer




























      0














      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






      share|improve this answer


























        0












        0








        0







        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






        share|improve this answer













        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







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 23 '18 at 13:10









        AvioAvio

        4241 gold badge7 silver badges10 bronze badges




        4241 gold badge7 silver badges10 bronze badges






























            draft saved

            draft discarded




















































            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.




            draft saved


            draft discarded














            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





















































            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







            Popular posts from this blog

            Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

            Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

            Ciclooctatetraenă Vezi și | Bibliografie | Meniu de navigare637866text4148569-500570979m