ve the following reply: C:\WINDOWS\system32> Get-NetRoute -DestinationPref ix 192.168.200.0/24 if Index DestinationPref ix NextHop 192.168.200.0/24 0.0.0.0 Then, you will be able to continue with this recipe. Chapter 5 62. Make a note of the ifIndex value that has been returned, as this is the Interface Index the machine uses to route traffic outside of its local subnet. Run the following PowerShell cmdlet: New-NetRoute -DestinationPrefix 10.0.0.3/32 - InterfaceIndex 31 -AddressFamily IPv4 -NextHop 192.168.200.32 In this, 10.0.0.3 is the IP address of the VM you have installed IIS on, 192.168.200.32 is the IP address of the External (NAT) interface on HNVGateway2 ad. demo. com, and the InterfaceIndex value is the ifIndex value returned in step 61. 63. Return to Internet Explorer and press F5 to refresh the page. You will get the following screenshot: http://10.0.0.3/hnv.htm HNV Testing for Direct Rou... x Software Defined Networking Rocks! Direct Routing is easy! This is some more test text for the Hyper-V Network Virtualization Cookbook! 64. In the PowerShell console you have open, enter the following command: Tracert 10.0.0.3 65. You should receive the following information. If you do not receive this information, then check that the VM either has its firewall disabled or the File and Printer Sharing (Echo Request - ICMPv4-In) rule is enabled: PS C:\WINDOWS\system32> tracert 10.0.0.3 Tracing route to TENBUM10 [10.0.0.3] over a maximum of 30 hops <1 MS <1 MS <1 MS HNUGATEWAY2 [192.168.200.321 TENBUM10 [10.0.0.3] TENBUM10 [10.0.0.3] 66. You will see that none of the routing information returned contains the Provider IP addresses for HNVGateway2 or the VM. Windows Server Gateway Configuration How it works Direct Routing within HNV is very similar to traditional routing. When the Windows Server Gateway is connected to VMM, it is provisioned in routing mode. The Windows Server Gateway combined with the Hyper-V host wraps the inbound traffic in the NVGRE protocol. This allows the traffic to be routed on the physical 