Changes

Jump to: navigation, search

VMware Server 2.0 DHCP Configuration

484 bytes added, 18:49, 29 May 2016
m
Text replacement - "<google>BUY_VMWARE_SERVER_2_BOTTOM</google>" to "<htmlet>vmware</htmlet>"
<table border="0" cellspacing="0" width="100%">
<tr>
<td width="20%">[[VMware Server NAT Configuration|Previous]]<td align="center">[[VMware Server 2.0 Essentials|Table of Contents]]<td width="20%" align="right">[[Managing VMware Server 2.0 Virtual Disks|Next]]</td>
<tr>
<td width="20%">VMware Server NAT Configuration<td align="center"><td width="20%" align="right">Managing VMware Server 2.0 Virtual Disks</td>
</table>
<hr>
 
 
<htmlet>vmware</htmlet>
 
 
In order for a client to connect to a TCP/IP based network, it needs a Internet Protocol (IP) address which uniquely identifies it among the other devices connected to the network. In addition, the addresses of one or more DNS servers and a gateway may optionally be configured. One way to configure this is to manually assign this information to each client on the network. Whilst this approach can work for a small network, it quickly becomes unmanageable in larger enterprises. To alleviate this problem, the Dynamic Host Configuration Protocol was created. This takes the form of one or more servers on a network which dynamically allocate IP addresses and other network configuration information to network clients.
/etc/vmware/vmnet''n''/dhcpd/dhcpd.conf
where ''n'' represents the number of the virtual network, for example ''/etc/vmware/vmnet1/dhcpd/dhcpd.conf''. A typical dhcp.conf file will read as follows when viewed in a suitable text editor:
<pre>
* '''option domain-name''' - The optional name of the network domain. For example, ''techotopia.com''.
 
 
<htmlet>vmware</htmlet>

Navigation menu