68.190.2 InterfaceAlias : Ethernet 2 SourceAddress : 192.168.190.3 PingSucceeded : False PingReplyDetails (RTT) : This result shows how two VM network adapters that are in Isolated mode cannot communicate despite being on the same Primary and Secondary VLAN. 10. Using the PowerShell console that was left open on the VMM server in step 28, enter the following cmdlet (if this was closed please repeat steps 21-23): Set-VMNetworkAdapterVlan -VMName PVLAN190-1 Promiscuous - PrimaryVlanId 190 -SecondaryVlanIdList 5 11. Then, run the following PowerShell cmdlet: Get-VMNetworkAdapterVlan -VMName PVLAN190-1 12. You will see that the mode has changed from Isolated to Promiscuous. Chapter 6 13. Repeat steps 40-43 and you will see that the VMs can now communicate: PS C:\Users\Administrator> Test-NetConnection 192.168.190.2 ComputerName : 192.168.190. 2 RemoteAddress 192.168. 190. 2 InterfaceAlias Ethernet 2 SourceAddress 192.168.190. 3 PingSucceeded PingReplyDetails (RTT) 14. This shows how a VM network adapter that is in Isolated mode and one that is in Promiscuous mode can communicate on the same Primary and Secondary VLAN. 15. The PVLAN virtual machines should currently be in the following configuration: Virtual Machine PVLAN Mode PVLAN190-1 Promiscuous PVLAN190-2 Isolated PVLAN190-3 Isolated PVLAN190-4 Isolated The following diagram shows this configuration: Isolated Promiscuous Community PVLAN190-2 PVLAN190-3 PVLAN190-1 PVLAN190-4 Implementing Network Isolation in Hyper-V Promiscuous and Community Perform the following steps for Promiscuous and Community 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 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.6 6. Thi