11-20-2007 06:33 AM - edited 07-03-2021 02:58 PM
Hello,
I've been having a problem for the past few weeks. Before upgrading our wireless infrastructure with the WLC we just used standalone 1242's. 802.11b devices would connect to an ssid using wpa-psk. Something has happened lately and these devices won't work anymore, laptops and other devices work with the same ssid just fine.
If I should send more info just let me know.
Hope you can help.
I am attatching a debug client log for one of these devices, the only errors I see are dhcp, but the clients have always been setup statically:
11-20-2007 06:54 AM
This has been fixed, just changed from static to dhcp on the client.
Odd, static should work as well I would think.
11-21-2007 12:51 PM
It is likely that you have a 'DHCP Required' rule in the WLAN settings. If you disable / remove this setting, the WLC will not required clients to get a DHCP IP Address before granting them access to the network.
Regards,
Richard.
11-21-2007 12:54 PM
No, DHCP required is not enabled on the WLC. I checked this.
11-21-2007 02:11 PM
Sometimes there are issues using static IP addresses on the client side. This can result in the client associating but not authenticating as the clients ARP entry never hits the controller and thus the client is never in the controllers client list. Use DHCP when necessary, 90 percent of tac calls at Airespace were a result of not using dhcp.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: