</pre>
Having identified (or compiled) and loaded the appropriate kernel modules the ''vmware-config.pl'' script proceeds to the network configuration phase.
Bridged networking — Configures your virtual machine as a unique identity on the networkIf the virtual guest systems running within the VMware Server environment are not required to have any form of network connectivity, separate from and unrelated to its hostenter 'n'' when prompterd, otherwise enter ''y'' to configure networking options. Other computers on the network can communicate directly with the virtual machineVMware Server 2. Bridged networking 0 provides support for three types of virtual networking and before selecting the network options to be made available to guest systems, it is worth taking a little time to understand each of these options:works with Ethernet* '''Bridged networking''' — Although the guest systems use the physical network connections on the host system, DSLeach guest is treated as an independent client on the network. As such it will obtain an IP address from the network's DHCP server, cable, wireless, and legacy phone modemsor will require a static IP address to be manually configured if DHCP is not used. Guest systems using bridged networking will be able to communicate directly with both the host and other clients on the network to which the host is connected. See “Bridged Networking” on page 207.* '''Network address translation (NAT) — Configures your virtual machine to share the IP and MAC addresses of the host''' — Virtual guests share the IP and MAC address of the host system. The virtual machine shares the host’s public network identityGuests will be able to communicate with other clients on the network to which the host is connected, and has a private identity that is not visible beyond the hostbut will appear to those clients as the host system, rather than as individual network clients. NAT can be useful when you are allowed a single IP address or MAC address by your network administratorthis approach allows multiple systems to operating using a single IP address. You might also use NAT to configure separate virtual machines for handling HTTP and FTP requests, with both virtual machines running off the same IP address or domain* '''Host‐only networking''' - Creates a private sub-net within the host for the guest systems. NAT works with EthernetGuests configured with host-only networking can communicate directly only with the host system and other guests which are also members of the host-only network. The guest systems cannot, DSLhowever, and legacy phone modemscommunicate with the network to which the host is connected. See “Network Address Translation (NAT)” on page 208.Host‐only networking — Configures your virtual machine to allow network access only to a private network on the hostIt is important to note that at this point that we are simply deciding what networking options will be available to the guest systems. With host‐only networkingJust because an option is selected now, the virtual machine can communicate only with the host and other virtual machines in the host‐only networkit does not mean that any of the virtual guests have to be configured to use it. This can be useful when you want a secure virtual machine that is connected to the host networkSimilarly, but available only through the host machineif 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. In this configuration, the virtual machine cannot connect to the Internet. See “Host‐Only Networking” on page 210pl'' script and selecting the missing option.
