<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Unable to mount NFS on linux clients in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/unable-to-mount-nfs-on-linux-clients/m-p/4290253#M34253</link>
    <description>I know nothing, but "mount request from&lt;BR /&gt;unknown host 10.0.0.10" suggests that the&lt;BR /&gt;server can't translate that IP address to a&lt;BR /&gt;name, which sounds like a problem with DNS&lt;BR /&gt;(or /etc/hosts, or NIS, or whatever,&lt;BR /&gt;depending on how you expect to do&lt;BR /&gt;name-address resolution).</description>
    <pubDate>Mon, 20 Oct 2008 19:29:13 GMT</pubDate>
    <dc:creator>Steven Schweda</dc:creator>
    <dc:date>2008-10-20T19:29:13Z</dc:date>
    <item>
      <title>Unable to mount NFS on linux clients</title>
      <link>https://community.hpe.com/t5/operating-system-linux/unable-to-mount-nfs-on-linux-clients/m-p/4290252#M34252</link>
      <description>Hi Experts&lt;BR /&gt;&lt;BR /&gt;We have a 2 node serviceguard cluster running on redhat linux version 2.6.18-53.el5. We also use the NFStoolkit to export the filesystems to different clients. From the server end the filesystems seem to be exported, however when I try to mount it on the client, I'm unable to mount the filesystems and the mount command fails with the error message 'Permission denied'. On the server side ' mount request from unknown host 10.0.0.10 for /local/a (/local/a)' messages are seen in the /var/log/messages file. The exporting of the filesystems is done by the serviceguard package and the filesystems are exported to the net group. I have copied information from netgroup file and the showmount -e command here.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance for all your help&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Kaushik&lt;BR /&gt;&lt;BR /&gt;[root@esuk1ds1 log]# showmount -e&lt;BR /&gt;Export list for esuk1ds1:&lt;BR /&gt;/local/a    @esuk1ds-farm&lt;BR /&gt;/local/opt  @esuk1ds-farm&lt;BR /&gt;/local/home @esuk1ds-farm&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;esuk1ds-farm     (esuk1ds1-p,,uk.eu.airbus.corp),(esuk1ds2-p,,uk.eu.airbus.corp),(nfslocal,,uk.eu.airbus.corp),(esuk1&lt;BR /&gt;man,,uk.eu.airbus.corp),(esuk1010,,uk.eu.airbus.corp),(esuk1011,,uk.eu.airbus.corp),(esuk1012,,uk.eu.airbus.corp),(es&lt;BR /&gt;uk1013,,uk.eu.airbus.corp),(esuk1014,,uk.eu.airbus.corp),(esuk1015,,uk.eu.airbus.corp),(esuk1016,,uk.eu.airbus.corp),&lt;BR /&gt;(esuk1017,,uk.eu.airbus.corp),(esuk1018,,uk.eu.airbus.corp),(esuk1019,,uk.eu.airbus.corp),(esuk1020,,uk.eu.airbus.cor&lt;BR /&gt;p),(esuk1021,,uk.eu.airbus.corp),(esuk1022,,uk.eu.airbus.corp),(esuk1023,,uk.eu.airbus.corp),(esuk1024,,uk.eu.airbus.&lt;BR /&gt;corp),(esuk1025,,uk.eu.airbus.corp),(esuk1026,,uk.eu.airbus.corp),(esuk1027,,uk.eu.airbus.corp),(esuk1028,,uk.eu.airb&lt;BR /&gt;us.corp),(esuk1029,,uk.eu.airbus.corp),(esuk1030,,uk.eu.airbus.corp),(esuk1031,,uk.eu.airbus.corp),(esuk1032,,uk.eu.a&lt;BR /&gt;irbus.corp),(esuk1033,,uk.eu.airbus.corp),(esuk1034,,uk.eu.airbus.corp),(esuk1035,,uk.eu.airbus.corp),(esuk1036,,uk.e&lt;BR /&gt;u.airbus.corp),(esuk1037,,uk.eu.airbus.corp),(esuk1038,,uk.eu.airbus.corp),(esuk1039,,uk.eu.airbus.corp),(esuk1040,,u&lt;BR /&gt;k.eu.airbus.corp),(esuk1041,,uk.eu.airbus.corp),(esuk1042,,uk.eu.airbus.corp),(esuk1043,,uk.eu.airbus.corp),(esuk1044&lt;BR /&gt;,,uk.eu.airbus.corp),(esuk1045,,uk.eu.airbus.corp),(esuk1046,,uk.eu.airbus.corp),(esuk1047,,uk.eu.airbus.corp),(esuk1&lt;BR /&gt;048,,uk.eu.airbus.corp),(esuk1049,,uk.eu.airbus.corp),(esuk1050,,uk.eu.airbus.corp),(esuk1051,,uk.eu.airbus.corp),(es&lt;BR /&gt;uk1052,,uk.eu.airbus.corp),(esuk1053,,uk.eu.airbus.corp),(esuk1054,,uk.eu.airbus.corp),(esuk1055,,uk.eu.airbus.corp),&lt;BR /&gt;(esuk1056,,uk.eu.airbus.corp),(esuk1057,,uk.eu.airbus.corp),(,,)&lt;BR /&gt;</description>
      <pubDate>Mon, 20 Oct 2008 13:00:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/unable-to-mount-nfs-on-linux-clients/m-p/4290252#M34252</guid>
      <dc:creator>kaushikbr</dc:creator>
      <dc:date>2008-10-20T13:00:38Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to mount NFS on linux clients</title>
      <link>https://community.hpe.com/t5/operating-system-linux/unable-to-mount-nfs-on-linux-clients/m-p/4290253#M34253</link>
      <description>I know nothing, but "mount request from&lt;BR /&gt;unknown host 10.0.0.10" suggests that the&lt;BR /&gt;server can't translate that IP address to a&lt;BR /&gt;name, which sounds like a problem with DNS&lt;BR /&gt;(or /etc/hosts, or NIS, or whatever,&lt;BR /&gt;depending on how you expect to do&lt;BR /&gt;name-address resolution).</description>
      <pubDate>Mon, 20 Oct 2008 19:29:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/unable-to-mount-nfs-on-linux-clients/m-p/4290253#M34253</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2008-10-20T19:29:13Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to mount NFS on linux clients</title>
      <link>https://community.hpe.com/t5/operating-system-linux/unable-to-mount-nfs-on-linux-clients/m-p/4290254#M34254</link>
      <description>Hi Steven &lt;BR /&gt;&lt;BR /&gt;I agree with you, when I export the filesystems explicitly to the full IPv4 IP address of the client, I can mount the filesystems on the client. The server is unable to resolv the hostname even when the filesystems is exported to a wildcarded IP address meaning exported to 10.0.0.*.&lt;BR /&gt;&lt;BR /&gt;I've searched different forums and on google.&lt;BR /&gt;In all these forums it was recomended to use host, dig instead of nslookup, and to update the resolv.conf and nsswitch.conf.&lt;BR /&gt;&lt;BR /&gt;The resolv.conf and nsswitch.conf on my machine looks like ---&lt;BR /&gt;&lt;BR /&gt;/etc/resolv.conf&lt;BR /&gt;search localdomain&lt;BR /&gt;nameserver      127.0.0.1&lt;BR /&gt;&lt;BR /&gt;/etc/nsswitch.conf&lt;BR /&gt;passwd:     files&lt;BR /&gt;shadow:     files&lt;BR /&gt;group:      files&lt;BR /&gt;hosts:      files&lt;BR /&gt;bootparams: nisplus [NOTFOUND=return] files&lt;BR /&gt;ethers:     files&lt;BR /&gt;netmasks:   files&lt;BR /&gt;networks:   files&lt;BR /&gt;protocols:  files&lt;BR /&gt;rpc:        files&lt;BR /&gt;services:   files&lt;BR /&gt;netgroup:   files nisplus&lt;BR /&gt;publickey:  nisplus&lt;BR /&gt;automount:  files nisplus&lt;BR /&gt;aliases:    files nisplus&lt;BR /&gt;&lt;BR /&gt;I have all the IP addresses in the /etc/hosts file.&lt;BR /&gt;&lt;BR /&gt;Since we use a private network, we do not have a DNS server.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance for all your replies.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Kaushik&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 22 Oct 2008 09:09:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/unable-to-mount-nfs-on-linux-clients/m-p/4290254#M34254</guid>
      <dc:creator>kaushikbr</dc:creator>
      <dc:date>2008-10-22T09:09:31Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to mount NFS on linux clients</title>
      <link>https://community.hpe.com/t5/operating-system-linux/unable-to-mount-nfs-on-linux-clients/m-p/4290255#M34255</link>
      <description>hi&lt;BR /&gt;&lt;BR /&gt;In the process of investigation I've found something useful.&lt;BR /&gt;&lt;BR /&gt;By exporting the filesystems to the entire subnet using &lt;BR /&gt;&lt;BR /&gt;/local/a 10.0.0.0/255.255.255.0(rw,sync) -&lt;BR /&gt;I'm able to mount the filesystems on all the hosts.&lt;BR /&gt;&lt;BR /&gt;However I'm still not able to fix the problem of the host resolution.&lt;BR /&gt;&lt;BR /&gt;The host &lt;HOSTNAME&gt; command still comes back with ';; connection timed out; no servers could be reached' and I'm not able to force the host lookup to use the /etc/hosts file.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks in advance for all your suggestions.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Kaushik&lt;/HOSTNAME&gt;</description>
      <pubDate>Wed, 22 Oct 2008 13:25:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/unable-to-mount-nfs-on-linux-clients/m-p/4290255#M34255</guid>
      <dc:creator>kaushikbr</dc:creator>
      <dc:date>2008-10-22T13:25:46Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to mount NFS on linux clients</title>
      <link>https://community.hpe.com/t5/operating-system-linux/unable-to-mount-nfs-on-linux-clients/m-p/4290256#M34256</link>
      <description>The message ';; connection timed out; no servers could be reached' seems to indicate that the system is failing in trying to access a DNS server (maybe on 127.0.0.1, as your resolv.conf indicates).&lt;BR /&gt;&lt;BR /&gt;Remember that processes generally read configuration files like /etc/nsswitch.conf only when they're starting up. If you've made changes to your nsswitch.conf file while your NFS daemons have already been running, the daemons might still be using the old settings.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Fri, 24 Oct 2008 04:06:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/unable-to-mount-nfs-on-linux-clients/m-p/4290256#M34256</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2008-10-24T04:06:07Z</dc:date>
    </item>
  </channel>
</rss>

