s should succeed and you should receive this message in the PowerShell console: PS C:\Users\Administrator> Test-NetConnection 192.168.190.6 ComputerName : 192.168.190.6 RemoteAddress : 192.168.190.0 6 InterfaceAlias : Ethernet 2 SurceAddress : 192.168.190. 2 PingSucceeded : True PingReplyDetails (RTT) In the VMM Console right-click on PVLAN190-3, 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.3 11. This should fail and you should receive the following message in the PowerShell console: PS C:\Users\Administrator> Test-NetConnection 192.168.190. 3 WARNING: Ping to 192.168.190.3 failed -- Status: DestinationHostUnreachable ComputerName : 192.168.190. 3 RemoteAddress : 192.168.190. 3 InterfaceAlias : Ethernet 2 SourceAddress : 192.168.190. 6 PingSucceeded : False PingReplyDetails (RTT) Chapter 6 12. So the Isolated VMs cannot communicate with each other, but they can communicate with the VMs set to Promiscuous. 13. On the VMM server, open a PowerShell console. Note that this does not need to be an elevated PowerShell console. 14. Once you have opened PowerShell, type in Enter-PSSession HYPVCH1 and press Enter (where HYPVCH1 is the name of the Hyper-V host where PVLAN190-1 is running). 15. As in the previous recipe, you will see the PowerShell session change. Windows PowerShell Windows PowerShe II Copyright (C) 2013 Microsoft Corporation. All rights reserved. PS C:\Users\adminuser> Enter-PSSession HYPVCH1 [HYPVCH1] : PS C: :\Users\AdminUser\Documents) 16. Using this PowerShell console enter the following cmdlet (if this was closed please repeat steps 21-23): Set-VMNetworkAdapterVlan, -VMName PVLAN190-3 Community - PrimaryVlanId 190 -SecondaryVlanId 5 17. Then, run the following PowerShell cmdlet: Get-VMNetworkAdapterVlan -VMName PVLAN190-3 18. You will see that the mode has changed from Isolated to Community. If you repeat steps 53-62, y