[an error occurred while processing this directive] [an error occurred while processing this directive]
VMware Workstation 3.2
A host-only network uses a private virtual network. The host and all virtual machines configured for host-only networking are connected to the network through a virtual switch. Typically all the parties on this private network use the TCP/IP protocol suite, although other communication protocols may be used.
A network address translation (NAT) configuration also sets up a private network, which must be a TCP/IP network. The virtual machines configured for NAT are connected to that network through a virtual switch. The host computer is also connected to the private network used for NAT.
Each virtual machine and the host must be assigned addresses on the private network. This is typically done using the DHCP server that comes with VMware Workstation. Note that this server does not service virtual (or physical) machines residing on bridged networks.
Addresses can also be assigned "statically" from a pool of addresses that are not assigned by the DHCP server.
When host-only networking is enabled at the time VMware Workstation is installed, the network number to use for the virtual network is automatically selected as an unused private IP network number. To find out what network is used, run ipconfig from a command prompt on a Windows host or ifconfig on a Linux host.
A NAT configuration also uses an unused private network automatically selected when you install VMware Workstation. To check what network is used in a Windows .NET Server, Windows XP, Windows 2000 or Windows NT guest, run ipconfig. In a Windows Me or Windows 9x guest, run winipcfg. In a Linux guest, run ifconfig.
Using DHCP to assign IP addresses is simpler and more automatic than statically assigning them. Most Windows operating systems, for example, come preconfigured to use DHCP at boot time, so Windows virtual machines can connect to the network the first time they are booted, without additional configuration. If you want your virtual machines to communicate with each other using names instead of IP addresses, however, you must set up a naming convention, a name server on the private network, or both. In that case it may be simpler to use static IP addresses.
In general, if you have virtual machines you intend to use frequently or for extended periods of time, it is probably most convenient to assign them static IP addresses or configure the VMware DHCP server to always assign the same IP address to each of these virtual machines.
On a Linux host, you configure the host-only DHCP server by editing the DHCP configuration file for VMnet1 (/etc/vmware/vmnet1/dhcp/dhcp.conf). To configure the DHCP server for the NAT network, edit the configuration file for VMnet8 (/etc/vmware/vmnet8/dhcp/dhcp.conf).
Editing the DHCP server configuration file requires information that is best obtained directly from the DHCP server documentation. Consult the manual pages dhcpd(8) and dhcpd.conf(8).
Follow these steps to change the subnet of the DHCP server for the host-only network on VMnet1. In this example, you set the IP address of your host-only network to 192.168.3.1. To change the subnet used by a host-only DHCP server, you need to make the change to the IP address in two places: in the registry and in the vmnetdhcp.conf file.
To make corresponding changes to the DHCP server for the NAT network, follow the same procedure, with these changes:
For virtual machines that you do not expect to keep for long, use DHCP and let it allocate an IP address.
For each host-only network, the available IP addresses are split up using the conventions shown in the table below, where <net> is the network number assigned to your host-only network. VMware Workstation always uses a Class C address for host-only and NAT networks.