Skip to content

Commit c30bcce

Browse files
committed
additional minor corrections
1 parent 0d1a9eb commit c30bcce

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/virtual-network/tutorial-connect-virtual-networks-portal.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: virtual-network
88
ms.topic: tutorial
99
ms.tgt_pltfrm: virtual-network
1010
ms.workload: infrastructure
11-
ms.date: 06/23/2022
11+
ms.date: 06/24/2022
1212
ms.author: mbender
1313
ms.custom: template-tutorial #Required; leave this attribute/value as-is.
1414
# Customer intent: I want to connect two virtual networks so that virtual machines in one virtual network can communicate with virtual machines in the other virtual network.
@@ -178,20 +178,20 @@ Test the communication between the two virtual machines over the virtual network
178178

179179
1. You may receive a certificate warning during the sign-in process. Select **Yes** to continue with the connection.
180180

181-
1. In a later step, ping is used to communicate with **myVm1** from the **myVm2**. Ping uses the Internet Control Message Protocol (ICMP), which is denied through the Windows Firewall, by default. On the **myVm1**, enable ICMP through the Windows firewall, so that you can ping this VM from **myVm2** in a later step, using PowerShell:
181+
1. In a later step, ping is used to communicate with **myVm1** from **myVm2**. Ping uses the Internet Control Message Protocol (ICMP), which is denied through the Windows Firewall, by default. On **myVm1**, enable ICMP through the Windows firewall, so that you can ping this VM from **myVm2** in a later step, using PowerShell:
182182

183183
```powershell
184184
New-NetFirewallRule –DisplayName "Allow ICMPv4-In" –Protocol ICMPv4
185185
```
186186
187187
Though ping is used to communicate between VMs in this tutorial, allowing ICMP through the Windows Firewall for production deployments isn't recommended.
188188
189-
1. To connect to **myVm2** from **myVm1**, enter the following command from a command prompt on the **myVm1**:
189+
1. To connect to **myVm2** from **myVm1**, enter the following command from a command prompt on **myVm1**:
190190
191191
```
192192
mstsc /v:10.1.0.4
193193
```
194-
1. Enter the username and password you specified when creating the **myVm2** and select **Yes** if you receive a certificate warning during the sign-in process.
194+
1. Enter the username and password you specified when creating **myVm2** and select **Yes** if you receive a certificate warning during the sign-in process.
195195
196196
:::image type="content" source="./media/tutorial-connect-virtual-networks-portal/rdp-credentials-to-second-vm.png" alt-text="Screenshot of R D P credential screen for R D P session from first virtual machine to second virtual machine.":::
197197

0 commit comments

Comments
 (0)