04-24-2015 06:15 AM - edited 11-18-2020 03:09 AM
Cisco Wireless 1.1.1.1/login.html redirect issues.
User was using WLC 5500 controller and once the end clients get the DHCP address but the page is not redirecting them to the guest portal.
What is the best way to check as to why the redirection is failing?
That usually points to dns. Is the home page an https, if so, the user will not get redirected. The WLC intercepts the home page when the users opens up a browser and then verifies that dns can resolve the home page. If so, the WLC pushes the WebAuth page to the user. If not, the WLC dies nothing. If your using a 3rd part certificate to get rid of the certificate error, you need to make sure the fqdn can be resolved by the dns the clients are going to use.
Dns should resolve the initial url request then wlc hacks that packet and replace it with 1.1.1.1 instead of the resolved address to show the splash page to user, either u can use the public dns or insider dns that resolves the initial url request.
once client connected to webauth wlan and got an ip, manually type https://1.1.1.1/login.html, does it shows the cert warning and splash page after that, if not try with diff device, could be a browser issue. if it brings the page then like scott mentioned check the dns works thru nslookup.
The main thing if the webauth page does not appear is due to the clients homepage being https not http or dns issues. If you remove the webauth and associate to the ssid, can you access the internet? This will prove that dns is working okay from the guest users.
User followed the below mentioned steps and resolved the issue:
Clients Redirected to External Web Authentication Server Receive a Certificate Warning
Problem: When clients are redirected to Cisco's external web authentication server, they receive a certificate warning. There is a valid certificate on the server, and if you connect to the external web authentication server directly the certificate warning is not received. Is this because the virtual IP address (1.1.1.1) of the WLC is presented to the client instead of the actual IP address of the external web authentication server that is associated with the certificate?
Yes. Whether or not you perform local or external web authentication, you still hit the internal web server on the controller. When you redirect to an external web server, you still receive the certificate warning from the controller unless you have a valid certificate on the controller itself. If the redirect is sent to https, you receive the certificate warning from the controller and from the external web server, unless both have a valid certificate.
In order to get rid of the certificate warnings all together, you need to have a root level certificate issued and downloaded onto your controller. The certificate is issued for a host name and you put that host name in the DNS host name box under the virtual interface on the controller. You also need to add the host name to your local DNS server and point it to the virtual IP address (1.1.1.1) of the WLC.
Error: "page cannot be displayed"
Problem: After the controller is upgraded to 4.2.61.0, the "page cannot be displayed " error message appears when you use a downloaded web page for web authentication. This worked well prior to the upgrade. The default internal web page loads without any problem .
From the WLC version 4.2 and later a new feature is introduced wherein you can have multiple customized login pages for Web authentication.
In order to have the web page load properly, it is not sufficient to set the web-authentication type as customized globally in the Security > Web Auth > Web login page. It must also be configured on a particular WLAN . In order to do this, complete these steps:
A source of pain for many when they get into Cisco Wireless Guest services. Great post to point users to for information with very informative links. Thanks for sharing Vinay! +5
We are just facilitators, we would like to thank you guys for your expertise and enthusiasm for helping community users. Hope to see you sometimes :-)
Hi Vinay,
I am facing a similar issue wherein the following happens:
The user is having troubles to connect external guests with external laptops to connection “guest”:
What are my options here?
How can i troubleshoot this? All i have is the access to the router.
Kindly help.
Regards,
Shubham
Hi,
We also facing same issue. Anyone got the solution for the same.
Thanks,
Did you guys try using Internet Explorer rather than Chrome ?
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: