<?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: VMNAT.EXE Bug? VMWare 17.0.2 to 17.5.0 - change in network behavior in VMware Workstation Player Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Workstation-Player/VMNAT-EXE-Bug-VMWare-17-0-2-to-17-5-0-change-in-network-behavior/m-p/2994226#M41069</link>
    <description>&lt;P&gt;can we classify this as a VMNAT.EXE bug for fix in next version?&lt;/P&gt;</description>
    <pubDate>Sat, 04 Nov 2023 18:26:28 GMT</pubDate>
    <dc:creator>htoh</dc:creator>
    <dc:date>2023-11-04T18:26:28Z</dc:date>
    <item>
      <title>VMNAT.EXE Bug? VMWare 17.0.2 to 17.5.0 - change in network behavior</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Player/VMNAT-EXE-Bug-VMWare-17-0-2-to-17-5-0-change-in-network-behavior/m-p/2993121#M41028</link>
      <description>&lt;P&gt;&lt;STRONG&gt;At version 17.0.2:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Host:&lt;/STRONG&gt; Windows 11&lt;BR /&gt;&lt;STRONG&gt;Guest:&lt;/STRONG&gt; Windows 10, 11&lt;BR /&gt;&lt;STRONG&gt;Network:&lt;/STRONG&gt; DHCP -- host (VPN) -- VMWare Guest (vmxnet3 - NAT)&lt;BR /&gt;&lt;STRONG&gt;Behavior:&lt;/STRONG&gt; Works normally, sleep, wakes, works normally&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;At version 17.5.0:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;New Behavior:&lt;/STRONG&gt; Works normally, sleep, wakes, DNS calls fail&lt;BR /&gt;&lt;STRONG&gt;Immediate Workaround:&lt;/STRONG&gt;&amp;nbsp;(vmxnet3 - bridged), but &lt;U&gt;VPN is bypassed&lt;/U&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This change in behavior occurs with VMWare Tools 12.3.0 and 12.3.5&lt;/P&gt;&lt;P&gt;Can anything be done to make NAT work with VPN (after sleep and wake)?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Additional Information:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;What did not work:&lt;/STRONG&gt; Restarting VM NAT Service&lt;BR /&gt;&lt;STRONG&gt;What worked:&lt;/STRONG&gt;&amp;nbsp;Restarting VM NAT Service after file replacement - vmnat.exe (version 17.5.0) changed to vmnat.exe (version 17.0.2)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 28 Oct 2023 09:57:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Player/VMNAT-EXE-Bug-VMWare-17-0-2-to-17-5-0-change-in-network-behavior/m-p/2993121#M41028</guid>
      <dc:creator>htoh</dc:creator>
      <dc:date>2023-10-28T09:57:42Z</dc:date>
    </item>
    <item>
      <title>Re: VMNAT.EXE Bug? VMWare 17.0.2 to 17.5.0 - change in network behavior</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Player/VMNAT-EXE-Bug-VMWare-17-0-2-to-17-5-0-change-in-network-behavior/m-p/2993441#M41043</link>
      <description>&lt;P&gt;a bump up&lt;/P&gt;</description>
      <pubDate>Tue, 31 Oct 2023 05:08:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Player/VMNAT-EXE-Bug-VMWare-17-0-2-to-17-5-0-change-in-network-behavior/m-p/2993441#M41043</guid>
      <dc:creator>htoh</dc:creator>
      <dc:date>2023-10-31T05:08:35Z</dc:date>
    </item>
    <item>
      <title>Re: VMNAT.EXE Bug? VMWare 17.0.2 to 17.5.0 - change in network behavior</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Player/VMNAT-EXE-Bug-VMWare-17-0-2-to-17-5-0-change-in-network-behavior/m-p/2994226#M41069</link>
      <description>&lt;P&gt;can we classify this as a VMNAT.EXE bug for fix in next version?&lt;/P&gt;</description>
      <pubDate>Sat, 04 Nov 2023 18:26:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Player/VMNAT-EXE-Bug-VMWare-17-0-2-to-17-5-0-change-in-network-behavior/m-p/2994226#M41069</guid>
      <dc:creator>htoh</dc:creator>
      <dc:date>2023-11-04T18:26:28Z</dc:date>
    </item>
  </channel>
</rss>

