1,798
edits
Changes
→Configuring VMware Server 2.0
It is important to note that at this point that we are simply deciding what networking options will be available to the guest systems. Just because an option is selected now, it does not mean that any of the virtual guests have to be configured to use it. Similarly, if at a later date a networking option is required which was not selected at this point it may be enabled simply by re-running the ''vmware-config.pl'' script and selecting the missing option.
In the case of Bridged network support the configuration script will prompt for a name for the network and, in the case of hosts with multiple ethernet adapters, the adapter to be be used for the bridge. Note that even though an ethernet adapter is used for the bridge it will still be available for continued use by the host.
As with Bridged network support, the NAT option requires that a name be assigned. The script will provide the option to probe the network to locate an unused private subnet address range. Either choose the probe option, or enter a known available subnet for the NAT addressing scheme. Once selected, virtual guests will communicate with each other using the these private subnet addresses, but will communicate with the external network using the IP address of the host.
Host-only networking will similarly require a name and an unused private subnet which may be entered manually or automatically identified by the configuration script. Once the network configuration process is complete, ''vmware-config.pl'' will load the VMware Server network kernel module (vmnet) into the running kernel of the host operating system.
The next step of the configuration involves defining how the VMware Server management interface will be accessed, both for local and remote administration. VMware Server 2.0 differs from previous releases of the product in that the management interface is entirely browser based so both local and remote administration tasks will be performed using a web browser. The first option to configure is the port through which the VMware Server environment will be accessed from remote systems. The default is port 902. Finally, the HTTP and secure HTTPS access ports need to be specified. By default these are 8222 and 8333 respectively. Therefore, if the host system has an IP address of 192.168.2.21, then the management interface would be accessed securely by entering 192.168.2.21:8333 in a browser URL field. Different ports may, of course, be specified if required, for example to avoid conflict with other applications or to accommodate firewall restrictions.
