Hiya Folks. Somewhere in the last few versions of Parallels, DHCP stopped working for me. I'm currently running Build 3188, and unfortunately, didn't notice what version things quit for me. The odd part is, everything works fine if the hosting Mac (a Macbook Pro) is using its wireless adapter. It's just the wired adapter for which DHCP doesn't work. I haven't taken too close a look at what's happening on the wire, but the client appears to be able to receive DHCPNAK-type messages. It's just the DHCP requests that go unanswered. This happens with both Linux and OpenBSD client sessions, so it does not appear to be a problem with the hosted OSes. Shared networking, of course, works just fine. Does anyone have an idea what is going on? Would sniffing DHCP session itself shed some light, or is this a known problem?
Are you using wireless on your OSX? Do one of two things or try both. First place Parallels Network Adaptor in Shared Networking mode. You should now be online but your Guest Host will not bet getting an IP address from your Router. It will be getting one from OSX. See if you can get online. Once that is determined working reboot your router. Once it's rebooted check again that you can get online on both OSX and Guest Host. Once that is determined working switch your Parallels back to Default Adaptor and you should be online again and DCHP should be working fine for you again. The problem is an issue with the OSX and using it's wireless. Switching to wired connection will more than likely fix any DHCP issues with the Guest Host. I know Apple is coming out with an update for Airport. If you haven't already make sure you have all current Apple updates. I hope this help you.
i have also found that if youre in shared mode and you cant get a connection using wireless, setup the VM to be in shared mode, then, when it has an IP from parallels, start the Internet Sharing on OSX between the parallels interface(s) and the airport.
Hi Folks. Thanks for the quick replies. To be clear: The Mac can ALWAYS get an IP address, via both its wired, or wireless interfaces. The Guest OSes can ALWAYS get an IP address via shared networking The Guest OSes can ALWAYS get an IP address via DHCP when the Mac is using the Wireless interface The Guest OSes can NEVER get an IP address via DHCP when the Mac is using its Wired network. I see this behavior in two separate locations, with two different wireless and wired routers (respectively), and with two different Guest OSes. In other words, I'm fairly sure the problem is in Parallels, specifically, with Bridged Ethernet and the Wired ethernet adapter.
Have you tried re-installing Parallels tools and/or Parallels? It sounds like you are running into your issue with Bridged networking. Have you tried manually changing the MAC address of the virtualized ethernet card (you can do this from the Parallels Properties window)? I found this to clean things up as I would usually not allow two IPs to a single card. Also, make sure that static is not required on your wired network, but DHCP is enabled via Wireless, this is not uncommon.
Are you in a home netowrk or in a company's network? Do you know where your DHCP server is in the wired network? Some companies' DHCP server, for security reason, are configurated with MAC address filtering. When you do bridge network, Parallels fabricates a MAC address and try to fool the DHCP server thinking there is a different NIC asking for IP. If the MAC address is outside of the filtering range, DHCP will not response.
The solution to my 3188 networking problems was found in this post: http://forums.parallels.com/post50001-4.html Basically: Completely shut down your virtual machine (not suspend/pause), then reboot OS X. This seems to have been triggered by the 10.4.9 upgrade.
Cheers Westside_guy and gegervision! Graceful reboots fix a multitude of things... And re-installing Parallels Tools almost deserves the title 'the water of life'.
It's probably overkill, but because of some problems I ran into during the beta testing... I now make it a habit to uninstall Parallels Tools from my VM before upgrading to a new build of Parallels. It avoids any issues that might come up involving the Tools being upgraded (which was problematic at one point in the beta cycle, but I don't remember exactly when).
