31 ExternalPort InternalIPAddress 10.0.0.14 InternalPort InternalRout ingDomainId {00000000-0000-0000-0000-000000000000 Active [HNUGateway1]: PS C:\Users\adminuser\Documents> As you can see, the External IP Address has been set to 192.168.200.31, the External Port has been set to 80, the Internal IP Address has been set to 10.0.0.14, and the Internal Port has been set to 80. Chapter 5 33. Type in the following cmdlet: Get-NetNatSession 34. You will then see the current sessions using this NAT rule: [HNUGateway1]: PS C:\Users\adminuser\Documents> Get-NetNatSession NatName a18eeff9-bd7f-46bd-b313-d825983d2df9 InternalRoutingDomainId {a18eeff9-bd7f-46bd-b313-d825983d2df91 CreationTime 04/09/2014 20:28:48 Protocol InternalSourceAddress 10.0.0.14 InternalSourcePort InternalDestinationAddress 192.168.200.1 InternalDestinationPort 52198 ExternalSourceAddress 192.168.200.31 ExternalSourcePort ExternalDestinationAddress 192.168.200.1 ExternalDestinationPort 52198 The External IP address can be seen to be 192.168.200.1, which is where the website was visited from. How it works Network Address Translation (NAT) within Hyper-V Network Virtualization (HNV) is very similar to traditional NAT. When the Windows Server Gateway is connected to VMM, it is provisioned in multitenant mode. In addition to knowing the destination IP address and port number for the inbound traffic, the Windows Server Gateway combined with the Hyper-V host wraps the traffic in the NVGRE protocol. This allows the traffic to be routed on the physical network using the Provider Address network to ensure the traffic arrives on the Hyper-V host where the destination machine is residing. Direct Routing and how it is different from NAT Direct Routing does not mask the VM Network to external networks unlike NAT, which can expose port numbers and then direct that traffic to the correct VM and (optionally) a different port. Direct Routing works more like a traditional router and as such a Windows Server Gateway that is configured in Direct Routing mode can only su