 for Virtual Machines (4) pvlan Logical Netw. PVLAN190-1 PVLAN190-2 PVLAN190-3 PVLAN190-4 34. By clicking on the + symbol you will see all of the network adapters attached to the VM and the IP address(es) that have been assigned. Logical Netw... IP Pool IP Address PVLAN190-1 PVLAN190-1 PVLAN Testing IPP-PVLAN_Testing_0-1... 192.168.190.2 35. Make a note of all four IP addresses. You may have a list similar to the following: PVLAN190-1: 192.168.190.2 PVLAN190-2: 192.168.190.3 PVLAN190-3: 192.168.190.6 PVLAN190-4: 192.168.190.5 36. Ensure that each VM's firewall is either disabled or that the Windows Firewall rule File and Printer Sharing (Echo Request - ICMPv4-In) is enabled on each PVLAN virtual machine. Promiscuous and Isolated Perform the following steps for Promiscuous 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 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. Implementing Network Isolation in Hyper-V 5. Enter the following PowerShell and press Enter: Test-NetConnection 192.168.190.3 Here, 192.168.190.3 is the IP address for PVLAN190-2. This should fail and you should receive the following message in the PowerShell console: 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.2 PingSucceeded : False PingReplyDetails (RTT) If you do not receive this message, then please ensure that your PVLANs are configured correctly and that all of your PVLAN VMs are in isolated mode. Repeat the process from PVLAN190-2 to PVLAN190-1 (steps 38-43). You should receive similar results. WARNING: Ping to 192.168.190.2 failed -- Status: DestinationHostUnreachable ComputerName : 192.168.190.2 RemoteAddress : 192.1