Custom Nat And Dhcp Configuration On A Windows Host; Considerations For Using Nat - VMware 4 User Manual

VMware Workstation 4 User's Manual
226
The [incomingudp] Section
This section is used to configure UDP port forwarding for NAT. In this section, you can
assign a port number to an IP address and port number on a virtual machine.
The following line shows the format used in this section. It illustrates a way to forward
X server traffic from the host port 6000 to the virtual machine's port 6001.
6000 = 192.168.27.128:6001
This example creates a mapping from port 6000 on the host to the IP address
192.168.27.128 and port 6001. When this mapping is set and an external machine
connects to the host at port 6000, the network packets are automatically forwarded to
port 6001 on the virtual machine with IP address 192.168.27.128.

Custom NAT and DHCP Configuration on a Windows Host

If you are an advanced user on a Windows host computer, you may wish to make
custom configuration settings by editing the NAT and DHCP configuration files. If your
host operating system is installed on the C drive, the configuration files for NAT and
DHCP are in the following locations:
• NAT: C:\Documents and Settings\All Users\Application
Data\VMware\vmnetnat.conf
• DHCP: C:\Documents and Settings\All Users\Application
Data\VMware\vmnetdhcp.conf
Note: In VMware Workstation 4, you can change many key NAT and DCHP settings
using the Virtual Network Editor (Edit > Virtual Network Settings). However, if you
have made manual changes to the configuration files, some or all of those changes
may be lost when you use the Virtual Network Editor. If you have made manual
changes, you should make backup copies of the files before changing any settings in
the Virtual Network Editor. After making changes in the Virtual Network Editor, you
can copy your manual changes back into the appropriate configuration files.

Considerations for Using NAT

Because NAT requires that every packet sent and received from virtual machines is in
the NAT network, there is an unavoidable performance penalty. Our experiments
show that the penalty is minor for dial-up and DSL connections and performance is
adequate for most VMware Workstation uses.
NAT is not perfectly transparent. It does not normally allow connections to be
initiated from outside the network, although you can set up server connections by
manually configuring the NAT device. The practical result is that some TCP and UDP
protocols that require a connection be initiated from the server machine — some
www.vmware.com