Description |
This article describes that a few users cannot connect to wifi and get error 'Can’t connect to network' and explains why.
|
Scope | FortiGate 6.4.x,7.0.x,7.2.x. |
Solution |
1) Confirm log for wifi and FortiAP logs, it shows that:
Description: Wireless client RADIUS authentication failure. Action: ActionRADIUS-auth-failureReasonReserved 0.
2) Run wifi debug logs:
# diagnose wireless-controller wlac sta_filter <MAC> 2 # diag debug console timestamp e # diag debug application cw_acd 0x7f # diag debug enable
3) Confirm if the below output from the debug is visible:
v2023-01-12 13:56:05 53365.510 04:ea:56:xx:xx:xx <eh> recv IEEE 802.1X ver=1 type=0 (EAP_PACKET) data len=37 2023-01-12 13:56:05 53365.510 04:ea:56:xx:xx:xx <eh> RADIUS message (type=0) ==> RADIUS Server code=1 (Access-Request) id=17 len=349 2023-01-12 13:56:05 53365.516 04:ea:56:xx:xx:xx <eh> RADIUS message (type=0) <== RADIUS Server code=3 (Access-Reject) id=17 len=44
If the above logs are visible, it shows that Access-reject from radius server then the issue with the Radius server and not the FortiGate. |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.