You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-network/troubleshoot-vm-connectivity.md
+11-12Lines changed: 11 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,11 +4,10 @@ description: Learn how to diagnose and resolve connectivity problems that affect
4
4
author: asudbring
5
5
ms.author: allensu
6
6
manager: dcscontentpm
7
-
audience: ITPro
8
7
ms.topic: troubleshooting
9
8
ms.service: azure-virtual-network
10
9
ms.localizationpriority: medium
11
-
ms.date: 08/29/2019
10
+
ms.date: 04/17/2025
12
11
---
13
12
14
13
# Troubleshoot Azure VM connectivity problems
@@ -31,7 +30,7 @@ To resolve these problems, follow the steps in the following section.
31
30
>
32
31
## Resolution
33
32
34
-
### Azure VM cannot connect to another Azure VM in same virtual network
33
+
### Azure VM can't connect to another Azure VM in same virtual network
35
34
36
35
#### Step 1: Verify that VMs can communicate with each other.
37
36
@@ -51,10 +50,10 @@ To resolve these problems, follow the steps in the following section.
51
50
52
51
#### Step 2: Check the Network security group settings.
53
52
54
-
For each VM, check for default Inbound port rules ("Allow VNet Inbound" and "Allow Load Balancer Inbound"). Make sure to also check that there are no matching blocking rules that are listed below a lower-priority rule.
53
+
For each VM, check for default Inbound port rules of *Allow VNet Inbound* and *Allow Load Balancer Inbound*. Make sure to also check that there are no matching blocking rules that are listed below a lower-priority rule.
55
54
56
55
> [!NOTE]
57
-
> Rules that have a lower number will be matched first. For example, if you have a rule that has priority 1000 and 6500, the rule that has priority 1000 will be matched first.
56
+
> Rules that have a lower number are matched first. For example, if you have a rule that has priority 1000 and 6500, the rule that has priority 1000 is matched first.
58
57
59
58
After that, try to ping the destination from the source VM again:
60
59
@@ -136,20 +135,20 @@ Hops : [
136
135
|Issue type |Value |Resolution action |
137
136
|---------|---------|---------|
138
137
|NetworkSecurityRule|Name of the blocking NSG|You can [delete the NSG rule](./manage-network-security-group.md#delete-a-security-rule) or modify the rule as described [here](./manage-network-security-group.md#change-a-security-rule).|
139
-
|UserDefinedRoute | Name of the blocking UDR | If you do not require this route, delete the UDR. If you can’t delete the route, update the route by using the appropriate address prefix and next hop. You can also adjust the Network Virtual Appliance to forward traffic appropriately. For more information, see: [Virtual network traffic routing](./virtual-networks-udr-overview.md) and [Route network traffic with a route table using PowerShell](./tutorial-create-route-table-powershell.md).|
138
+
|UserDefinedRoute | Name of the blocking UDR | If you don't require this route, delete the UDR. If you can’t delete the route, update the route by using the appropriate address prefix and next hop. You can also adjust the Network Virtual Appliance to forward traffic appropriately. For more information, see: [Virtual network traffic routing](./virtual-networks-udr-overview.md) and [Route network traffic with a route table using PowerShell](./tutorial-create-route-table-powershell.md).|
140
139
|CPU | Usage | Follow these recommendations that describe in [Generic performance troubleshooting for Azure Virtual Machine running Linux or Windows](https://support.microsoft.com/en-in/help/3150851/generic-performance-troubleshooting-for-azure-virtual-machine-running).|
141
140
|Memory | Usage | Follow the recommendations that are described in [Generic performance troubleshooting for Azure Virtual Machine running Linux or Windows](https://support.microsoft.com/en-in/help/3150851/generic-performance-troubleshooting-for-azure-virtual-machine-running).|
142
-
|Guest Firewall | Name of the firewall blocking | Follow these steps: [Turn Windows Defender Firewall on or off](https://support.microsoft.com/help/4028544/windows-turn-windows-firewall-on-or-off).|
141
+
|Guest Firewall | Name of the firewall blocking | Follow these steps: [Turn Windows Firewall on or off](https://support.microsoft.com/help/4028544/windows-turn-windows-firewall-on-or-off).|
143
142
|DNS Resolution | Name of the DNS | Follow these steps: [Azure DNS troubleshooting guide](../dns/dns-troubleshoot.md) and [Name resolution for resources in Azure virtual networks](./virtual-networks-name-resolution-for-vms-and-role-instances.md). |
144
143
|Socket Error | Not applicable | The specified port is already in use by another application. Try to use a different port. |
145
144
146
145
3. Run the connectivity check again to determine whether the problem is resolved.
147
146
148
-
### Azure VM cannot connect to the second network adapter of an Azure VM in same virtual network
147
+
### Azure VM can't connect to the second network adapter of an Azure VM in same virtual network
149
148
150
149
#### Step 1: Make sure that the second network adapter is enabled to talk outside the subnet.
151
150
152
-
By default, secondary network adapters (also known as network interface cards, or network adapters) are not configured to have a default gateway. Therefore, the traffic flow on the secondary adapter will be limited to the same subnet.
151
+
By default, secondary network adapters (also known as network interface cards, or network adapters) aren't configured to have a default gateway. Therefore, the traffic flow on the secondary adapter will be limited to the same subnet.
Now, try to connect to secondary network adapter. If the connection is still unsuccessful, go to next step.
176
175
177
176
#### Step 2: Check NSG settings for the network adapters.
178
177
179
-
For both the primary and secondary network adapters, check the default Inbound port rules (Allow VNet Inbound, Allow Load Balancer) to inbound on both network adapters. You should also make sure that there are no matching blocking rules that have a lower-priority rule above them.
178
+
For both the primary and secondary network adapters, check the default Inbound port rules of **Allow VNet Inbound** and **Allow Load Balancer** allow inbound on both network adapters. You should also make sure that there are no matching blocking rules that have a lower-priority rule above them.
180
179
181
180

182
181
@@ -229,7 +228,7 @@ Hops : [
229
228
230
229
#### Step 4: Refer the table under [Step 5](#step-5-fix-the-issue-in-the-connectivity-check-result), and follow these steps to resolve the issues.
231
230
232
-
### Azure VM cannot connect to the internet
231
+
### Azure VM can't connect to the internet
233
232
234
233
#### Step 1: Check whether the network adapter is in a failed state.
0 commit comments