From b1e0f749a1d0b5ad01cb56fc0a9b3fc727417d31 Mon Sep 17 00:00:00 2001 From: staleycyn <45440075+staleycyn@users.noreply.github.com> Date: Fri, 1 Dec 2023 08:37:42 -0800 Subject: [PATCH] Update LAB_05-Implement_Intersite_Connectivity.md --- .../Lab/LAB_05-Implement_Intersite_Connectivity.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md b/New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md index 51491a5b..4dd9a275 100644 --- a/New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md +++ b/New Instructions/Lab/LAB_05-Implement_Intersite_Connectivity.md @@ -190,11 +190,8 @@ In this task, you will check whether the VMs can communicate with each other. Yo 1. Use the following command to verify that there is now a connection to CoreServicesVM on CoreServicesVnet. Ensure that you use the IP address of the VM as documented earlier in the lab. - ```powershell - Test-NetConnection 10.0.0.4 -port 3389 - ``` - - + ```Test-NetConnection 10.0.0.4 -port 3389``` + 1. The test connection should succeed, and you will see a result similar to the following: ![Powershell window with Test-NetConnection succeeded](../media/az104-lab05-success.png)