Robert.N.Barrett_2 Fri, 05/01/2009 - 09:28
User Badges:
  • Bronze, 100 points or more

Are the autonomous or lightweight AP's? On lightweight AP's - console in to the AP and do a "show hosts". You may see a line that reads something like "default domain =". If so, then that's probably where your problem lies. If you are using DHCP for the AP IP addresses, be sure and hand out domain information. Manually set it otherwise. I think the "show hosts" command works the same way on autonomous APs.

Lightweight AP's will try to resolve CISCO-LWAPP-CONTROLLER as a standard part of locating a controller during the join process. If you don't specify a domain name to be handed out with DHCP address leases, the AP will try to resolve, which is (try it for yourself!). Trying to figure out why APs were resolving CISCO-LWAPP-CONTROLLER to (and not what I had set on my DNS servers) is how I figured all this out.


This Discussion



Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode