Network Initialization Failed

Any news? I can't use it for work and it's not possible that after more than 2 months anybody can solve this problem!!
 
Kiki said:
And what exactly is "your case"? Witch PD version and bootcamp or normal VM?

Because, as excepted. It does not work.
Click to expand...

Like the other posts since almost 2 weeks, my case is about the most recent versions: MacOS 11.0.1 Big Sur and Parallels Desktop 16.1.1.
 
Why is the support so silent on this? The business edition doesn't deserve the attention ?
I tried everything, and running with sudo is just ridiculous since the workflow is broken, fix it already, give a proper communication on social
 
For Big sur user's The only solution for now is to use the parallel version 15 & When you want to run the Parallel use this 2 command lines and run it on terminal
Run terminal :
first run this line : export SYSTEM_VERSION_COMPAT=1
Second Run this line :
open -a "Parallels Desktop"
this is the only solution until parallel team cover the network problem in the new version
 
Hello Support. I just upgraded to Big Sur 11.0.1, and am running Parallels 16.1.1. I'm having the same network problems as everyone else. I have a bridged/bonded network connection on my Mac (802.3ad/LACP), named "bond0" by macOS. It was working fine in Catalina. In Big Sur, "bond0" is MISSING from the Bridged Network drop-down list. Being a bond, individual network adapters will not work. I've tried both terminal commands being circulated in these forums, but nothing is working. I have many NAS shares, so cannot be using bridged mode. Any insight from the development team? Thanks.
 
JohnD44 said:
Hello Support. I just upgraded to Big Sur 11.0.1, and am running Parallels 16.1.1. I'm having the same network problems as everyone else. I have a bridged/bonded network connection on my Mac (802.3ad/LACP), named "bond0" by macOS. It was working fine in Catalina. In Big Sur, "bond0" is MISSING from the Bridged Network drop-down list. Being a bond, individual network adapters will not work. I've tried both terminal commands being circulated in these forums, but nothing is working. I have many NAS shares, so cannot be using bridged mode. Any insight from the development team? Thanks.
Click to expand...


For Big sur user's The only solution for now is to use the parallel version 15 & When you want to run the Parallel use this 2 command lines and run it on terminal
Run terminal :
first run this line : export SYSTEM_VERSION_COMPAT=1
Second Run this line :
open -a "Parallels Desktop"
this is the only solution until parallel team cover the network problem in the new version
 
abdeljalilm said:
For Big sur user's The only solution for now is to use the parallel version 15 & When you want to run the Parallel use this 2 command lines and run it on terminal
Run terminal :
first run this line : export SYSTEM_VERSION_COMPAT=1
Second Run this line :
open -a "Parallels Desktop"
this is the only solution until parallel team cover the network problem in the new version
Click to expand...
Do we have to do this each time, or once is enough?
 
I'm routing all my VM traffic through WiFi, which is not ideal, but getting me by 'till Parallels fixes this major networking bug.
 
(Actually I now have the "black screen" issue with v15 so this fix doesn't solve anything for me sadly, btw it's a pain posts can't be edited)
 
It looks like the error cause is a non-existent network interface (in my case, en6). When launching the VM, app tries to create a bridged interface, but fails if we're not the root (it also fails with sudo -u).
Workaround: sudo -bEH /Applications/Parallels\ Desktop.app/Contents/MacOS/prl_client_app
 
Hi all,

So it does seem that running this command in terminal will get networking working with Parallels 16.1.1.

sudo -b /Applications/Parallels\ Desktop.app/Contents/MacOS/prl_client_app
However, it seems if you launch Parallels this way, Coherence now no longer works.
If I launch parallels without the above command (regular way you would launch), it will load with the network error message, but then Coherence works. So it seems that although that workaround fixes the network issue, it breaks Coherence.

What's the deal?!?
 
Americanninja said:
Hi all,

So it does seem that running this command in terminal will get networking working with Parallels 16.1.1.

sudo -b /Applications/Parallels\ Desktop.app/Contents/MacOS/prl_client_app
However, it seems if you launch Parallels this way, Coherence now no longer works.
If I launch parallels without the above command (regular way you would launch), it will load with the network error message, but then Coherence works. So it seems that although that workaround fixes the network issue, it breaks Coherence.

What's the deal?!?
Click to expand...
When launching with sudo Parallels won't be in the same session as you (the regular user) are - it basically switches the user, so as long as you're not logged in to a graphical session Coherence (and a lot of similar stuff) won't probably work.
 
fuckroyal said:
When launching with sudo Parallels won't be in the same session as you (the regular user) are - it basically switches the user, so as long as you're not logged in to a graphical session Coherence (and a lot of similar stuff) won't probably work.
Click to expand...

Thanks for the reply and explanation. So given that there is no fix provided by parallels (which is absolutely pathetic at this stage), what option do I have to use with network and coherence. Is there a way I can launch the application or get both network and coherence to work? Thanks in advance!
 
I see that people with geniue Parallels licenses does not have any issue at all about network configuration. My clients are asking me sometimes about it and i found out they have pirated versions of Parallels. I told them to buy license from Parallels. And when they buy license directly from Parallels, issue is fixed.
 
You must log in or register to reply here.
Back
Top