WORKAROUND TO TO RESOLVE A CONFLICT BETWEEN "VMWARE PLAYER", AND "ORACLE VM VIRTUALBOX" IN A "WINDOWS" HOST COMPUTER

SUMMARY:
If you are running both "VMware Player 3" and "Oracle VirtualBox 4" in the same "Windows" host computer, "VMware Player" virtual machines will usually fail to acquire a DHCP IP address when their virtual network adapters are set to "Bridged", unless you perform this simple workaround.

BASIC INFORMATION:
The "VirtualBox Bridged Networking Driver" or "VMware Bridge Protocol" are not compatible with each other. When these two drivers are both "bound" to the same virtual "VirtualBox Host-Only Adapter" of a "Windows" host computer, "VMware Player" virtual machines will usually fail to acquire a DHCP IP address when their network adapters are set to "Bridged". The simple fix is to uncheck one or both of these two conflicting "link layer" network protocols.

STEP-BY-STEP PROCEDURE:

Step 1: Click on the Windows "Start" button of the host computer.

Step 2: Click on "Control Panel" in the "Start menu". Step 3: A "Control Panel" window will be displayed.

Step 4: Double-click on "Network and Sharing Center".

Step 5: Double-click on "Change adapter settings":

Step 6: Perform a right click on the "VirtualBox Host-Only Network" adapter:

Step 7: Click on "Properties" in the pop-up context menu:

Step 8: A "..Properties" box will be displayed:

Step 9: "VirtualBox Bridged Networking Driver" or "VMware Bridge Protocol" are not compatible with each other. Remove the checkmark from one or the other:

Step 10: Click on the "OK" button of the "..Properties" box: