To resolve this problem proceed following steps:
•
You will require elevated privileges to perform this step.
•
You will require elevated privileges to perform this step.
The Client service will generate the configuration file based on the template.
5.) wpa-supplicant running
A successful start of the wpa-supplicant can be verified by:
•
•
Table 14–8
wpa-supplicant running – phions.log
Item
802.1X
Non-ethernet adapters
Virtual adapters
Disabled adapters
Active adapters
Table 14–9
wpa-supplicant running – wpa_supplicant_{adapter_uid}.log
Output
CTRL: Open pipe
CTRL: ConnectNamedPipe: connection in progress
Initializing interface '{adapter_uid}' ...
14.3.7
Runtime
During runtime the wpa-supplicant will re-authenticate periodically. This can be triggered either by the
Client service or the switch.
192 802.1X – Technical Guideline
Delete the corrupted configuration file
Kill the process wpa_supplicant.exe
The Process Explorer or Task Manager will show for every network interface
using 802.1X, a wpa-supplicant, named "wpa_supplicant.exe" as child process
of "phions.exe" appearing in the Process Explorer or Task Manager
If verbose output is enabled following verbose output needs to be present in
the log files:
Output
[009001000001]
[009004000002]
[009002000009]
[009001000002]
[009001000003]
[009001000003]
[009001000003]
[009001000004]
Description
stating that 802.1X monitoring is enabled
stating the authentication method (machine, user, user with
certificate)
802.1x monitor created
reloading adapter list for wpa_supplicant
adapter found to be non-ethernet ...
found virtual adapter ...
found disabled adapter ...
802.1x disabled for adapter ...
Need help?
Do you have a question about the NG Network Access Client SP4 and is the answer not in the manual?
Questions and answers