2 Replies Latest reply on Aug 21, 2019 8:44 AM by eChuck

    Windows 7 Ethernet not connecting after upgrade to 11.1.1

    eChuck Lurker

      After upgrading Fusion to 11.1.1, a Windows 7 VM is no longer able to connect to the network. The symptom is the same as if a physical cable had been removed. I.e., there is a red x over the network connection. This connection uses bridging to the Mac's Ethernet connection so that the VM has its own IP address on the subnet. This was all working prior to the upgrade, and no changes have been made to the setup. Rebooting the VM has not helped. VMware tools were updated, with no effect. We've also tried disabling and enabling the network interface on the Windows side, and we've also disabled and enabled the VM network adapter.

       

      Anyone else encountering this problem?

        • 1. Re: Windows 7 Ethernet not connecting after upgrade to 11.1.1
          bfan Enthusiast
          VMware Employees

          Can you see the vmnet services(vmnet-bridge, vmnet-natd, vmnet-netifup) alive in Activity Monitor? if not, you could try to restart them by

          1) Launch Fusion

          2) In terminal, enter /Applications/VMware Fusion 11.1.1.app/Contents/Library

          3) Execute 'sudo ./vmnet-cli --stop', then 'sudo ./vmnet-cli --start'

          4) Power on guest and check the network connection

          • 2. Re: Windows 7 Ethernet not connecting after upgrade to 11.1.1
            eChuck Lurker

            As a follow up on this problem note, we were able to resolve this problem by rebooting the host macOS operating system (10.13.6 in this case). We also created a new Ethernet virtual adapter for the VM and deleted the original adapter. This introduced some changes to the options for bridging the VM via the host's Ethernet interface, but we were able to easily re-establish the bridge option that allowed the Win7 VM to have its own IP address on the local subnet. The Release Notes for 11.1.1 did not mention any changes to networking, but it does seem that some changes were made.

             

            I should also point out that merely restarting VMware Fusion did not resolve the problem.