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/network-watcher/network-watcher-connectivity-overview.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,7 +64,7 @@ Connection troubleshoot can detect the following types of issues that can impact
64
64
65
65
## Response
66
66
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.
68
68
69
69
|**Property**|**Description**|
70
70
|---------|---------|
@@ -113,12 +113,12 @@ Connection troubleshoot returns fault types about the connection. The following
113
113
|---------|---------|
114
114
|CPU | High CPU utilization. |
115
115
|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. |
117
117
|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) |
119
119
|UserDefinedRoute|Traffic is dropped due to a user defined or system route. |
120
120
121
121
### Next steps
122
122
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