From 954b8a444793f8c9eee92871355dad6360e62ef4 Mon Sep 17 00:00:00 2001 From: MikeBlodge Date: Fri, 26 Oct 2018 09:40:44 -0700 Subject: [PATCH] metadata --- .../advanced-troubleshooting-802-authentication.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/client-management/advanced-troubleshooting-802-authentication.md b/windows/client-management/advanced-troubleshooting-802-authentication.md index 298dc476db..d21a06f26b 100644 --- a/windows/client-management/advanced-troubleshooting-802-authentication.md +++ b/windows/client-management/advanced-troubleshooting-802-authentication.md @@ -74,10 +74,10 @@ If you collect network packet capture on both a client and a NPS side, you can s > info not critical to a task If you also enable wireless scenario trace with network packet capture, you can see more detailed information on Network Monitor with **ONEX\_MicrosoftWindowsOneX** and **WLAN\_MicrosoftWindowsWLANAutoConfig** Network Monitor filtering applied. -![client-side packet capture data](clientsidepacket_cap_data.png) +![client-side packet capture data](images/clientsidepacket_cap_data.png) _Client-side packet capture data_ -![NPS-side packet capture data](NPS_sidepacket_capture_data.png) +![NPS-side packet capture data](images/NPS_sidepacket_capture_data.png) _NPS-side packet capture data_ ‎ ## Additional references