VMware Intranet Virtual Machine port mapped to public IP

Issue: A vmware-brought NAT mapping 80 port is not valid causing the virtual machine Web site to map 80 ports to the public IP

Idea: Since the NAT service of Windows Server can map a port to a Hyper-V virtual machine via a loopback adapter (see HTTP://MWT666.BLOG.51CTO.COM/64376/265362/), VMware should be able to , but the configuration steps for the virtual network editor are different.

Step One: Create a loopback Adapter

In Device Manager, select the network adapter, click Add Outdated hardware, point to next

Select Manual Selection, click Next

Select the network adapter, click Next

Vendor selects Microsoft Network adapter to select Microsoft Km-test Loopback Adapter, and the next step is to complete the installation

Step Two: Add the newly installed network adapter to VMware

Open the Virtual network editor

Point to add a network, click OK

Select the newly added network and select Bridge mode, bridge to drop-down select Microsoft Km-test Loopback Adapter

Change, IP is the intranet segment IP. Remember to add the Network Bridge and then change the IP in VMware, the order cannot be reversed.

At the end of the NIC configuration, NAT is configured below.

Step three: Routing and Remote Access configuration

Windows Server 2012 How to install routing with Remote Access is not the focus, do not repeat. Need to emphasize that the Routing and Remote Access functionality requires a domain environment, the related configuration is relatively simple, the article a lot of Baidu casually follow the steps to 5 minutes to complete.

After installation, open the Routing and Remote Access tool

Click Configure, click Next

Select NAT

This is the network card that can sisu the network

This step selects the newly installed virtual adapter

Next

Open Properties dialog box

You can see that the intranet network segment DHCP is already assigned

Open the Properties dialog box for the external network card

This is where the map port is added, and the port you need is written in.

It is important to note that the 80 port already has the rule, edit it

Enter the IP test of the external network card, successfully visit the website of 172.18.5.111 this address

Summary: VMware more popular than Hyper-V more people, hoping to meet this problem of people a little help less detours, I take the detour I go to summarize.

One is to the Loopback adapter property configuration in the check do not remove the original can be, because the author of the test process found to be removed after VMware will not be able to bridge to the network card.

Second, for NIC teaming Nic, although the configuration steps can be successful, but NAT mapping always failed, but I am not sure about this, perhaps I do not configure the other places, if not the combination of network card without consideration.

Third, the configuration of the successful test, do not on the server server you configured or the VMware Intranet segment of the machine test, so that the result is not valid, because no NAT, should find an external network network card on the local area network machine test.