My client PC connects to the AP, however it doesn't send or receive any packets once it has been authenticated
Posted by Gabriel Yu on 14 March 2008 06:54 AM
Your PC can't send or receive packets after the PC
connects because the client PC was never actually authenticated to the
access point â€” it only got as far as associated to the AP.Â The confusion is understandable because the terms both sound similar, and have similar meanings.Â |
Authentication is simply a way for the device to verify the identity of another device that's attempting to connect to it.
The first step in establishing a connection is to check that the other device is available, and so the PC first "associates" with the AP. During the association no information other than challenge/request handshake passes between the devices.
The Authentication challenge handshake uses the encryption key, and so the only way the two devices will authenticate is if they both have the same security settings, including encryption key.
If your client PC doesn't have the matching WEP/WPA key, it can 'see' the AP in the list of available networks and associate to the AP, but cannot authenticate against it - and consequently there is no data trransfer.
Our recommendation is to double-check the security parameters on the PC against those on the AP.Â If necessary, turn OFF all wireless security mechanisms, check that the hardware works OK, then turn on the security one step at a time.Â If it stops working, then you know exactly which setting is responsible.
For more information, see the Wi-Fi Planet tutorial Explaining Wi-Fi Authentication and Encryption.