Networking – No internet on host OS (OS X Lion) when VMware Fusion is running

nat;networkingvmware-fusion

I have installed OS X Mountain Lion as a VM in VMware Fusion (version 4.1.2) for environment testing. The host OS is OS X 10.7.4, and is connected to the internet via a wired connection (in fact I get the same problem if it is connected via wireless as well).

As long as VMware Fusion is running, my internet for the Host OS stops working, but remains functional inside the VM.

I am using NAT for VMware Fusion.

For additional testing, I have an Ubuntu box on Virtual Box. When VMware Fusion is off, I have internet on both my host OS and the Ubuntu VM, and when VMware fusion is running, I have no internet connection except inside VMware Fusion.

VMware Fusion blocks internet even if the actual VM is suspended.

Best Answer

You have likely set your VM to use the same IP address as your host machine. This article talks about it. If both are using the same address, any traffic destined to the IP address of the network adapter used by the host OS will be passed to the VM.

Simplest solution is to ensure everyone has their own IP address (the Host machine has one, and the VM has one that is on the same network).

This article walks you through reconfiguring the virtual network adapter. The part you need is quoted here:

To change the configuration of an existing virtual network adapter, follow these steps.

  1. Open the virtual machine settings editor (VM > Settings).

  2. Select the adapter you want to modify.

  3. Select the network type you want to use — Bridged, NAT, Host-only or Custom.

  4. If you select Custom, choose the VMnet virtual network you want to use for the network from the drop-down list.

  5. Click OK to save your changes and close the virtual machine settings editor.

  6. Be sure the guest operating system is configured to use an appropriate IP address on the new network. If the guest is using DHCP, release and renew the lease. If the IP address is set statically, be sure the guest has an address on the correct virtual network.

Item 6 is likely to be what you need to focus on. Remember to make sure the IP address for the VM isn't in use elsewhere in the network.

Related Question