|
2 | 2 | title: Troubleshoot connections - Azure portal
|
3 | 3 | titleSuffix: Azure Network Watcher
|
4 | 4 | description: Learn how to use the connection troubleshoot capability of Azure Network Watcher using the Azure portal.
|
5 |
| -services: network-watcher |
6 | 5 | author: halkazwini
|
| 6 | +ms.author: halkazwini |
7 | 7 | ms.service: network-watcher
|
8 | 8 | 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. |
13 | 11 | ---
|
14 | 12 |
|
15 | 13 | # Troubleshoot connections with Azure Network Watcher using the Azure portal
|
16 | 14 |
|
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). |
18 | 16 |
|
19 | 17 | ## Prerequisites
|
20 | 18 |
|
21 | 19 | - 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). |
23 | 21 |
|
24 | 22 | > [!IMPORTANT]
|
25 | 23 | > 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.
|
50 | 48 | | **Probe Settings** | |
|
51 | 49 | | Preferred IP version | Select **IPv4**. |
|
52 | 50 | | Protocol | Select **TCP**. |
|
53 |
| - | Destination port | Enter *80*. | |
| 51 | + | Destination port | Enter **80**. | |
54 | 52 | | **Connection Diagnostics** | |
|
55 | 53 | | Diagnostics tests | Select **Select all**. |
|
56 | 54 |
|
57 |
| - :::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."::: |
| 55 | + :::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." lightbox="./media/network-watcher-connectivity-portal/test-virtual-machines-connected.png"::: |
58 | 56 |
|
59 |
| -1. Select **Test connection**. |
| 57 | +1. Select **Run diagnostic tests**. |
60 | 58 |
|
61 | 59 | The test results show that the two virtual machines are communicating with no issues:
|
62 | 60 |
|
@@ -95,9 +93,9 @@ In this section, you test connectivity between two virtual machines that have co
|
95 | 93 | | **Connection Diagnostics** | |
|
96 | 94 | | Diagnostics tests | Select **Select all**. |
|
97 | 95 |
|
98 |
| - :::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."::: |
| 96 | + :::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." lightbox="./media/network-watcher-connectivity-portal/test-two-virtual-machines.png"::: |
99 | 97 |
|
100 |
| -1. Select **Test connection**. |
| 98 | +1. Select **Run diagnostic tests**. |
101 | 99 |
|
102 | 100 | The test results show that the two virtual machines aren't communicating:
|
103 | 101 |
|
@@ -135,9 +133,9 @@ In this section, you test connectivity between a virtual machines and `www.bing.
|
135 | 133 | | **Connection Diagnostics** | |
|
136 | 134 | | Diagnostics tests | Select **Connectivity**. |
|
137 | 135 |
|
138 |
| - :::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."::: |
| 136 | + :::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." lightbox="./media/network-watcher-connectivity-portal/test-bing.png"::: |
139 | 137 |
|
140 |
| -1. Select **Test connection**. |
| 138 | +1. Select **Run diagnostic tests**. |
141 | 139 |
|
142 | 140 | The test results show that `www.bing.com` is reachable from **VM1** virtual machine:
|
143 | 141 |
|
|
0 commit comments