I have configured a Cisco 2100 WLC. I have configured two WLANs, one of them with Web-Authentication. When I connect to it, I get an IP address, and if I open the browser, I was redirected to the authentication page (in the browser toolbar appears "http://188.8.131.52/login.html", I understand that it works correctly), but doesn't load the page, as if not found (I.E. doesn't find).
I searched the Cisco configuration examples, and in this forum, but haven't found any similar problem.
Sorry for not specifying details. I have no proxy server configured in the browser, I have tested with IE and Firefox, and with two different computers (With Windows XP and Windows 7) and I have the same problem, so I think that the problem is in the WLC configuration, but I don't know where,I followed the steps of various manuals and examples of Cisco.
I'm using the internal WLC page for web-authentication, and the "Layout 3 security" is correctly configured in the WLAN.
The WLC is configured to give me as a DNS server, my DNS server on my network, it works correctly, which is in another range of IPs (10.1.1.x), as well as the IP address I assigned the WLC.
Could it be problem of IPs? I have the management interface in the range 172.16.70.x (I have in this range switches and other network appliances, to manage), the dynamic interface I have in the 10.1.1.x range (This is the office general network), and the virtual interface to 184.108.40.206 as has indicated in the manual for Cisco, and the DNS name is "wificontroller".
When the browser is redirect to login page, in the browser toolbar appears the name of the virtual interface ("wificontroller"), but before didn't have a DNS name, and in the browser toolbar appears the IP (220.127.116.11), but I have the same problem. I have the virtual interface configured correctly?
When you manually enter the address 18.104.22.168, can you validate and surf the web?
Check you have the correct DNS and gateway on the clients.
After the problems discussed above, switched WLAN interface with web-auth to use another different range of IPs. When I did, I again had the same problem (In addition, I had not access to network), and was to have incorrectly DNS and gateway.
Also, in my case, I have a Cisco 3750 switch with different VLAN created, customers will get the 3750 IP as gateway.
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...