6105 - deauth after EAPOL key exchange sequence

wifi无法连接公司的网络

Warning Error in Event Log - deauth after EAPOL key exchange sequence

https://forums.intel.com/s/question/0D50P0000490TN9SAM/warning-error-in-event-log-deauth-after-eapol-key-exchange-sequence?language=en_US

We understand you would like more information regarding some warning events on Device Manager related to your Intel® Dual Band Wireless-AC 8265.

We can see that you're using 802.1x with PEAP on a WPA2-Enterprise network. In most cases it's normal to see deauthentication after EAP over LAN key exchange warnings as the adapters attempts to roam or renews it's authentication. The problem comes if these are frequent or if your system is entirely unable to authenticate causing a disconnection.

In order to better assist you we would like the following information:

1. Do the errors result in loss of connectivity?
2. What is your wireless router/access point brand and model?
3. How long ago did the issue start?
4. Please share your wireless Autoconfig report
   1. Right click your start menu icon and select Command Prompt (Admin) from the list.
   2. Enter: netsh wlan show wlanreport
   3. Go to C:\ProgramData\Microsoft\Windows\WlanReport\
   4. Upload the wlan-report-latest.html file along with your reply.

Also, there is a newer driver available. Is it possible for you to update to this driver and see if the issue persists?

- https://www.intel.com/content/www/us/en/support/articles/000005559/network-and-i-o/wireless-networking.html Download the Latest Driver for Your Intel® Wireless Adapter

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-xp/bb457018(v=technet.10)

Information Gathering

The first step to take for a wireless issue is to gather information that might be needed to perform a preliminary diagnosis, including the following:

1. Windows operating system version, including the latest service pack installed and build number if applicable.

2. Wireless connection details of the Windows wireless client including the type of authentication and encryption that is being used.

3. Wireless network adapter details, including vendor, model, and driver version.

4. Wireless access point (AP) information, including vendor, model, firmware version, and configuration details similar to Step 2.

5. Wireless logs. Logging can be enabled through the netsh ras set tracing * en command. After enabling logging, you can either restart the computer or restart the Wireless Zero Configuration (for Windows XP) or Wireless Configuration (for Windows Server 2003) service with the net stop wzcsvc and net start wzcsvc commands. The wireless logs are located in the systemroot\tracing folder. The log files most useful for troubleshooting wireless issues are the following:

   • Wzctrace.log Used mostly for 802.11 association. This file is present only on computers running Windows XP Service Pack 2 (SP2) or Windows Server 2003 Service Pack 1.

   • Eapol.log Used mostly for IEEE 802.1X authentication.

   • Wzcdlg.log Used for user interface changes, such as changes made through the View Available Networks or Choose a wireless network dialog boxes.

   • Netman.log Used for user interface changes.

   • Netshell.log Used for user interface changes.

   • Along with any .old versions of these files

6. Note the times when the issues occurred so you can locate the relevant sections of the log files.

There are times when it is not necessary to have all this information, but when in doubt, it is better to have too much information than too little.

https://support.microsoft.com/en-my/help/3121002/windows-10-devices-can-t-connect-to-an-802-1x-environment

To add these registry values, follow these steps:

1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. Locate and then click the following subkey in the registry:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\RasMan\PPP\EAP\13

3. On the Edit menu, point to New, and then click DWORD Value.
4. Type TlsVersion for the name of the DWORD value, and then press Enter.
5. Right-click TlsVersion, and then click Modify.
6. In the Value data box, use the following values for the various versions of TLS, and then click OK.

   TLS version	DWORD value
   TLS 1.0	0xC0
   TLS 1.1	0x300
   TLS 1.2	0xC00

7. Exit Registry Editor, and then either restart the computer or restart the EapHost service.

~\Desktop> Get-Service Eaphost

Status Name DisplayName
------ ---- -----------
Running Eaphost Extensible Authentication Protocol

~\Desktop> Restart-Service Eaphost

https://docs.microsoft.com/en-us/windows/client-management/advanced-troubleshooting-802-authentication

On the client side, navigate to Event Viewer (Local)\Applications and Services Logs\Microsoft\Windows\WLAN-AutoConfig/Operational for wireless issues. For wired network access issues, navigate to ..\Wired-AutoConfig/Operational. See the following example: