Skip to content

Commit e3eb248

Browse files
committed
update prerequisites and screenshots
1 parent 4117013 commit e3eb248

File tree

4 files changed

+9
-11
lines changed

4 files changed

+9
-11
lines changed
3.83 KB
Loading
4.2 KB
Loading
7.23 KB
Loading

articles/network-watcher/network-watcher-connectivity-portal.md

Lines changed: 9 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -2,24 +2,22 @@
22
title: Troubleshoot connections - Azure portal
33
titleSuffix: Azure Network Watcher
44
description: Learn how to use the connection troubleshoot capability of Azure Network Watcher using the Azure portal.
5-
services: network-watcher
65
author: halkazwini
6+
ms.author: halkazwini
77
ms.service: network-watcher
88
ms.topic: how-to
9-
ms.workload: infrastructure-services
10-
ms.date: 07/17/2023
11-
ms.author: halkazwini
12-
ms.custom: template-how-to, engagement-fy23
9+
ms.date: 09/13/2023
10+
#CustomerIntent: As an Azure administrator, I want to learn how to use Connection Troubleshoot to diagnose connectivity problems in Azure.
1311
---
1412

1513
# Troubleshoot connections with Azure Network Watcher using the Azure portal
1614

17-
In this article, you learn how to use [Azure Network Watcher connection troubleshoot](network-watcher-connectivity-overview.md) to diagnose and troubleshoot connectivity issues.
15+
In this article, you learn how to use Azure Network Watcher connection troubleshoot to diagnose and troubleshoot connectivity issues. For more information about connection troubleshoot, see [Connection troubleshoot overview](network-watcher-connectivity-overview.md).
1816

1917
## Prerequisites
2018

2119
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
22-
- A virtual machine with inbound TCP connectivity from 168.63.129.16 over the port being tested.
20+
- A virtual machine with inbound TCP connectivity from 168.63.129.16 over the port being tested (for Port scanner diagnostic test).
2321

2422
> [!IMPORTANT]
2523
> Connection troubleshoot requires that the virtual machine you troubleshoot from has the `AzureNetworkWatcherExtension` extension installed. The extension is not required on the destination virtual machine.
@@ -50,13 +48,13 @@ In this section, you test connectivity between two connected virtual machines.
5048
| **Probe Settings** | |
5149
| Preferred IP version | Select **IPv4**. |
5250
| Protocol | Select **TCP**. |
53-
| Destination port | Enter *80*. |
51+
| Destination port | Enter **80**. |
5452
| **Connection Diagnostics** | |
5553
| Diagnostics tests | Select **Select all**. |
5654

5755
:::image type="content" source="./media/network-watcher-connectivity-portal/test-virtual-machines-connected.png" alt-text="Screenshot of Network Watcher connection troubleshoot in Azure portal to test the connection between two connected virtual machines.":::
5856

59-
1. Select **Test connection**.
57+
1. Select **Run diagnostic tests**.
6058

6159
The test results show that the two virtual machines are communicating with no issues:
6260

@@ -97,7 +95,7 @@ In this section, you test connectivity between two virtual machines that have co
9795

9896
:::image type="content" source="./media/network-watcher-connectivity-portal/test-two-virtual-machines.png" alt-text="Screenshot of Network Watcher connection troubleshoot in Azure portal to test the connection between two virtual machines.":::
9997

100-
1. Select **Test connection**.
98+
1. Select **Run diagnostic tests**.
10199

102100
The test results show that the two virtual machines aren't communicating:
103101

@@ -137,7 +135,7 @@ In this section, you test connectivity between a virtual machines and `www.bing.
137135

138136
:::image type="content" source="./media/network-watcher-connectivity-portal/test-bing.png" alt-text="Screenshot of Network Watcher connection troubleshoot in Azure portal to test the connection between a virtual machines and Microsoft Bing search engine.":::
139137

140-
1. Select **Test connection**.
138+
1. Select **Run diagnostic tests**.
141139

142140
The test results show that `www.bing.com` is reachable from **VM1** virtual machine:
143141

0 commit comments

Comments
 (0)