dslreports logo

    All FAQs Site FAQ DSL FAQ Cable Tech About DSL Distance DSL Hurdles »»


how-to block ads

- WPA is a key-exchanging encryption and authentication method. The correct keys must be exchanged within a certain time and order.
- If this is not completed, the process ends by interrupting communications. Both the client and AP perform this checking and either one (or both) may be the side with the problem.
- This communications interruption is a possible cause for the DHCP failure.
- Because of profile corruption or bugs in some software, this problem can affect wireless products that are not configured to use WPA, WPA-PSK or 802.1X. Use these same steps if you are having the described problems and are using WEP or no encryption.
- Some 802.11 software and hardware products are more robust than others. Some products may not tolerate unexpected issues like an AP changing security methods, a frequently rebooting AP or client, or multiple security profiles for a single access point.

The purpose of these steps is to give a hardware and software independent method of resolving the issue of repeated communication lockouts between a wireless Access Point and a wireless client computer.

- You repeatedly get a message from a wireless computer about Limited Connectivity because you did not get an IP address, or you are assigned an APIPA 169.254 address.
- If you have set a manual IP address, the wireless client says it is connected, but it repeatedly is not communicating or it stops communicating within 5 minutes of connecting every time
- Even though you have saved profiles for your wireless Access Point (AP), some clients repeatedly refuse to attempt to connect
- In Event Viewer, DHCP and TCPIP appear in the system event logs over and over, and rebooting has not solved the problem

- Reboot your wireless computers and power-cycle your AP.
- Turn off any options to hide your SSID from broadcasts.
- Turn off any proprietary speed-enhancing technologies.
- On your wireless client, delete and re-create your saved profile.

1. On your wireless AP, change your SSID to something that you have never used before.
2. Unplug power to your AP, take note of the time
3. Remove all saved profiles for that AP from your wireless computers
4. Reboot your wireless computers
5. After 65+ minutes from step 2, plug in your router
6. Using your wireless computers, associate with the new SSID
7. Leave the client connected for 65+ minutes. There may or may not be indications of up to two brief reconnections during this time. Do not reboot the AP during this time.
8. Shut down or reboot your wireless client computer normally (do not sleep, hibernate, or abruptly power-cycle).

TIP: The 65+ minute wait in step 5 may not be necessary for your hardware or software. If you only have one or two clients, you may wish to first try these steps without that wait. If they are not successful, then try all of the steps again with the wait.

WHY THIS WOULD WORK (IF IT WORKS): Setting up a new SSID causes the clients to create a new, clean, and correct profile for the access point. Rebooting the hardware is one attempt at clearing authentication failure lockouts. Waiting 65 minutes with the router off is another. Leaving the client online for 65 minutes is to ensure at least one successful key exchange after the initial successful authentication. Shutting down normally allows the software or OS to save configuration or registry information so that you can successfully connect in the future.

Expand got feedback?

by funchords See Profile edited by KeysCapt See Profile
last modified: 2005-07-18 18:59:25