mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-23 06:13:41 +00:00
Merged PR 13777: Multiple changes to several troubleshooting topics + reorg of TOC in this area
Multiple examples added, text edited, and conceptual articles linked
This commit is contained in:
Greg Lindsay
@ -1,78 +1,72 @@
|
||||
---
|
||||
title: Data Collection for Troubleshooting 802.1x Authentication
|
||||
description: Data needed for reviewing 802.1x Authentication issues
|
||||
keywords: troubleshooting, data collection, data, 802.1x authentication, authentication, data
|
||||
title: Data collection for troubleshooting 802.1X authentication
|
||||
description: Data needed for reviewing 802.1X Authentication issues
|
||||
keywords: troubleshooting, data collection, data, 802.1X authentication, authentication, data
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl:
|
||||
ms.sitesec: library
|
||||
author: kaushika-msft
|
||||
ms.localizationpriority: medium
|
||||
ms.author: mikeblodge
|
||||
ms.date: 10/29/2018
|
||||
---
|
||||
|
||||
# Data Collection for Troubleshooting 802.1x Authentication
|
||||
|
||||
# Data collection for troubleshooting 802.1X authentication
|
||||
|
||||
Use the following steps to collect data that can be used to troubleshoot 802.1X authentication issues. When you have collected data, see [Advanced troubleshooting 802.1X authentication](advanced-troubleshooting-802-authentication.md).
|
||||
|
||||
## Capture wireless/wired functionality logs
|
||||
|
||||
Use the following steps to collect wireless and wired logs on Windows and Windows Server:
|
||||
|
||||
1. Create C:\MSLOG on the client machine to store captured logs.
|
||||
2. Launch a command prompt as an administrator on the client machine, and run the following commands to start RAS trace log and Wireless/Wired scenario log.
|
||||
2. Launch an elevated command prompt on the client machine, and run the following commands to start a RAS trace log and a Wireless/Wired scenario log.
|
||||
|
||||
**Wireless Windows 8.1 and Windows 10:**
|
||||
|
||||
```
|
||||
netsh ras set tracing * enabled
|
||||
netsh trace start scenario=wlan,wlan_wpp,wlan_dbg,wireless_dbg globallevel=0xff capture=yes maxsize=1024 tracefile=C:\MSLOG\%COMPUTERNAME%_wireless_cli.etl
|
||||
```
|
||||
|
||||
**Wireless Windows 7 and Windows 8:**
|
||||
|
||||
<br>**Wireless Windows 7 and Windows 8:**
|
||||
```
|
||||
netsh ras set tracing * enabled
|
||||
netsh trace start scenario=wlan,wlan_wpp,wlan_dbg globallevel=0xff capture=yes maxsize=1024 tracefile=C:\MSLOG\%COMPUTERNAME%_wireless_cli.etl
|
||||
```
|
||||
|
||||
**Wired client, regardless of version**
|
||||
|
||||
<br>**Wired client, regardless of version**
|
||||
```
|
||||
netsh ras set tracing * enabled
|
||||
netsh trace start scenario=lan globallevel=0xff capture=yes maxsize=1024 tracefile=C:\MSLOG\%COMPUTERNAME%_wired_cli.etl
|
||||
```
|
||||
|
||||
3. Run the following command to enable CAPI2 logging:
|
||||
|
||||
```
|
||||
wevtutil.exe sl Microsoft-Windows-CAPI2/Operational /e:true
|
||||
```
|
||||
|
||||
4. Create C:\MSLOG on the NPS to store captured logs.
|
||||
|
||||
5. Launch a command prompt as an administrator on the NPS and run the following commands to start RAS trace log and Wireless/Wired scenario log:
|
||||
5. Launch an elevated command prompt on the NPS server and run the following commands to start a RAS trace log and a Wireless/Wired scenario log:
|
||||
|
||||
**Windows Server 2012 R2, Windows Server 2016 wireless network:**
|
||||
|
||||
```
|
||||
netsh ras set tracing * enabled
|
||||
netsh trace start scenario=wlan,wlan_wpp,wlan_dbg,wireless_dbg globallevel=0xff capture=yes maxsize=1024 tracefile=C:\MSLOG\%COMPUTERNAME%_wireless_nps.etl
|
||||
```
|
||||
|
||||
**Windows Server 2008 R2, Windows Server 2012 wireless network**
|
||||
|
||||
|
||||
<br>**Windows Server 2008 R2, Windows Server 2012 wireless network**
|
||||
```
|
||||
netsh ras set tracing * enabled
|
||||
netsh trace start scenario=wlan,wlan_wpp,wlan_dbg globallevel=0xff capture=yes maxsize=1024 tracefile=C:\MSLOG\%COMPUTERNAME%_wireless_nps.etl
|
||||
```
|
||||
|
||||
**Wired network**
|
||||
|
||||
<br>**Wired network**
|
||||
```
|
||||
netsh ras set tracing * enabled
|
||||
netsh trace start scenario=lan globallevel=0xff capture=yes maxsize=1024 tracefile=C:\MSLOG\%COMPUTERNAME%_wired_nps.etl
|
||||
```
|
||||
|
||||
6. Run the following command to enable CAPI2 logging:
|
||||
|
||||
```
|
||||
wevtutil.exe sl Microsoft-Windows-CAPI2/Operational /e:true
|
||||
```
|
||||
@ -82,16 +76,16 @@ Use the following steps to collect wireless and wired logs on Windows and Window
|
||||
> When the mouse button is clicked, the cursor will blink in red while capturing a screen image.
|
||||
|
||||
```
|
||||
psr /start /output c:\MSLOG\%computername%_psr.zip /maxsc 100
|
||||
psr /start /output c:\MSLOG\%computername%_psr.zip /maxsc 100
|
||||
```
|
||||
8. Repro the issue.
|
||||
9. Run the following command on the client PC to stop the PSR capturing:
|
||||
|
||||
```
|
||||
psr /stop
|
||||
psr /stop
|
||||
```
|
||||
|
||||
10. Run the following commands from the command prompt on the NPS.
|
||||
10. Run the following commands from the command prompt on the NPS server.
|
||||
|
||||
- To stop RAS trace log and wireless scenario log:
|
||||
|
||||
@ -134,14 +128,14 @@ Use the following steps to collect wireless and wired logs on Windows and Window
|
||||
- C:\MSLOG\%COMPUTERNAME%_wireless_nps.cab (%COMPUTERNAME%_wired_nps.cab for wired scenario)
|
||||
- All log files and folders in %Systemroot%\Tracing
|
||||
|
||||
## Save environmental and configuration information
|
||||
## Save environment and configuration information
|
||||
|
||||
### On Windows client
|
||||
|
||||
1. Create C:\MSLOG to store captured logs.
|
||||
2. Launch a command prompt as an administrator.
|
||||
3. Run the following commands.
|
||||
- Environmental information and Group Policies application status
|
||||
- Environment information and Group Policy application status
|
||||
|
||||
```
|
||||
gpresult /H C:\MSLOG\%COMPUTERNAME%_gpresult.htm
|
||||
@ -299,7 +293,7 @@ Use the following steps to collect wireless and wired logs on Windows and Window
|
||||
|
||||
4. Save the logs stored in C:\MSLOG.
|
||||
|
||||
### Certificate Authority (CA) (OPTIONAL)
|
||||
## Certification Authority (CA) (OPTIONAL)
|
||||
|
||||
1. On a CA, launch a command prompt as an administrator. Create C:\MSLOG to store captured logs.
|
||||
2. Run the following commands.
|
||||
@ -378,7 +372,7 @@ Use the following steps to collect wireless and wired logs on Windows and Window
|
||||
|
||||
```powershell
|
||||
Import-Module ActiveDirectory
|
||||
Get-ADObject -SearchBase ";CN=Public Key Services,CN=Services,CN=Configuration,DC=test,DC=local"; -Filter \* -Properties \* | fl \* > C:\MSLOG\Get-ADObject_$Env:COMPUTERNAME.txt
|
||||
Get-ADObject -SearchBase ";CN=Public Key Services,CN=Services,CN=Configuration,DC=test,DC=local"; -Filter * -Properties * | fl * > C:\MSLOG\Get-ADObject_$Env:COMPUTERNAME.txt
|
||||
```
|
||||
7. Save the following logs.
|
||||
- All files in C:\MSLOG on the CA
|
||||
|
||||
Reference in New Issue
Block a user