From 1bd397bfc60edc955ae9ef383e3b932a16ddbff4 Mon Sep 17 00:00:00 2001 From: MikeBlodge Date: Fri, 26 Oct 2018 12:11:20 -0700 Subject: [PATCH] updating articles --- .../advanced-troubleshooting-wireless-network-connectivity.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/advanced-troubleshooting-wireless-network-connectivity.md b/windows/client-management/advanced-troubleshooting-wireless-network-connectivity.md index 4a2d5d6fc4..966e294bb0 100644 --- a/windows/client-management/advanced-troubleshooting-wireless-network-connectivity.md +++ b/windows/client-management/advanced-troubleshooting-wireless-network-connectivity.md @@ -98,7 +98,7 @@ Reset --> Ihv_Configuring --> Configuring --> Associating --> Authenticating --> Connected --> Roaming --> Wait_For_Disconnected --> Disconnected --> Reset -- Filtering the ETW trace with the provided [TextAnalyisTool (TAT)](Link) filter is an easy first step to determine where a failed connection setup is breaking down: +- Filtering the ETW trace with the provided [TextAnalyisTool (TAT)](https://github.com/TextAnalysisTool/Releases) filter is an easy first step to determine where a failed connection setup is breaking down: Use the **FSM transition** trace filter to see the connection state machine. Example of a good connection setup: