I've noticed that every once in awhile, my host OS and virtual machines will not be able to talk to each other after a restart. The problem seems to be that my host ethernet interface (en2 in this case) never gets a dhcp address from the parallels dhcpd daemon.
Symptoms usually include the following line in the Apple Console:
Aug 23 09:38:45 nemo prl_dhcp[205]: Can not bind to en2.
Until today my main workaround was to restart my laptop over and over again until eventually dhcp started working and I got an IP address on en2.
However, today I discovered a more reliable workaround, which is to start up the prl_dhcpd manually. It's in /Library/StartupItems/Parallels/prl_dhcpd
Why the daemon is not starting up properly I have no idea. Anyone else run into this problem?
The following things might be unusual about my setup: using host-only networking; using dhcp for all networks; local network is 10.0.xx.xx (255.255.0.0 netmask) and using default 10.37.xx.xx for parallels; Cisco VPN client 4.9.00 (0050) is installed but not generally in use
Symptoms usually include the following line in the Apple Console:
Aug 23 09:38:45 nemo prl_dhcp[205]: Can not bind to en2.
Until today my main workaround was to restart my laptop over and over again until eventually dhcp started working and I got an IP address on en2.
However, today I discovered a more reliable workaround, which is to start up the prl_dhcpd manually. It's in /Library/StartupItems/Parallels/prl_dhcpd
Why the daemon is not starting up properly I have no idea. Anyone else run into this problem?
The following things might be unusual about my setup: using host-only networking; using dhcp for all networks; local network is 10.0.xx.xx (255.255.0.0 netmask) and using default 10.37.xx.xx for parallels; Cisco VPN client 4.9.00 (0050) is installed but not generally in use