Parallels 17 does not connect host Mac to shared and host-only networks

Discussion in 'Installation and Configuration of Parallels Desktop' started by JonL8, Jan 26, 2022.

  1. JonL8

    JonL8 Bit poster

    Messages:
    3
    Since upgrading to Parallels Desktop 17 (and/or moving to macOS 11 and now 12), my host Mac does not connect to the Parallels shared and host-only networks. In older versions of Parallels, there was a checkbox in the Preferences > Network settings to indicate you want to host Mac to connect to these networks. That setting is not present on Parallels 17.

    Guest machines are assigned the appropriate IP addresses for the network adaptor selected. But when using shared networking or host-only networking, I need to be able to connect back to the host via IP address (e.g, to a Web server running on the host Mac), especially when I am in a location where I don't have internet access.

    How do I get the Mac to get connected to the Parallels provided networks?

    Parallels version: 17.1.1 (51537)
    Mac: MacBook Pro (2019) with Intel chip; running macOS 12.1 (Monterey)

    The shared network and host-only network appear to be bound to virtual NICs on the Mac:
    Code:
    % prlsrvctl net list         
    Network ID        Type      Bound To
    Shared            shared  vnic0
    NAT server:
    
    Host-Only         host-only  vnic1
    en5 (en5)         bridged   en5
    Wi-Fi (en0)       bridged   en0
    awdl0 (awdl0)     bridged   awdl0
    llw0 (llw0)       bridged   awdl0
    USB 10/100/1000~  bridged   en9
    vnic0 (vnic0)     bridged   vnic0
    vnic1 (vnic1)     bridged   vnic1
    Default           bridged   FF:FF:FF:FF:FF:FF
    But I don't get IP addresses assigned to the Mac:
    Code:
    % ifconfig
    ...
    vnic0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=3<RXCSUM,TXCSUM>
        ether 00:1c:42:00:00:08
        media: autoselect
        status: active
    vnic1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=3<RXCSUM,TXCSUM>
        ether 00:1c:42:00:00:09
        media: autoselect
        status: active
    Thank you in advance for any assistance.
     
  2. DebasmitaM

    DebasmitaM Forum Maven

    Messages:
    1,142
    Hi, kindly refer to this KB article for resolving the issue.
     
  3. JonL8

    JonL8 Bit poster

    Messages:
    3
    @DebasmitaM@Parallels, thank you for the response. The KB article you pointed me to does not address the issue I am having. My guest VMs (such as Windows 10) are getting assigned an IP and can access the internet just fine (along with other guest VMs using shared networking).

    What is NOT working is that the Parallels HOST (that is, my Mac) is not getting assigned an IP for the Parallels-created subnets. So I cannot access the host Mac from the guest machines.

    In previous versions of Parallels, the host Mac would get assigned IP addresses 10.37.129.2 and/or 10.211.55.2 and I could use those addresses from a guest Windows VM to connect to the Web server on the Host Mac. But that IP is no longer being assigned to the host Mac. See results of a ping from the Windows guest VM to this IP:

    Code:
    C:\Users\jon>ipconfig
    Windows IP Configuration
    
    Ethernet adapter Local Area Connection:
    
       Connection-specific DNS Suffix  . : localdomain
       IPv6 Address. . . . . . . . . . . : fdb2:2c26:f4e4:0:bcb6:1d5f:25e:53aa
       Temporary IPv6 Address. . . . . . : fdb2:2c26:f4e4:0:38ae:293:976f:d4f1
       Link-local IPv6 Address . . . . . : fe80::bcb6:1d5f:25e:53aa%11
       IPv4 Address. . . . . . . . . . . : 10.211.55.3
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 10.211.55.1
    
    C:\Users\jon>ping 10.37.129.2
    
    Pinging 10.37.129.2 with 32 bytes of data:
    Request timed out.
    Request timed out.
    
    Ping statistics for 10.37.129.2:
        Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
    Control-C
    ^C
    C:\Users\jon>ping 10.211.55.2
    
    Pinging 10.211.55.2 with 32 bytes of data:
    Reply from 10.211.55.3: Destination host unreachable.
    Reply from 10.211.55.3: Destination host unreachable.
    
    Ping statistics for 10.211.55.2:
        Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
    Control-C
    ^C
    C:\Users\jon>
    Any ideas on why the host Mac cannot connect to these Parallels-created subnets?
     
  4. GampaA@P

    GampaA@P Pro

    Messages:
    442
  5. StevenD8

    StevenD8 Bit poster

    Messages:
    1
    Hi, what was the fix here? Getting the same problem. It was working before.
     
  6. JonL8

    JonL8 Bit poster

    Messages:
    3
    No fix yet that I am aware of. They wanted me to put in a support ticket on the issue to get assistance. I had gotten used to living with the way things were and haven't gotten around to creating the support case.
     
  7. JohnS127

    JohnS127 Bit poster

    Messages:
    1
    @JonL8 @StevenD8 are you still having this issue? I had the same issue but resolved it by doing a few things, I'm not if all steps are required:
    1. Uncheck "connect mac to this network" on all networks listed in Preferences -> Network
    2. (test -- still not working)
    3. sudo ifconfig bridge100 down
    4. sudo ifconfig bridge100 up
    5. sudo ifconfig bridge101 down
    6. sudo ifconfig bridge101 up
    7. (test -- still not working)
    8. restart parallels
    9. (test -- working!)
    In my case bridge100 == shared network and bridge101 is my host-only. If you have more than two bridge networks you will need to find out what ones are owned by parallels.
    upload_2023-1-13_11-1-11.png

    I wonder if it would be enough to just check/uncheck/restart? Or maybe ifconfig down/up restart?
     
  8. VladimirP12

    VladimirP12 Bit poster

    Messages:
    1
    I had the same issues.
    ifconfig on mac shows that ip is assigned for bridge101 but not for bridge100.
    I've toggled off/on Parallels setting 'Connect Mac to this network' for both Shared and Host, restart Parallels and wow! bridge100 also has ip.
     

Share This Page