From bf7876addfb99fa027e02096a1fc6bfadc087a4f Mon Sep 17 00:00:00 2001 From: Kaushik Ainapure Date: Wed, 31 Oct 2018 18:01:33 +0530 Subject: [PATCH] Update the link to the missing TAT filter file Missing wifi.tat file --- .../advanced-troubleshooting-wireless-network-connectivity.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/client-management/advanced-troubleshooting-wireless-network-connectivity.md b/windows/client-management/advanced-troubleshooting-wireless-network-connectivity.md index 0896ab5eed..5647279113 100644 --- a/windows/client-management/advanced-troubleshooting-wireless-network-connectivity.md +++ b/windows/client-management/advanced-troubleshooting-wireless-network-connectivity.md @@ -5,7 +5,7 @@ keywords: troubleshooting, wireless network connectivity, wireless, Wi-Fi ms.prod: w10 ms.mktglfcycl: ms.sitesec: library -author: mikeblodge +author: kaushika-msft ms.localizationpriority: medium ms.author: mikeblodge ms.date: 10/29/2018 @@ -99,7 +99,7 @@ Reset --> Ihv_Configuring --> Configuring --> Associating --> Authenticating --> Connected --> Roaming --> Wait_For_Disconnected --> Disconnected --> Reset -- 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: +- Filtering the ETW trace with the provided [TextAnalyisTool (TAT)](Missing wifi.tat file) 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: