VMware Server Networking Options

[LEFT][CODE]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/VMwareServerNetworkingOptions.htm[/CODE]



[URL="http://www.vmware.com/products/server/"]VMware Server[/URL] has a dedicated option(editor) called “[I]Virtual Network Settings[/I]” from where we can play with the virtual networks and adapters:
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image1.jpg[/IMG]
[B]Figure1: VMware Server Virtual Network Settings[/B]
We can have as many as 9 host virtual adapters and 10 virtual networks as you can see below:
VMware virtual host adapters: [B]VMnet1:VMnet9[/B]
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image2.jpg[/IMG]
[B]Figure2: VMware Server Virtual Network Editor(Host Virtual Adapters)[/B]
VMware virtual networks: [B]VMnet0:VMnet9[/B]
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image3.jpg[/IMG]
[B]Figure3: VMware Server Virtual Network Editor(Host Virtual Network Mapping)[/B]
By default we have two virtual adapters enabled: [B]VMnet1 and VMnet8:[/B]
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image4.jpg[/IMG]
[B]Figure4: VMware Server Virtual Network Editor: Default Virtual Adapters[/B]
Also by default there are three virtual networks configured : VMnet0, VMnet1 and VMnet8:
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image5.jpg[/IMG]
[B]Figure5: VMware Server Virtual Network Editor: Default Virtual Networks[/B]
Please note that there is an option to automatically choose a real(physical) network adapter(the first one available) and bridge it to VMnet0. But we can manually select what physical adapter to bridge. VMnet0 network is special, meaning that we cannot bind a virtual network adapter to it. We can only bridge physical adapters to it. This bridge operation means that the VMnet0 network will actually “be a part” from our real network to which the bridged physical adapter belongs. So we can’t define any subnet ranges on it. Also if we have multiple physical adapters if we bridge one of these adapters to any VmnetX network automatically this adapter will be excluded from the bridge menu of VMnet0 network.
The “Automatically choose an available physical adapter to bridge to VMnet0” option:
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image6.jpg[/IMG]
[B]Figure6: VMware Server Virtual Network Editor: Automatic Bridging[/B]
Bellow the specified excluded network adapter was bridge to VMnet9 and thus it cannot be bridge to VMnet0:
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image7.jpg[/IMG]
[B]Figure7: VMware Server Virtual Network Editor: Excluded Adapters[/B]
As we start and add virtual adapters they are automatically added to a virtual network:
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image8.jpg[/IMG]
[B]Figure8: VMware Server Virtual Network Editor: Added Virtual Adapter and Virtual Networks[/B]
And the VMware Network Adapter VmnetX will show up on our real host in its [I]Network Connection[/I] panel:
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image9.jpg[/IMG]
[B]Figure9: VMware NICs[/B]
[B][U]Note:[/U][/B] If you don’t disable these network adapters on your PC, your computer will be directly connected to the virtual networks(for example leaving connected VMware Network Adapter VMnet2 means that you can direcly access the virtual hosts from VMnet2(like 192.168.10.0/24)).
If we add a VM and then we take a look at its network options for its Ethernet adapter we will notice that we have four options of network connections: [URL="http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/VMwareServerNetworkingOptions.htm#toAa"][B]Bridge[/B][/URL], [URL="http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/VMwareServerNetworkingOptions.htm#toBb"][B]NAT[/B][/URL], [URL="http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/VMwareServerNetworkingOptions.htm#toCc"][B]Host-Only[/B][/URL] and [URL="http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/VMwareServerNetworkingOptions.htm#toDd"][B]Custom[/B][/URL].
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image10.jpg[/IMG]
[B]Figure10: VMware VM Network Connection[/B]
The VMnet1 adapter and network are for the “[B]Host-Only[/B]” network connection option and the VMnet8 adapter and network are for the ”[B]NAT[/B]” network connection option. These adapters are selected by default by VMware to accomplish these tasks. So if you select the “Host-only” option, the VM will use automatically the VMnet1 network and adapter. ”NAT” goes with VMnet8 adapter and network. They do have some IP address ranges and DHCP Scopes enabled on them by default.
To access these settings click on “>” in the “Host Virtual Network Mapping” tab:
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image11.jpg[/IMG]
[B]Figure11: VMware Virtual Network Editor: Choosing Subnet[/B]
The subnet options:
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image12.jpg[/IMG]
[B]Figure12: VMware Virtual Network Editor: Subnet Options[/B]
The DHCP settings:
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image13.jpg[/IMG]
[B]Figure13: VMware Virtual Network Editor: DHCP Options[/B]
Taking our time and digging through the Help file provided by VMware we can find plenty of information about virtual networks and virtual adapters.
Let’s analyze them one by one.
Bridge
The VM configured with this setting uses an IP address from our physical network and will have full access to our network resources. This means it can access Internet, a DHCP server located on our LAN, files shared and much more. As said above if we have a DHCP server our VM can obtain its IP address and other network settings from that server. It’s like having a separate computer on our network because this VM is also fully accesible from any host on our real LAN. This setting can be used in many scenarios.
NAT
This option allows us to access some TCP/IP based resources on the host system (like our Internet connection) without requiring an IP address from our real LAN. Instead the VM will use an IP address which belongs to VMnet8 virtual network. The VM is not accesible from any hosts located on the real LAN(obvioulsly except from our host), but VMware provides us some tools to make some services running on this VM available to the rest(see bellow).
This is VMnet8 adapter enabled on our real host:
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image14.jpg[/IMG]
[B]Figure14: VMware VMnet8 on Real PC[/B]
On the VM the IP settings will look like bellow(they were assigned by the DHCP service from VMware Server):
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image15.jpg[/IMG]
[B]Figure15: VM Network Settings[/B]
Also the NAT setting has some options. If we click the ”Edit” from the “NAT” tab on “Virtual Network Editor”:
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image16.jpg[/IMG]
[B]Figure16: VMware Virtual Server Virtual Network Editor: NAT(Edit)[/B]
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image17.jpg[/IMG]
[B]Figure17: VMware Virtual Server Virtual Network Editor: NAT(Edit/Port Forwarding)[/B]
We will get the above window. Note the “Port Forwarding” button. To explain it let’s consider the following scenario: a real host with the IP address of 192.168.22.3 is holding our VM. If we use this button and add a port mapping we can “publish” for example a web server located on the VM which will be accessible from all hosts on our real LAN. With the bellow settings: on the real host the TCP port is 80 and the web server configured on the VM is listening on port 80(TCP) also. So any host from our real LAN can contact this web server by [URL="http://192.168.22.3/"]http://192.168.22.3:80[/URL] or we can use a DNS server to give it a name.
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image18.jpg[/IMG]
[B]Figure18: VMware Virtual Server Virtual Network Editor: NAT(Edit/Port Forwarding Options)[/B]
Host-Only
Enables us to have a VM which is connected to our real host but invisible for other devices on our real LAN.For example, I have a VM with Windows XP SP2 installed on it configured with this network setting. My VMnet1 network belongs to 192.168.80.0/24 and the VMnet1 adapter is enabled on my real host. It has an IP address of 192.168.80.1. My virtual XP can use the DHCP server from VMware Server and obtain automatically an IP address belonging to this subnet. Bellow are the network setting from both machines, real and virtual:
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image19.jpg[/IMG]
[B]Figure19: VMware VMnet1 NIC on Real PC[/B]
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image20.jpg[/IMG]
[B]Figure20: VM Network Settings[/B]
I can ping and access network shares from 192.168.80.1 to 192.168.80.128 and vice-versa.
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image21.jpg[/IMG]
[B]Figure21: Ping 192.168.80.1 to 192.168.80.128[/B]
As VMware says, it is a private virtual network shared between the host and any VM configured with this option. Also all VM using this settings are located on the same virtual network, meaning that they can “see” each other.
Custom
Using this setting we can setup complex network designs. For this option we have left seven virtual networks: VMnet2, VMnet3, VMnet4, VMnet5, VMnet6, VMnet7 and VMnet9. Note that this networks are also host-only networks and the VMs which belongs to them are accessible from our host if the corresponding virtual adapter is enabled on our host.
Misc Options
We can disable DHCP and NAT from VMware if we don’t need them.
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image22.jpg[/IMG]
[B]Figure22: Virtual Network Editor Stop/Disable NAT[/B]
Stop DHCP:
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image23.jpg[/IMG]
[B]Figure23: Virtual Network Editor Stop DHCP[/B]
Go to the [I]Services[/I](on our real host)and disabled the Vmware DHCP and NAT services. Below I have also configured the two required services: [I]VMware Authorization Service[/I] and [I]VMware Registration Service[/I] to be manually started in order to optimize my PC performance. I will start them manually when I need to use VMware Server.
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/Services%20on%20Real%20PC.jpg[/IMG]
[B]Figure24: Services on Real PC[/B]
If you are curios and take a look at the “Local users and Groups” on your PC you will see that VMware has created a new user and a new group listed below. You should not touch these two.
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image25.jpg[/IMG]
[B]Figure25: Local Users on Real PC[/B]
[IMG]http://www.carbonwind.net/VMware/VMwareServerNetworkingOptions/image26.jpg[/IMG]
[B]Figure26: Local Groups on Real PC[/B]
The disscusion about routing from [URL="http://www.carbonwind.net/Misc/VPCNetworkingOptions/VPCNetworkingOptions.htm"]VPC Networking Options[/URL] applies here too so I won’t repeat it
[/LEFT]