<?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: new esxi 6.7.0 host will not connect to the same nfs server the esxi 6.0.0 host it is replacing.  How to troubleshoot? in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/new-esxi-6-7-0-host-will-not-connect-to-the-same-nfs-server-the/m-p/2244313#M218695</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;well, I don't know if it qualifies as an answer, but after upgrading the freebsd NFS server from 11.2p0 to 11.2p9 the esxi 6.7.0 host can now mount the NFS shares that I could previously mount only with esxi 6.0.0&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 09 Mar 2019 17:51:08 GMT</pubDate>
    <dc:creator>DerekShaw</dc:creator>
    <dc:date>2019-03-09T17:51:08Z</dc:date>
    <item>
      <title>new esxi 6.7.0 host will not connect to the same nfs server the esxi 6.0.0 host it is replacing.  How to troubleshoot?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/new-esxi-6-7-0-host-will-not-connect-to-the-same-nfs-server-the/m-p/2244310#M218692</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have seen many of the unanswered questions about esxi mysteriously not mounting NFS shares.&amp;nbsp; This one provides perhaps a chance to track down what is going on.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The situation:&amp;nbsp; I have built a new esxi 6.7.0 host to move some VMs to while we upgrade the hardware on a host currently running esxi 6.0.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The plan was simple, and I've done this numerous times before (with earlier versions of esxi) --&amp;nbsp; use a manual&amp;nbsp; ghettoVCB run to capture the VMs to the long-running NFS server then use cp and vmkfstools to move them on to the new box (running esxi 6.7.0). (ghettoVmotion....)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But the esxi 6.7.0 throws the maddeningly vague error&lt;/P&gt;&lt;P&gt;2019-03-07T03:44:12.632Z cpu7:2098551 opID=7457c6f4)NFS: 171: NFS mount 192.168.42.3:/somepool/esxi_backupstore0 failed: Unable to connect to NFS server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This NFS server is v3, FreeBSD 11.2 p0.&amp;nbsp; It is used every week by ghettoVCB to make copies of the VMs.&amp;nbsp; It also used to host the linux home dirs for the machines on the LAN ('til we virtualized that to a FreeBSD VM on the esxi host).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, off I go and find all the&amp;nbsp; variants of this problem (mostly unsolved).&amp;nbsp; Salient points -- no firewall on any of the 3 hosts, I can vmkping the NFS server, and netcat to it.&amp;nbsp; I can mount an NFS store on a different FreeBSD server (running 9.1 p0) from the esxi 6.7.0 box, across the internet via a VPN tunnel.&amp;nbsp; I can mount the FreeBSD 11.2 NFS store from linux boxes, (and obviously from the esxi 6.0.0 box).&amp;nbsp; NFS is all v3.&amp;nbsp; The exports on both NFS machines are virtually identical (no pun intended).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so, here are the vmkernel log excerpts showing the failing mount and the successful mounts. If anybody knows how to make these appear as code blocks, please let me know.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;esxi 6.7.0 failure on 192.168.42.3&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:43:40.836Z cpu0:2098551 opID=7457c6f4)World: 11942: VC opID b1067550 maps to vmkernel opID 7457c6f4&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:43:40.836Z cpu0:2098551 opID=7457c6f4)NFS: 160: Command: (mount) Server: (192.168.42.3) IP: (192.168.42.3) Path: (/somepool/esxi_backupstore0) Label: (backupstore0) Options: (None)&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:43:40.836Z cpu0:2098551 opID=7457c6f4)StorageApdHandler: 977: APD Handle be94838e-79e611ed Created with lock[StorageApd-0x430e2a0d6700]&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:43:40.836Z cpu0:2098551 opID=7457c6f4)CpuSched: 693: user latency of 2099586 RPC-tx-192.168.42.3.0.111 0 changed by 2098551 hostd-worker -6&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:43:40.837Z cpu0:2098551 opID=7457c6f4)SunRPC: 1099: Destroying world 0x200982&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:43:40.837Z cpu0:2098551 opID=7457c6f4)CpuSched: 693: user latency of 2099587 RPC-tx-192.168.42.3.3.245 0 changed by 2098551 hostd-worker -6&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:43:51.633Z cpu0:2098551 opID=7457c6f4)SunRPC: 3303: Synchronous RPC abort for client 0x4304551ec120 IP 192.168.42.3.3.245 proc 1 xid 0x2907a083 attempt 1 of 3&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:44:01.633Z cpu2:2098551 opID=7457c6f4)SunRPC: 3303: Synchronous RPC abort for client 0x4304551ec120 IP 192.168.42.3.3.245 proc 1 xid 0x2907a084 attempt 2 of 3&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:44:12.632Z cpu0:2098551 opID=7457c6f4)SunRPC: 3303: Synchronous RPC abort for client 0x4304551ec120 IP 192.168.42.3.3.245 proc 1 xid 0x2907a085 attempt 3 of 3&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:44:12.632Z cpu0:2098551 opID=7457c6f4)SunRPC: 1099: Destroying world 0x200983&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:44:12.632Z cpu7:2098551 opID=7457c6f4)StorageApdHandler: 1063: Freeing APD handle 0x430e2a0d6700 [be94838e-79e611ed]&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:44:12.632Z cpu7:2098551 opID=7457c6f4)StorageApdHandler: 1147: APD Handle freed!&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T03:44:12.632Z cpu7:2098551 opID=7457c6f4)NFS: 171: NFS mount 192.168.42.3:/somepool/esxi_backupstore0 failed: Unable to connect to NFS server.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;esxi 6.7.0 success on 192.168.254.3&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.012Z cpu2:2098619 opID=2a84b29f)World: 11942: VC opID b1067619 maps to vmkernel opID 2a84b29f&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.012Z cpu2:2098619 opID=2a84b29f)NFS: 160: Command: (mount) Server: (192.168.254.3) IP: (192.168.254.3) Path: (/otherpool/esxi_backupstore0) Label: (backupstore0) Options: (None)&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.012Z cpu2:2098619 opID=2a84b29f)StorageApdHandler: 977: APD Handle c02083a6-ef60d04d Created with lock[StorageApd-0x430e2a0d6700]&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.012Z cpu2:2098619 opID=2a84b29f)CpuSched: 693: user latency of 2099848 RPC-tx-192.168.254.3.0.111 0 changed by 2098619 hostd-worker -6&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.059Z cpu2:2098619 opID=2a84b29f)SunRPC: 1099: Destroying world 0x200a88&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.059Z cpu2:2098619 opID=2a84b29f)CpuSched: 693: user latency of 2099849 RPC-tx-192.168.254.3.2.216 0 changed by 2098619 hostd-worker -6&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.101Z cpu2:2098619 opID=2a84b29f)SunRPC: 1099: Destroying world 0x200a89&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.101Z cpu2:2098619 opID=2a84b29f)CpuSched: 693: user latency of 2099850 RPC-tx-192.168.254.3.0.111 0 changed by 2098619 hostd-worker -6&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.144Z cpu2:2098619 opID=2a84b29f)SunRPC: 1099: Destroying world 0x200a8a&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.144Z cpu2:2098619 opID=2a84b29f)CpuSched: 693: user latency of 2099851 RPC-tx-192.168.254.3.8.1 0 changed by 2098619 hostd-worker -6&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.212Z cpu2:2098619 opID=2a84b29f)NFS: 346: Restored connection to the server 192.168.254.3 mount point /otherpool/esxi_backupstore0, mounted as c02083a6-ef60d04d-0000-000000000000 ("backupstore0")&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new, courier; font-size: 10pt;"&gt;2019-03-07T04:11:56.212Z cpu2:2098619 opID=2a84b29f)NFS: 221: NFS mount 192.168.254.3:/otherpool/esxi_backupstore0 status: Success&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;seen and tried the suggestions in these&lt;BR /&gt;&lt;A href="https://kb.vmware.com/s/article/1003967?CoveoV2.CoveoLightningApex.getInitializationData=1&amp;amp;r=3&amp;amp;ui-communities-components-aura-components-forceCommunity-seoAssistant.SeoAssistant.getSeoData=1&amp;amp;other.KM_Utility.getArticleDetails=1&amp;amp;other.KM_Utility.getArticleMetadata=2&amp;amp;other.KM_Utility.getUrl=1&amp;amp;other.KM_Utility.getUser=1&amp;amp;other.KM_Utility.getAllTranslatedLanguages=2&amp;amp;ui-comm-runtime-components-aura-components-siteforce-qb.Quarterback.validateRoute=1" title="https://kb.vmware.com/s/article/1003967?CoveoV2.CoveoLightningApex.getInitializationData=1&amp;amp;r=3&amp;amp;ui-communities-components-aura-components-forceCommunity-seoAssistant.SeoAssistant.getSeoData=1&amp;amp;other.KM_Utility.getArticleDetails=1&amp;amp;other.KM_Utility.getArticleMetadata=2&amp;amp;other.KM_Utility.getUrl=1&amp;amp;other.KM_Utility.getUser=1&amp;amp;other.KM_Utility.getAllTranslatedLanguages=2&amp;amp;ui-comm-runtime-components-aura-components-siteforce-qb.Quarterback.validateRoute=1"&gt;VMware Knowledge Base&lt;/A&gt; &lt;SPAN class="uiOutputText slds-align-middle article_title slds-wrap slds-page-header__title" data-aura-class="uiOutputText" data-aura-rendered-by="34:81;a"&gt;Troubleshooting connectivity issues to an NFS datastore on ESX and ESXi hosts (1003967)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/message/2684697"&gt;NFS mount failed: Unable to connect to NFS server.&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/thread/600747"&gt;Strange Issue : NFS datastore can't be mounted only to several ESXi hosts&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;A href="https://communities.vmware.com/thread/597018"&gt;Unable to add NFS datastore in ESXI 6.5&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Mar 2019 05:34:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/new-esxi-6-7-0-host-will-not-connect-to-the-same-nfs-server-the/m-p/2244310#M218692</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2019-03-07T05:34:16Z</dc:date>
    </item>
    <item>
      <title>Re: new esxi 6.7.0 host will not connect to the same nfs server the esxi 6.0.0 host it is replacing.  How to troubleshoot?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/new-esxi-6-7-0-host-will-not-connect-to-the-same-nfs-server-the/m-p/2244311#M218693</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;B&gt;DerekShaw&lt;/B&gt;,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just a question if I may. In the log extracts you have there is two IP addresses (192.168.42.3 - failure and 192.168.254.3) and I'm wondering if these are two different NFS hosts being tried from the same ESXi server?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Mar 2019 03:28:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/new-esxi-6-7-0-host-will-not-connect-to-the-same-nfs-server-the/m-p/2244311#M218693</guid>
      <dc:creator>ThompsG</dc:creator>
      <dc:date>2019-03-08T03:28:39Z</dc:date>
    </item>
    <item>
      <title>Re: new esxi 6.7.0 host will not connect to the same nfs server the esxi 6.0.0 host it is replacing.  How to troubleshoot?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/new-esxi-6-7-0-host-will-not-connect-to-the-same-nfs-server-the/m-p/2244312#M218694</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;H6&gt;&lt;B&gt;ThompsG&lt;/B&gt; &lt;/H6&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;yes -- these are two different NFS servers being mounted from the same host (at slightly different times). It was a troubleshooting step to narrow the troubleshooting scope.&amp;nbsp; You can see a certain similarity in the way I set things up at different clients (in this case the .254.3 address is at my office), which makes it maybe not so obvious what I have done.&amp;nbsp; The .3 is mostly random chance, but fixed IPs typically get assigned in the first 50 addresses, and NFS servers typically get set up pretty early in the process.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After getting some much-needed sleep (and a weekend, when time demands are not so intense), I am going to try patching up the local NFS server (.42.3) to current freeBSD 11.2 levels ( I think it is p9), and if that doesn't work, then to 12.0pX.&amp;nbsp; I can do those without having to down the esxi box, and they are relatively reliable operations.&amp;nbsp; I'll post the results when I've done it. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ghettoVCB would normally run on sunday night, so I'm still withing normal "failure paramaters".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 09 Mar 2019 02:33:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/new-esxi-6-7-0-host-will-not-connect-to-the-same-nfs-server-the/m-p/2244312#M218694</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2019-03-09T02:33:35Z</dc:date>
    </item>
    <item>
      <title>Re: new esxi 6.7.0 host will not connect to the same nfs server the esxi 6.0.0 host it is replacing.  How to troubleshoot?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/new-esxi-6-7-0-host-will-not-connect-to-the-same-nfs-server-the/m-p/2244313#M218695</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;well, I don't know if it qualifies as an answer, but after upgrading the freebsd NFS server from 11.2p0 to 11.2p9 the esxi 6.7.0 host can now mount the NFS shares that I could previously mount only with esxi 6.0.0&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 09 Mar 2019 17:51:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/new-esxi-6-7-0-host-will-not-connect-to-the-same-nfs-server-the/m-p/2244313#M218695</guid>
      <dc:creator>DerekShaw</dc:creator>
      <dc:date>2019-03-09T17:51:08Z</dc:date>
    </item>
    <item>
      <title>Re: new esxi 6.7.0 host will not connect to the same nfs server the esxi 6.0.0 host it is replacing.  How to troubleshoot?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/new-esxi-6-7-0-host-will-not-connect-to-the-same-nfs-server-the/m-p/2244314#M218696</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Great work! Glad you got this solved &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://communities.vmware.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 09 Mar 2019 21:09:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/new-esxi-6-7-0-host-will-not-connect-to-the-same-nfs-server-the/m-p/2244314#M218696</guid>
      <dc:creator>ThompsG</dc:creator>
      <dc:date>2019-03-09T21:09:10Z</dc:date>
    </item>
    <item>
      <title>Re: new esxi 6.7.0 host will not connect to the same nfs server the esxi 6.0.0 host it is replacing.  How to troubleshoot?</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/new-esxi-6-7-0-host-will-not-connect-to-the-same-nfs-server-the/m-p/2244315#M218697</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have the same problem.&lt;/P&gt;&lt;P&gt;ESXi 6.5 hosts are connected to Sigmanas NFS share without problems.&lt;/P&gt;&lt;P&gt;ESXi 6.7 hosts Unable to connect to NFS server.&lt;/P&gt;&lt;P&gt;2020-07-30T10:05:00.477Z cpu0:2101391 opID=40d32ba3)NFS: 160: Command: (mount) Server: (major.test.ru) IP: (172.22.222.115) Path: (/mn&lt;/P&gt;&lt;P&gt;2020-07-30T10:05:00.477Z cpu0:2101391 opID=40d32ba3)StorageApdHandler: 977: APD Handle a14cee7c-4ebf2a62 Created with lock[StorageApd-0x4310fa9096&lt;/P&gt;&lt;P&gt;2020-07-30T10:05:00.478Z cpu0:2101391 opID=40d32ba3)SunRPC: 1099: Destroying world 0x20759e&lt;/P&gt;&lt;P&gt;2020-07-30T10:05:11.435Z cpu4:2101391 opID=40d32ba3)SunRPC: 3303: Synchronous RPC abort for client 0x430556c67180 IP 172.22.222.115.3.185 proc 1 x&lt;/P&gt;&lt;P&gt;2020-07-30T10:05:22.433Z cpu4:2101391 opID=40d32ba3)SunRPC: 3303: Synchronous RPC abort for client 0x430556c67180 IP 172.22.222.115.3.185 proc 1 x&lt;/P&gt;&lt;P&gt;2020-07-30T10:05:32.433Z cpu8:2101391 opID=40d32ba3)SunRPC: 3303: Synchronous RPC abort for client 0x430556c67180 IP 172.22.222.115.3.185 proc 1 x&lt;/P&gt;&lt;P&gt;2020-07-30T10:05:32.433Z cpu8:2101391 opID=40d32ba3)SunRPC: 1099: Destroying world 0x20759f&lt;/P&gt;&lt;P&gt;2020-07-30T10:05:32.433Z cpu8:2101391 opID=40d32ba3)StorageApdHandler: 1063: Freeing APD handle 0x4310fa9096f0 [a14cee7c-4ebf2a62]&lt;/P&gt;&lt;P&gt;2020-07-30T10:05:32.433Z cpu8:2101391 opID=40d32ba3)StorageApdHandler: 1147: APD Handle freed!&lt;/P&gt;&lt;P&gt;2020-07-30T10:05:32.433Z cpu8:2101391 opID=40d32ba3)NFS: 171: NFS mount major.test.ru:/mnt/ZFSPOOL/vmware failed: Unable to connect to&lt;/P&gt;&lt;P&gt;NAS firmware Xigmanas &lt;SPAN&gt;FreeBSD 12.1-RELEASE-p7 #0 r363366M: Mon Jul 20 16:59:25 CEST 2020&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Node software version&lt;/P&gt;&lt;TABLE class="table-noborder table-vertical table table-compact"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TH class="table-heading"&gt;ESXi Version&lt;/TH&gt;&lt;TD&gt;6.7.0&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TH class="table-heading"&gt;Hypervisor&lt;/TH&gt;&lt;TD&gt;VMware ESXi&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TH class="table-heading"&gt;Build&lt;/TH&gt;&lt;TD&gt;16075168&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;Ping and vmkping are works. Trst machine with CentOS 7 connected without problems to my NAS. Hosts 6.7 connected without problems to QNAP NFS storage.&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Jul 2020 10:46:41 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/new-esxi-6-7-0-host-will-not-connect-to-the-same-nfs-server-the/m-p/2244315#M218697</guid>
      <dc:creator>Clustev</dc:creator>
      <dc:date>2020-07-30T10:46:41Z</dc:date>
    </item>
  </channel>
</rss>

