th the following parameters: Name: www Test Protocol: TCP Incoming Port: 80 Destination IP: 10.0.0.14 (please use the IP address obtained in step 14) Destination Port: 80 Tenant A Properties Network address translation (NAT) In NAT all traffic to external network is routed through single IP, select the IP address pool and IP below. If you want VM Subnets VMM to automatically pick any available IP from the selected address pool, leave the IP address column empty. Connectivity IP address pool: External (NAT)-IP-Pool (192.168.200.10) - 192.168.200.99) IP address: 192.168.200.31 Network Address... Specify network address translation (NAT) rules: Access Protocol Incoming Port Destination IP Destination Port www Test 10.0.0.14 Remove 24. Click on OK. 25. This has now created a new NAT rule for this VM Network only. Windows Server Gateway Configuration 26. On a machine that has access to the External (NAT) address, in this case 192.168.200.31, open Internet Explorer. 27. Navigate to http://192.168.200.31/hnv.htm.You should see the text you entered in step 7. http://192.168.200.31/hnv.htm HNV Testing Software Defined Networking Rocks! This is some test text for the Hyper-V Network Virtualization Cookbook! 28. To see what VMM has done to make this work, open a PowerShell console on the VMM server. 29. Type in the following cmdlet: Enter-PSSession HNVGateway1 30. Provided the account you are using has permissions to log on to the HNVGateway1 server, you will see the PS Console change to have a prefix of [HNVGateway1]. 31. Type in the following cmdlet: Get-NetNatStaticMapping 32. You will then see the configuration that VMM has applied to the Windows Server Gateway: Windows PowerShell Windows PowerShell Copyright (C) 2013 Microsoft Corporation. All rights reserved. PS C:\Users\adminuser> Enter-PSSession HNVGateway1 [HNUGateway1]: PS C:\Users\adminuser\Documents> Get-NetHatStaticMapping StaticMappingID NatName a18eeff9-bd7f-46bd-b313-d825983d2df9 Protocol RemoteExternalIPAddressPrefix 0.0.0.0/0 ExternalIPAddress 192.168.200.