Question: AP uses WPA2 related authentication types, but client cannot connect?
Answer: If your authentication type is WPA2 related ones. And your computer OS is windows XP, please check if you have patched Microsoft KB893357-v2. Please make sure the wireless client should also support 802.11i by reading product manual. Check if configuration exactly matches on both sides. Check system log to find out rejection reason. Wireless sniffering always work. (Airo Peek Wild packets)
Question: What can I do if the client cannot connect to the AP even after checking everything?
Answer: First, if you cannot find out the corresponding log, it is possible that the AP has not received packets from client. Maybe your RF environment is too noisy and channel may need to be changed.
Second, you can capture packets in our firewall. To check whether there are any DHCP packets. Please make sure your DHCP server has been enabled and have correct range.
Third, if you use WPA-EAP related authentication type:
Make sure radius server is started. Make sure your sever settings are correct. (IP address, radius server port, secret, user settings)
If you use windows server, you can check windows event logs to see event logs.
You can also capture radius related packets at radius server side. (Access request, access challenge, access accept). If you cannot capture any of these packets, it is highly possible that our firewall cannot communicate with radius server properly.
If you cannot see access accept packets after some access request and access challenge packets, you should check you server settings and make sure your secret is correct.