Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Parallels 16: Network initialization failed.

L

Lukeit

macrumors regular
Original poster
Feb 28, 2011
206
66
Shanghai, China
I'm on Parallels 16.0.1 and since I have upgraded to Mac OS 11 Big Sur when I start my Windows 10 virtual machine I get this error message "Network initialization failed. Your virtual machine will continue working normally but will no have no network connection".

I tried the solution posted on some forums to use Terminal with this command line:
"sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist && sudo killall -9 configd" but to no avail and the problem still persists.
Anyone with some ideas? Does Parallels 16.1 solves this issue?
Many thanks for your help, support and ideas.
 
I had the same issue. Do this AND disable internet sharing in system preferences. That made the trick for me.
 
Same issue here
Using Parallels 16.0.1 and have just upgraded to Mac OS 11 Big Sur
Tried:
1) "sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist && sudo killall -9 configd" + Restart

Internet Sharing is disabled


Any ideas on how to solve or woraround this issue?
 
  • Like
Reactions: agarakash
Seems to be a known issue
This workaround works for me:

1) Quit Parallels (shutdown any running VM)
2) Open terminal and type this command
sudo -b /Applications/Parallels\ Desktop.app/Contents/MacOS/prl_client_app
 
  • Like
Reactions: Gaspy, agarakash and Fredyk84
maconceicao said:
Seems to be a known issue
This workaround works for me:

1) Quit Parallels (shutdown any running VM)
2) Open terminal and type this command
sudo -b /Applications/Parallels\ Desktop.app/Contents/MacOS/prl_client_app
Click to expand...
Worked for me BUT lost integrity of home folders (desktop, downloads, etc). Reinstalled Parallels toolbox and revert to previous state, i.e everything works fine except network :(
 
  • Like
Reactions: karayuschij
Parallels was unable to provide help on this, but I needed a workaround and here it is. I have only been able to reproduce this bug with bridged networking.

Parallels is reading the "Default" and "Ethernet" adapters incorrectly. I am close to figuring out the pattern, but even creating an "Ethernet 2" does not help. The workaround is to use the wi-fi adapter if "Ethernet" is your primary or "Ethernet" if wi-fi is your primary.

Steps to fix:

Assume: Connection to the Mac is wired and "Ethernet" is the Mac's primary network.
Enable Wi-Fi and allow it to connect to your network. You will have 2 IP addresses, but as long as Wi-Fi is later than "Ethernet" in the "Set Service Order", you are all good.
For the network of the guest machine, choose "Wi-Fi". There is another tiny bug where you may have to select it twice if the machine is active. Make sure it was selected.

Bridged networking will now work, albeit over wi-fi. I intend to experiment with a second physical network adaptor, but for right now I just needed my virtual machines up and running.
 
  • Like
Reactions: MSReading and w1z
I have the same issue, I tried the fixes mentioned in this thread but no hope. any solution?
 
1) Quit Parallels (shutdown any running VM)
2) Open terminal and type this command
sudo -b /Applications/Parallels\ Desktop.app/Contents/MacOS/prl_client_app

that worked for me also! thanks!! running parallels 16.0.1 on big sur
 
Check for Updates on your installation, I got Parallels 16.1.1 today.
Screen Shot 2020-11-22 at 7.44.49 PM.png
 
Updated to Parallels 16.1.1 did not work for me, still no network with Parallels 16.1.1 & Big Surr.

The suggested command from @dabiohazard only works for one time. I re-installt he virtual machine after the command line. Then, networks works, al seems fine, until I shutdown and re-open. The network issue will be back.
 
T4rb0ch4rg3d said:
Updated to Parallels 16.1.1 did not work for me, still no network with Parallels 16.1.1 & Big Surr.

The suggested command from @dabiohazard only works for one time. I re-installt he virtual machine after the command line. Then, networks works, al seems fine, until I shutdown and re-open. The network issue will be back.
Click to expand...
It works just one time, but I created an "automator" app that send that command to the terminal, so I don't have to open the terminal every time. Try, it could be a nice suggestion for you.
 
kleon2020 said:
It works just one time, but I created an "automator" app that send that command to the terminal, so I don't have to open the terminal every time. Try, it could be a nice suggestion for you.
Click to expand...
Good evening
Can you send the automators app please???? Tanks!!!!
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back