<?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>htoh Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>htoh Tracker</description>
    <pubDate>Fri, 17 Nov 2023 18:30:23 GMT</pubDate>
    <dc:date>2023-11-17T18:30:23Z</dc:date>
    <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>
    <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>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: Merging VMDK failure: vmware-vdiskmanager quits with error 0x3e80</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830159#M108777</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Incredible, it worked, like black magic!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I just had to change:&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;ddb.adapterType = "pvscsi"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;to&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;ddb.adapterType = "lsilogic"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why or how this works is a mystery. Now, I must change pvscsi to lsilogic, merge, then change it back.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 15 Jun 2019 19:18:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830159#M108777</guid>
      <dc:creator>htoh</dc:creator>
      <dc:date>2019-06-15T19:18:39Z</dc:date>
    </item>
    <item>
      <title>Re: Merging VMDK failure: vmware-vdiskmanager quits with error 0x3e80</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830157#M108775</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for having a look at the descriptor file&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(some identifiers have been randomized)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 15 Jun 2019 15:59:59 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830157#M108775</guid>
      <dc:creator>htoh</dc:creator>
      <dc:date>2019-06-15T15:59:59Z</dc:date>
    </item>
    <item>
      <title>Merging VMDK failure: vmware-vdiskmanager quits with error 0x3e80</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830155#M108773</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;On WS 15.1.0 host=Windows 10 guest=Windows 10, attempting to merge split vmdk files &lt;SPAN style="font-family: courier new,courier;"&gt;w10.vmdk, w10-s001.vmdk ... w10-s011.vmdk&lt;/SPAN&gt; with this command:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;vmware-vdiskmanager.exe -r w10.vmdk -t 0 w10-new.vmdk&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It fails with this message&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;&lt;SPAN style="font-family: courier new,courier;"&gt;Failed to convert disk:&amp;nbsp; One of the parameters supplied is invalid (0x3e80).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The vm files are all normal.&amp;nbsp; For example, &lt;SPAN style="font-family: courier new,courier;"&gt;vmware-vdiskmanager.exe -k w10.vmdk&lt;/SPAN&gt;&amp;nbsp; or&amp;nbsp; &lt;SPAN style="font-family: courier new,courier;"&gt;vmware-vdiskmanager.exe -d w10.vmdk&lt;/SPAN&gt;&amp;nbsp; executes without error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What am I doing wrong?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 15 Jun 2019 15:03:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Merging-VMDK-failure-vmware-vdiskmanager-quits-with-error-0x3e80/m-p/1830155#M108773</guid>
      <dc:creator>htoh</dc:creator>
      <dc:date>2019-06-15T15:03:37Z</dc:date>
    </item>
    <item>
      <title>Re: USB 3.0 support in W7 x64 guest under W7 x64 host.</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Player/USB-3-0-support-in-W7-x64-guest-under-W7-x64-host/m-p/1804883#M22325</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I sort of understand what you're saying. So the missing stack accounts for the dev id? Is there anything at all we could do about this? Should I upgrade to Vista?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Aug 2014 02:12:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Player/USB-3-0-support-in-W7-x64-guest-under-W7-x64-host/m-p/1804883#M22325</guid>
      <dc:creator>htoh</dc:creator>
      <dc:date>2014-08-22T02:12:02Z</dc:date>
    </item>
    <item>
      <title>Re: USB 3.0 support in W7 x64 guest under W7 x64 host.</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Player/USB-3-0-support-in-W7-x64-guest-under-W7-x64-host/m-p/1804881#M22323</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have the same problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Windows 7 x64 guest on Windows 8.1 x64 host.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the VM guest, device with yellow bang comes up: VEN_15AD&amp;amp;DEV_0778&amp;amp;SUBSYS_077815AD&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm running VM Player 6.0.3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So where can we get this driver?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Aug 2014 17:39:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Player/USB-3-0-support-in-W7-x64-guest-under-W7-x64-host/m-p/1804881#M22323</guid>
      <dc:creator>htoh</dc:creator>
      <dc:date>2014-08-21T17:39:55Z</dc:date>
    </item>
  </channel>
</rss>

