Skip to content

Commit 9919b18

Browse files
committed
freshness and acrolinx
1 parent a849229 commit 9919b18

File tree

1 file changed

+11
-12
lines changed

1 file changed

+11
-12
lines changed

articles/virtual-network/troubleshoot-vm-connectivity.md

Lines changed: 11 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,10 @@ description: Learn how to diagnose and resolve connectivity problems that affect
44
author: asudbring
55
ms.author: allensu
66
manager: dcscontentpm
7-
audience: ITPro
87
ms.topic: troubleshooting
98
ms.service: azure-virtual-network
109
ms.localizationpriority: medium
11-
ms.date: 08/29/2019
10+
ms.date: 04/17/2025
1211
---
1312

1413
# Troubleshoot Azure VM connectivity problems
@@ -31,7 +30,7 @@ To resolve these problems, follow the steps in the following section.
3130
>
3231
## Resolution
3332

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
3534

3635
#### Step 1: Verify that VMs can communicate with each other.
3736

@@ -51,10 +50,10 @@ To resolve these problems, follow the steps in the following section.
5150
5251
#### Step 2: Check the Network security group settings.
5352
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.
5554
5655
> [!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.
5857
5958
After that, try to ping the destination from the source VM again:
6059
@@ -136,20 +135,20 @@ Hops : [
136135
|Issue type |Value |Resolution action |
137136
|---------|---------|---------|
138137
|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).|
140139
|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).|
141140
|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).|
143142
|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). |
144143
|Socket Error | Not applicable | The specified port is already in use by another application. Try to use a different port. |
145144

146145
3. Run the connectivity check again to determine whether the problem is resolved.
147146

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
149148

150149
#### Step 1: Make sure that the second network adapter is enabled to talk outside the subnet.
151150

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.
153152

154153
![IP configures](media/troubleshoot-vm-connectivity/ipconfig.png)
155154

@@ -168,15 +167,15 @@ If users want to enable secondary network adapters to talk outside their own sub
168167
Route add 0.0.0.0 mask 0.0.0.0 -p 192.168.0.1
169168
```
170169
171-
3. Run route print. If the entry is added successfully, you will see an entry that resembles the following:
170+
3. Run route print. If the entry is added successfully, you'll see an entry that resembles the following:
172171
173172
![IP route](media/troubleshoot-vm-connectivity/iproute.png)
174173
175174
Now, try to connect to secondary network adapter. If the connection is still unsuccessful, go to next step.
176175
177176
#### Step 2: Check NSG settings for the network adapters.
178177
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.
180179
181180
![Screenshot shows the Networking settings for a virtual machine where you can see Allow V net Inbound and Allow V net OutBound.](media/troubleshoot-vm-connectivity/nsg.png)
182181
@@ -229,7 +228,7 @@ Hops : [
229228
230229
#### 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.
231230
232-
### Azure VM cannot connect to the internet
231+
### Azure VM can't connect to the internet
233232
234233
#### Step 1: Check whether the network adapter is in a failed state.
235234

0 commit comments

Comments
 (0)