My problem is that once I connect and write a URL takes about 2 minutes to download the Web Page login. Once loaded and introduced the password, it works correctly.
Does someone has found something similar? How can I decrease this time to download the page?
I have two Controller 4402 with software version 188.8.131.52.
It shouldn't take that long. How extensive is your webauth page.
Have you tried another machine and or another browser?
Do you use internal or external page?
URL redirect or direct IP?
It should not be that long, it does take a few seconds, but not 2 minutes. Have you tried on the controller debug client
fella5, yes, I tried with another machine and another browser.
I use a customized the Web Authentication Login Page using the WLC. Customized login page is downloaded to the controller. But, With the default web page the problem is the same.
Did a test in my lab with this code, it takes about 25 to 30 seconds to load the default page, is it the time you find, or is it definitely 2 minutes?
Then, I would try, if it is the same with the default and the personalized page, to run a debug client
I tried it out in my lab and I got around a couple seconds. What you might want to look at is DNS. Try to change your home page to google.com or something. The wlc has to try to resolve the home page before you get the certificate error page and then the login page.
I'm sorry not answer before, but my client was unable to test until today.
Using directly https: / / 184.108.40.206/login.html the time it takes is between 1 minute and a half to 2 minutes, just 15 seconds less.
This is not normal, what may be happening? Do not I can think of nothing?
I believe it has to due with the time it takes to resolve a users home page. Users that associate to another ssid that does not use webauth, how fast is it for them to open up a web page? Take the webauth part out for now to troubleshoot.
When connected to another SSID which is validated through a radius (validation is very fast) and then connects to the Internet via a proxy and the first web page and navigation are proceeding apace.
Ah.... you have a proxy. WebAuth doesn't work well with a proxy since the wlc has to resolve the users homepage and doesn't know of any proxy settings.
If your guest traffic doesn't use a proxy and goes straight out to the internet, then it has to be an issues with DNS. Are you using an internal or public DNS? Your other ssids are internal users, how is your guest network setup. You using a guest anchor controller in a DMZ?
The users guests with WebAuth uses 3 public DNS.
The SSID guests is join a LAN network, which is conected to a ASA5505 and this conected with a DSL router to Internet.
May I renew my suggestion tu run a debug client
Here is a link to look at regarding WebAuth:
I agree, this seems to be DNS related issue. Redirect to the web-auth page works only when you make a http request.
If you can not resove ip address of the page you are requesting, your system is trying for a while and than fail making reqest and so redirect.
Make sure you have correct DNS server set on wireless client.