Network Initialization Failed

Discussion in 'Installation and Configuration' started by StephenB13, Oct 6, 2018.

  1. PaulM50

    PaulM50 Bit Poster

    Messages:
    3
    Hi, I have upgraded to big sur beta 8, ran that command above, then recreated my vm and it works
     
    JesseH1 likes this.
  2. JesseH1

    JesseH1 Bit Poster

    Messages:
    3
    Yup, that did it for me too, after upgrading to Big Sur dev beta 8 (build 20A5374i).

    I didn't need to recreate my VM or even restart it -- I started it back up from a suspended state and the bridged networking came up without missing a beat.
     
  3. RomainP1

    RomainP1 Bit Poster

    Messages:
    7
    Same update to beta 8, I re imported my Bootcamp and still have the problem
    ID 350260888
     
    haraldm7 likes this.
  4. Jon Drover

    Jon Drover Bit Poster

    Messages:
    2
    Upgraded to dev beta 8, ran the script, and networking is working again.
     
    Maria@Parallels likes this.
  5. PeterH44

    PeterH44 Bit Poster

    Messages:
    7
    Got it working but only as root, after running the shellscript.
    Found no solution for the regular user. Anyone?
     
  6. Maria@Parallels

    Maria@Parallels Kilo Poster

    Messages:
    8,694
    Hello, did you try the Terminal command above?
     
  7. Maria@Parallels

    Maria@Parallels Kilo Poster

    Messages:
    8,694
    The issue is still under investigation with Parallels Engineering Team.
    We will update once solution will be available.
     
  8. GonzaloE1

    GonzaloE1 Bit Poster

    Messages:
    1
    Same issue!
     
  9. Maria@Parallels

    Maria@Parallels Kilo Poster

    Messages:
    8,694
    Hello, please share with us your Parallels Desktop and macOS version.

    Did you try to run the following command in Terminal while Parallels Desktop was not started:
    sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist && sudo killall -9 configd
     
  10. EgieD

    EgieD Bit Poster

    Messages:
    6
    I'm having the same issue and yes I ran the command. Still can't connect...
     
  11. Dr.m17

    Dr.m17 Bit Poster

    Messages:
    3
    me too the same issue
     
  12. jazzamac

    jazzamac Bit Poster

    Messages:
    2
    I ran the command and deleted my VM and created a new one. The VM had network access but my MacBookPro didn't (I couldn't get to any websites or network shares). As soon as I shut down the VM my MacBookPro was back to normal. I tried setting the VM to both shared and bridged network mode and it made no difference.

    Uploaded the support logs: 350484011
     
  13. DonaldA3

    DonaldA3

    Messages:
    1
    • macOS 11.0 Beta (20A5374i) [Big Sur]
    • Parallels 16.0.1 (48919)
    • Windows 10 Pro ISO
    Ran the following command:
    sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist && sudo killall -9 configd

    Still getting the network error.
     
  14. Blondey

    Blondey Bit Poster

    Messages:
    6
    I have the same problem! :(
    - macOS Big Sur Beta 11.0 (20A5374i)
    - Parallel Desktop 16.0.1​
     
  15. Blondey

    Blondey Bit Poster

    Messages:
    6
    I also ran this command, but the error remained:
    sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist && sudo killall -9 configd

    [​IMG]
     
  16. PaulM50

    PaulM50 Bit Poster

    Messages:
    3
    Actually I missed a step in this. What I had to do was go into parallels preferences and restore defaults int he networking part. It seemed to keep creating new vnet adapters each time i fired up a vm. putting it back to defaults, then running that command, i notice it used the 2 default adapters, shared and host only, and then it works
     
  17. Nice to know that you were able to sort out the issue. Please get back to us for any further queries.
     
  18. ZeroCoolSpain

    ZeroCoolSpain Bit Poster

    Messages:
    11
    Hi!!
    I have found the solution. I know that if you open parallells in root session it works but I want to open parallells with my user session.

    The solution?

    sudo -b / Applications / Parallels \ Desktop.app/Contents/MacOS/prl_client_app

    Try it and tell me.
     
    lgu likes this.
  19. ZeroCoolSpain

    ZeroCoolSpain Bit Poster

    Messages:
    11
    May be you need re-create VM
     
  20. PeterH44

    PeterH44 Bit Poster

    Messages:
    7
    sudo -b?
    for what command?
     

Share This Page