No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.

Knowledge Base

Windows XP system defect lead to WLAN network remote desktop terminal got disconnected

Publication Date:  2012-09-20  |   Views:  195  |   Downloads:  0  |   Author:  SU1000722738  |   Document ID:  EKB1000015449


Issue Description

AP version: V100R003C07SPC100 WA603SN
AC version: V100R003C05SPC100 WS6603

Alarm Information

When the laptop A remote laptop B, the wireless connection of B will be broken. Encryption is 8021 x + WPA.

Handling Process

1Through the caught found that in every user remote, the remote end laptop will launch an EAPOL START request, while to the re-authentication request message of access side equipment, NIC side has no response, but launched another EAPOL START request.
2 Through the caught further find that after launched four re-authentication request, the AP side launch EOPAL FAIL message to terminal, after this user got disconnected. This realization method is consistent with WS6603, when the user does not response the EAPOL authentication request for four times, WS6603 will end the now authentication process, and launch EAPOL FAIL message to the user.
3 According to the above phenomenon analysis, the problems have no direct relation with access devices, through contrast tests with the C factory equipment found that C factory equipment also exists the problem (user remote once and the remote terminal correlated off), and further confirmed the problem has no relationship with access equipment, but the NIC driver and operating system have direct relationship.
4 After changing the operating system to WIN7 operating system, do the test in C manufacturer and huawei equipments were no this problem, it confirms the above conclusion: It isn’t the network equipment side issue, but the realization mechanism of terminal PC operating system.

Root Cause

When the users use laptop A remote laptop B, for laptop B users, in fact it is a cancellation to re-authentication process (Microsoft operating system's inherent processing mode). In this process, the N/A will launch EAPOL START request, after received EAPOL START request, AP will do authentic again to the users, while in this case the NIC side can't launch the follow-up authentication reply message, leading to the user got disconnected.
Note: XP and previous operating system all have the problem, but the WIN7 does not exist the problem. It has no relationship with access equipment, whether huawei or C factory equipment, or other friendly business equipment, as long as in the 8021 x + WPA authentication mode, would have this problem.