I'm facing a weird issue, I've one SSID for which all authentications are 100% correct, but now I need to use a new vlan with the same configuration, I did it, but the web page doesn't be displayed but when I entred the virtual interface I have the cisco web authentiaction and no the customized web page !!
I saw the cisco document for "web authen troubleshooting" but no solution solves my problem, any suggestion?
Well there are many things here. First off, make sure you can preview the custom WebAuth from the WLC GUI. Then I would enable the default and hit apply then set it to custom and hit apply. In some code versions there was an issue and you had to perform this.
You also need to have DNS working, which is very important. I always tell people to connect a laptop to the same vlan as your WebAuth and make sure you get an IP address and connect fine to the Internet. If this fails then your WebAuth will never happen.
As per your query i can suggest you the following solution-
After you configure web authentication, if the feature does not work as expected, complete these troubleshooting steps:
1.Check if the client gets an IP address. If not, users can uncheck DHCP Required on the WLAN and give the wireless client a static IP address. This assumes association with the access point. Refer to the IP addressing issues section of Troubleshooting Client Issues in the Cisco Unified Wireless Network for troubleshooting DHCP related issues.
2.On WLC versions earlier than 220.127.116.11, you must manually enter https://18.104.22.168/login.html in order to navigate to the web authentication window.
The next step in the process is DNS resolution of the URL in the web browser. When a WLAN client connects to a WLAN configured for web authentication, the client obtains an IP address from the DHCP server. The user opens a web browser and enters a website address. The client then performs the DNS resolution to obtain the IP address of the website. Now, when the client tries to reach the website, the WLC intercepts the HTTP Get session of the client and redirects the user to the web authentication login page.
3.Therefore, ensure that the client is able to perform DNS resolution for the redirection to work. On Windows, choose Start > Run, enter CMD in order to open a command window, and do a “nslookup www.cisco.com" and see if the IP address comes back.
On Macs/Linux: open a terminal window and do a “nslookup www.cisco.com" and see if the IP address comes back.
If you believe the client is not getting DNS resolution, you can either:
Does entering this URL bring up the web page? If yes, it is most likely a DNS problem. It might also be a certificate problem. The controller, by default, uses a self-signed certificate and most web browsers warn against using them.
So the issue then is DNS. If you can't display the splash page when you go to http://22.214.171.124, the your DNS isn't working properly or your NAT isn't enabled for that new subnet. Connect a laptop to that vlan on the switch and test... if that wired laptop can't browse the internet, then you have a network issue that you need to fix.
Help out other by using the rating system and marking answered questions as "Answered"