Fusion

 View Only
  • 1.  Can't get network

    Posted May 08, 2025 09:45 AM

    I have the MacBook Pro m4 on this 15.4.1 update. I can't get network on my VMWare Fusion windows 11, I have tried Nat, and bridge, but it just keeps saying "No Internet access you device can only access other devices on your local network." I can get It to work when I am at home but when I have to connect to the my university's network over vpn or when I at uni it docent work. Can anyone help solve this problem



  • 2.  RE: Can't get network

    Posted May 08, 2025 11:17 AM

    Is the Fusion GUI shut down before you connect to your university's network/VPN?



    ------------------------------
    - Paul (technogeezer)
    vExpert 2025
    ------------------------------



  • 3.  RE: Can't get network

    Posted May 09, 2025 03:54 AM

    Yes I shut it down. But I can only get network at home when I set the network setting to bridge, it can't work on nat where it shares the network with my MacBook. 




  • 4.  RE: Can't get network

    Posted May 09, 2025 10:53 AM
    Edited by a_p_ May 09, 2025 03:05 PM

    I have the same issue as Oliver. No problem with a bridged setup of Fusion at home, but at work, where we have Cisco wireless LAN controllers with ISE, I have no connectivity. I believe the issue is that my Macbook Pro does 802.1x authentication with the Cisco network, and the MacOS MAC address (the one in System Settings -> WiFi -> Details...) gets authorized and is permitted, but the MAC addresses in the Fusion VMs are different, are not recognized and are blocked. This particular behavior is not new, bridged mode didn't work on my work (Cisco) network prior to Sequoia 15.4.1 either. But it used to work perfectly fine in NAT mode, and since 15.4.1 it doesn't. I suspect the issue with NAT mode is a conflict between the Cisco Secure Client (that I use for VPN) and Fusion that didn't exist before Sequoia 15.4.1 but does now. My workaround is to use NAT mode, where I have network connectivity but the DHCP provided DNS server is broken, and manually set DNS address to resolver that works.




  • 5.  RE: Can't get network

    Posted May 09, 2025 11:40 AM

    @Bichon what you said makes sense for bridged networks. The individual guests may not be doing 802.1x authentication so their MAC addresses would be rejected. 

    NAT mode is a different. In your case is the network blocked (that is, you can ping the Mac host via its IP address, or is DNS service unavailable. Is your VPN a split-tunnel configuration (where resources on the local network is still available when the VPN is active)? I'm wondering if that's part of the problem?



    ------------------------------
    - Paul (technogeezer)
    vExpert 2025
    ------------------------------



  • 6.  RE: Can't get network

    Posted May 12, 2025 02:15 PM

    @Technogeezer, my VPN is a split tunnel configuration, but when Fusion is running a guest in NAT mode the DHCP provided DNS resolver (192.168.177.2) always times out. This happens regardless of whether the Cisco VPN client on the host is running and connected, running and not connected, or not running at all. Be aware that when the Cisco Secure Client is installed, it put 3 entries into the Mac's System Settings->Network->Filters section, one of which is a DNS proxy. In another thread on this forum (https://community.broadcom.com/vmware-cloud-foundation/discussion/fusion-dhcp-not-handing-out-a-dns-server-after-upgrade-to-sequoia-154), in post 10 user John John mentioned that if he disables that Cisco DNS proxy, Fusion DNS works in NAT mode, at least for the short time until some other background process re-enables it. In testing, this also appears to be the case on my system.