I have a wireless guest configration up and running using a 4402 controller and a number of 1130AG ap's.
The solution itself works fine. I have it configured for local web based authentication via the lobby administrator and DHCP via an external DHCP server.
Users can connect and login without any problems at all. The strange thing is that the browsers do not seem to autodetect the proxy servers unless I close the browser immediately after a sucesfull login, then restart it. It then detects the http proxy correctly and all is well.
So for example, if a user opens a browser, tries to go to www.cisco.com, the WLC correctly redirects the traffic to the login page. The user logs in and the browser then tries to retrieve the original page, in this case www.cisco.com. This fails with a timeout. I restart the browser and all is fine.
I have the browsers configured for 'auto detect' and in the DHCP server I am passing option 252 with the correct string to locate the wpad.dat file.
with the browser open, and prior to login, I can enter the option 252 string directly into the url bar and the file downloads correctly. Again, if I place a host directly onto the wired vlan and test the wpad.dat file, the browser behaves correctly so I know the file is ok.
Futher, I can see the browser trying to get to the proxy server prior to login, so I think that the browser is getting the wpad file from DHCP and is actually working ok.
I am using IE7 and running 126.96.36.199 on the controller
It looks like the WLC is causing the problem but I cant see where it could be going wrong.
Has anyone else seen this issue before ?
Or perhaps can point me in the right direction.