I have the exact same issue in our environment with Windows 2008 DHCP and DNS. Every other imaginable device registers a DNS record properly with the exception of the Cisco AP's. The AP's do not appear to be providing FQDN therefore the DNS server is rejecting it according to the audit logs.
I believe that we need the AP to provide the domain name suffix in order to register properly. Anyone successful in correcting this? WIll it do any good to open a TAC case?
It's been 2.5 years since I dealt with this but we did get it to work, my apologies if I don't have the exact information but I do remember the general fix. We did set the DHCP server to always update DNS as mentioned in the first post. It then became a permissions issue with the DHCP server/service account not having permissions to update DNS. After that it worked.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...
I have created a Powershell script to automatically add a Wireless Guest
User on Cisco WLCs. (tested on 2500 Series) The script should be
completely self explanatory. Prerequisites: Powershell SNMP Module
(Install-Module -Name SNMP) SNMP Write Access to y...