ou will receive the same results, as there are now three VMs in use, one of each type. 19. The PVLAN virtual machines should currently be in the following configuration: Virtual Machine PVLAN Mode PVLAN190-1 Promiscuous PVLAN190-2 Isolated PVLAN190-3 Community PVLAN190-4 Isolated Implementing Network Isolation in Hyper-V The following diagram shows this configuration: Isolated Promiscuous Community PVLAN190-2 PVLAN190-1 PVLAN190-3 PVLAN190-4 Promiscuous, Community, and Isolated Perform the following steps for Promiscuous, Community, and Isolated modes: 1. In the VMM console, navigate to VMs and Services I All Hosts and enter PVLAN in the filter. For this part of the recipe you will need the following VMs running: PVLAN190-1 PVLAN190-2 PVLAN190-3 PVLAN190-4 2. Right-click on PVLAN190-1, navigate to Connect or View, and click on Connect via Console. 3. Log on to the VM using the default password. 4. Open an elevated PowerShell console. 5. Enter the following PowerShell and press Enter: Test-NetConnection 192.168.190.5 Chapter 6 6. This should succeed and you should receive the following message in the PowerShell console: PS C:\Users\Administrator> Test-NetConnection 192.168.190.5 ComputerName : 192.168.190.5 RemoteAddress 192.168.190.5 InterfaceAlias Ethernet 2 SourceAddress 192.168.190.7 PingSucceeded : True PingReplyDetails (RTT) : 7. In the VMM Console right-click on PVLAN190-4, navigate to Connect or View, and click on Connect via Console. Log on to the VM using the default password. 9. Open an elevated PowerShell console. 10. Enter the following PowerShell and press Enter: Test-NetConnection 192.168.190.6 11. This should fail and you should receive the following message in the PowerShell console: PS C:\Users\Aaministrator> Test-NetConnection 192.168.190. 6 WARNING: Ping to 192.168.190.6 failed -- Status: DestinationHostUnreachable ComputerName : 192.168.190.6 RemoteAddress 192.168.190.6 InterfaceAlias Ethernet 2 SourceAddress 192.168.190.5 PingSucceeded : False PingReplyDetails (RTT) 12. On the VMM server open