02-05-2013 06:23 PM - edited 02-05-2013 06:30 PM
Trying to pick some Airhead brains...
I've recently changed some authentication timers because of complaints from users being prompted to re-login too often on open Captive Portal SSID. User Idle Timeout & Logon User Lifetime were changed from 30min to 90 min. DHCP lease times have always been short 35-45min. I did not change those when I changed the auth timeout which I'm now thinking I probably should with the additions of some VLAN's to the VLAN pool.
Analysing, would it make sense that the controller still has a user in a table because of increased timeouts when a new user is trying to use the Wi-Fi with the same IP as the previous IP owner, and as a result, the new user is denied access?
Users are experiencing the inability to bring up captive portal on open SSID and can't do anything when connected to 802.1x either besides getting IP, stuck in logon role.
OS 184.108.40.206. Using MS DHCP.
Thank you in advance.
02-05-2013 07:36 PM
I should also mention that I had to disable IP spoofing because of a bug in 220.127.116.11 where users would get blacklisted, until, supposedly, this is fixed in 18.104.22.168 by the end of this month.