02-20-2012 02:25 PM - edited 07-03-2021 09:37 PM
I have a 5508 WLC running 6.0.202.0. It functions as the Anchor Controller for the guest network. It sits in our Internet DMZ and is isolated from the rest of the network. It does not connect to AD, ACS, etc. The guest wireless WLAN is configured for Web Policy - Authentication. I have a customized login page. Credential management is done by WCS.
Users are connecting to the guest wireless network and entering their creds with no issues using mobile devices (iPad, etc). Then the mobile device goes to sleep / turns off and when they go to use it again, they have to type their creds in again. They dont like retyping their creds throughout the day.
Any suggestions for a good way mitigate the multiple logins? Something like a 'save password' option on the customized page?
Solved! Go to Solution.
02-20-2012 02:44 PM
more than likely it's the user idle timeout which is set to 300 seconds 5 minutes by default. You could set this to be 28800 which is 8 hours.
Steve
Sent from Cisco Technical Support iPhone App
02-20-2012 06:45 PM
In addition to the user idle timeout. You also want to make sure the session timeout under the WLAN advance tab which is set by default to 1800 seconds (30 minutes) is moved up as well.
User Idle Timeout -- If the user doesn't send any packets for default 300 seconds the WLC deletes the clients record. Which causes the client to reauth. i devices are very clean. they dont chat a lot unless a user sets up pushs.
Session Timeout -- After a user authenticates to the WLC. The timer kicks in and when it expires it kicks the users a DEAUTH frame, which will cause the client to reauth again..
Hope this helps...
02-20-2012 02:44 PM
more than likely it's the user idle timeout which is set to 300 seconds 5 minutes by default. You could set this to be 28800 which is 8 hours.
Steve
Sent from Cisco Technical Support iPhone App
02-20-2012 06:29 PM
Steve's right, that is the user idle timeout on the General->Controller tab. Adjust it something higher and those users won't have that issue. I've done that at a few sites.
02-20-2012 06:45 PM
In addition to the user idle timeout. You also want to make sure the session timeout under the WLAN advance tab which is set by default to 1800 seconds (30 minutes) is moved up as well.
User Idle Timeout -- If the user doesn't send any packets for default 300 seconds the WLC deletes the clients record. Which causes the client to reauth. i devices are very clean. they dont chat a lot unless a user sets up pushs.
Session Timeout -- After a user authenticates to the WLC. The timer kicks in and when it expires it kicks the users a DEAUTH frame, which will cause the client to reauth again..
Hope this helps...
02-21-2012 06:01 AM
Thanks guys - I had already extended the Session Timeout. Wasnt aware of the User Idle Timout. I just extended it and will see how it goes.
02-23-2012 08:37 AM
You guys nailed it. Much better now.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide