Killing this process stops the DHCP server, and lets you run your own DHCP server in the isolated network. Fortunately, this DHCP server is easy to spot in Activity Viewer (or top) - it's called Prl_dhcpd. You don't want your host OS X machine to be a DHCP server on your isolated network. If, like me, you need to test networks that include a DHCP server (for LDAP settings, NAP settings, etc.), this is a problem. Killing OS X's Parallels network adapter just dumps the VMs back into Bridged mode. While it gives you the ability to adjust the DHCP scope, there is no handy way to turn it off. But then Parallels does something annoying: It adds the Mac OS X machine to that isolated network and fires up a DHCP server. With Host-only, the VM is placed in an isolated network, as desired. With Bridged, the VM connects to your Mac's network and is basically on the local network. Parallels, by default, offers two choices for VM networking - Bridged or Host-only.

The lack of 'undo' disks is still a major problem, but I've found a way to build an internal, isolated network for your VMs (Virtual Machines) to play in. I need the XP VM for some work apps that do not run in WINE, and it is a pain using a laptop but having to depend on a wired network connection.I've been playing with Parallels Desktop on OS X as a replacement for Virtual PC on Windows in terms of testing complex Windows network designs. The worse part is when there is no network connection, the VM itself slows to crawl. I have a WEP key for my wireless network, but shouldn't my adapter on the host machine take care of that? I know with Paralells on a Mac it does, but all my Vmware Server experience is in the enterprise where I never had to have wireless support for vm's. I've even removed my VMware server networking config and re-ran it adding only the wireless adapter as a bridged adapter and then added that to the VM, and still no joy. If I switch it to custom to use vmnet2 (where the wireless adapter is bridged to) it doesn't get an IP.

Now, I bridged both network adapters, but when I add a second 'bridged' network adapter to my VM it seems to just bridge to my ethernet port.

:) When I attempt to use my wireless card, it won't get an IP at all. It gets an IP and all is right in the world. When I use my actual ethernet port, I have no problems. I am trying to run a Windows XP SP2 VM on my workstation. I installed VMWare following this tutorial: I am running Gutsy on a Dell Latitude D610 with the restricted Broadcom 43xx Chipset driver installed for my wireless adapter.

Parallels bridged network not working