For some configurations, you may need to set up more than one host-only network on the same host computer.
You may, for example, want to have two virtual machines connected to one host-only network, and at the same time have other virtual machines connected to another host-only network so the network traffic on each network is isolated.
Or you may want to test routing between two virtual networks. Or test a virtual machine with multiple network interface cards - without using any physical Ethernet adapters.
On Windows hosts, the first host-only network is set up automatically when you install VMware Workstation.
On Linux hosts, the first host-only network is set up when you run the vmware-config.pl script after you install VMware Workstation, provided you agree to install host-only networking. If you did not agree to use host-only networking, you need to run the script again to set up host-only networking.
To set up the second host-only network, follow the steps outlined below for your host operating system.
Follow these steps to set up the second host-only interface on a Windows host.
/usr/bin/vmware-config.pl
Do you want to be able to use host-only networking in your virtual machines?
Answer Yes.
The wizard reports on host-only networks that you have already set up on the host or, if none is present, configures the first host-only network.
Do you wish to configure another host-only network?
Answer Yes.
Repeat this step until you have as many host-only networks as you want. Then answer No.
Now you have two host-only interfaces (VMnet1 and VMnet2). You are ready to set up your virtual machines for one of the following configurations:
Windows host: Select Network Adapter, then select Host-only (VMnet1) from the drop-down list on the right.
If no network adapter is shown in the list of devices, click Add, then use the Add Hardware Wizard to add an adapter.
Linux host: Click the + sign to expand the Ethernet Adapters list and select the first adapter. From the Connection Type drop-down list on the right, select Host-only.
If the list of devices indicates the adapter is not installed, click Install.
Windows host: Select Network Adapter, then select Custom (VMnet2) from the drop-down list on the right.
If no network adapter is shown in the list of devices, click Add, then use the Add Hardware Wizard to add an adapter.
Linux host: Click the + sign to expand the Ethernet Adapters list and select the first adapter. From the Connection Type drop-down list on the right, select Custom. In the VMnet field, type /dev/vmnet2.
If the list of devices indicates the adapter is not installed, click Install.
Windows host: Select the first network adapter in the list of devices, then select Host-only (VMnet1) from the drop-down list on the right. Select the second network adapter in the list of devices, then select Custom (VMnet2) from the drop-down list on the right.
If you need to add one or more network adapters, click Add, then use the Add Hardware Wizard to add an adapter.
Linux host: Click the + sign to expand the Ethernet Adapters list and select the first adapter. From the Connection Type drop-down list on the right, select Host-only.
If the list of devices indicates the adapter is not installed, click Install.
Select the second adapter and, from the Connection Type drop-down list on the right, select Custom. In the VMnet field, type /dev/vmnet2.
If the list of devices indicates the adapter is not installed, click Install.
At this point you can power on the virtual machine and install your guest operating system. In configurations 1 and 2 you see one AMD PCNet Family Adapter. In configuration 3 you see two AMD PCNet Family Adapters within the guest. Configure the Ethernet adapters as you would physical adapters on a physical computer, giving each an IP address on the appropriate VMnet subnet.
On Windows hosts, you can open a command prompt and run ipconfig /all to see what IP addresses each host-only network is using.
On Linux hosts, you can open a terminal and run ifconfig to see what IP addresses each host-only network is using.
© 1998-2003 VMware, Inc. All rights reserved.