(NAT) rules: Access Protocol Incoming Port Destination IP Destination P... Remove 60. Click on OK. 61. Navigate to VMs and Services I All Hosts. 62. Right-click the Tenant A - VM 1 VM, navigate to Connect or View, and click on Connect via Console. Creating the Gateway for Virtual Machine Communications 63. Log in if necessary. Open a command prompt and run ping 4.2. 2. 2, as shown the following screenshot: C: \Users\Administrator>ping 4.2.2.2 Pinging 4.2.2.2 with 32 bytes of data: Reply from 4.2.2.2: bytes=32 time=19ms TTL=126 Reply from 4.2.2.2: bytes=32 time=11ms TTL=126 Reply from 4.2.2.2: bytes=32 time=17ms TTL=126 Reply from 4.2.2.2: bytes=32 time=13ms TTL=126 Ping statistics for 4.2.2.2: Packets Sent = 4, Received = 4, Lost = 0 <0% loss>, Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 19ms, Average = 15ms C: \Users\Administrator> 64. If you try to ping a DNS name such as www.bing.com, it will fail as currently there are no DNS servers set in the VM. Run the following PowerShell code inside the Tenant A - VM 1 VM: Get-NetAdapter Set-DnsClientServerAddress -ServerAddresses 4.2.2.2 65. You will then be able to ping DNS names such as www.bing.com and browse the Internet using DNS names. C:\Windows\system32>ping www.bing.com Pinging any.edge.bing.com [204.79.197.2001 with 32 bytes of data: Reply from 204.79.197.200: bytes=32 time=11ms TTL=126 Reply from 204.79.197.200: bytes=32 time=9ms TTL=126 Reply from 204.79.197.200: bytes=32 time=16ms TTL=126 Reply from 204.79.197.200: bytes=32 time=17ms TTL=126 Ping statistics for 204.79.197.200: Packets: Sent = 4, Received = 4, Lost = 0 <0% loss>, Approximate round trip times in milli-seconds: Minimum = 9ms, Maximum = 17ms, Average = 13ms C:\Windows\system32>, How it works The gateway server understands the NVGRE protocol and is able to act as NAT router. By not constraining the TenantNetworks virtual network adapter to a specific VM Network, it is possible for the server to cope with 50 VM Networks (by default)-each with multiple subnets if requ