Skip to content

Commit 8ec0dd6

Browse files
committed
tweak
1 parent c9607c2 commit 8ec0dd6

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ Connection troubleshoot can detect the following types of issues that can impact
6464

6565
## Response
6666

67-
The following table shows the properties returned when connection troubleshoot has finished running.
67+
The following table shows the properties returned after running connection troubleshoot.
6868

6969
|**Property** |**Description** |
7070
|---------|---------|
@@ -113,12 +113,12 @@ Connection troubleshoot returns fault types about the connection. The following
113113
|---------|---------|
114114
|CPU | High CPU utilization. |
115115
|Memory | High Memory utilization. |
116-
|GuestFirewall | Traffic is blocked due to a virtual machine firewall configuration. <br><br> Note that a TCP ping is a unique use case in which, if there's no allowed rule, the firewall itself responds to the client's TCP ping request even though the TCP ping doesn't reach the target IP address/FQDN. This event isn't logged. If there's a network rule that allows access to the target IP address/FQDN, the ping request reaches the target server and its response is relayed back to the client. This event is logged in the Network rules log. |
116+
|GuestFirewall | Traffic is blocked due to a virtual machine firewall configuration. <br><br> A TCP ping is a unique use case in which, if there's no allowed rule, the firewall itself responds to the client's TCP ping request even though the TCP ping doesn't reach the target IP address/FQDN. This event isn't logged. If there's a network rule that allows access to the target IP address/FQDN, the ping request reaches the target server and its response is relayed back to the client. This event is logged in the Network rules log. |
117117
|DNSResolution | DNS resolution failed for the destination address. |
118-
|NetworkSecurityRule | Traffic is blocked by an NSG Rule (Rule is returned) |
118+
|NetworkSecurityRule | Traffic is blocked by a network security group rule (security rule is returned) |
119119
|UserDefinedRoute|Traffic is dropped due to a user defined or system route. |
120120

121121
### Next steps
122122

123-
- Learn more about [Network Watcher](network-watcher-monitoring-overview.md).
124-
- Learn how to use connection troubleshoot using the [Azure portal](network-watcher-connectivity-portal.md), [PowerShell](network-watcher-connectivity-powershell.md), the [Azure CLI](network-watcher-connectivity-cli.md), or [REST API](network-watcher-connectivity-rest.md).
123+
- To learn how to use connection troubleshoot to test and troubleshoot connections, see [Troubleshoot connections with Azure Network Watcher using the Azure portal](network-watcher-connectivity-portal.md).
124+
- To learn more about Network Watcher and its other capabilities, see [What is Azure Network Watcher?](network-watcher-monitoring-overview.md).

0 commit comments

Comments
 (0)