No network cause DHCP not working!!

I have been working with a crippled Parallels for months now and I am really getting annoyed by it.
The problem is that DHCP for IPv4 is not working in my VM when I am using Shared Network (you know the Recommended and default setting).
So I am forced to use Bridged Network, which also means I cannot use the VPN running on my MacBook, which is really annoying.

I am running a clean install of the latest macOS 14.3 on a M2 using the latest Parallels 19.1.1 (54734). (I thought I give reinstalling my MacBook another try, but that doesn't help.)

What do I have to do to get my Shared Network working?!?!

 

I am not sure what happened, but it works now. I have been messing around trying a possible fix and found DHCP was working. Settings are back to as they were and it still works. So I have no idea why it got fixed, maybe an update somewhere, but it is working now. So I am happy again.

 

Just an update that I am getting so very fed up with this problem.
The network has been working fine for a while and now it is broken again. Only bridged works, but not shared or local. Something in Parallels is really messed up.

I think the problem really is with Parallels environment and not somewhere in the macOS system. I come to this conclusion because Parallels says the VM has an IP, but the VM itself doesn't get it. So the problem is somewhere between Parallels and the VM.

 

I have the same problem and it was running me crazy for weeks! I have a Mac M1 Pro running Sonoma (14.3.1) and after updating to 19.2.1 the shared network stopped working on my Windows 11 VM.
I have read all the suggestions but nothing worked. I tried reinstalling the network device in the device manager, everything in https://kb.parallels.com/8978 and also removing all network devices through command prompt: netcfg -d, changing the performance parameters of the vm, reinstalling Parallels Desktop (even removing all the residual files) but nothing worked. Sometimes switching between bridged and shared network would work for a few minutes, but after that it stopped working again. Bridged network would work, but was no solution for me, because I needed the VPN connection installed on my Mac (not Windows).
Then I tried controlling the VM through the Mac terminal and strangely it worked!
Open a command prompt. First you have to find the right ID for the network interface:
/Applications % prlctl list "Windows 11" -i | Grep -E 'net[0-9] \('
Where "Windows 11" is my VM name (replace it with your own).
It would output something like:
net0 (+) type=shared mac=001C42111753 card=virtio
Now for me there was only one output, there could be more. Now use the ID on the next command:
prlctl set "Windows 11" --device-set net0 --type shared
You can use --type bridged to set it to bridged.
Wait a few seconds and see if it connects.
It worked for me, hopefully also for you.

 

I have the EXACT same issue on Intel-silicon mac, so I don't think it's related to the ARM silicon. (Report number 4938285)

I just got off the chat with tech support, and they "fixed" the issue by changing to a static manually assigned IP address. Which is a good workaround, I agree, but doesn't actually resolve the issue with DHCP. Hopefully Parallels can figure out what's wrong here.