Hi,
I use Captive Portal for my students and they are only allowed to be on 1 machine at a time. I use local directory
Lately I have had an increase in students being unable to log in with their credentials getting the error message: "User is already logged in from another location".
I have instructed them in the logout procedure and made an easy quicklink, that redirects to the actual logout site. This seems to work fine, but I see an increase in the above problem even for students using only one machine (no phone or tablet, only computer).
Is there an issue I am not aware of?
Can I somehow release access for users making them able to log in again (other than changing their credentials as I do now)?
When they experience the problem, they sometimes have it for days (you know how fast teenagers react...). Shouldn't Untangle automatically release their login after the session timeouts (180 minutes) and thereby be able to log in again?
I have the 1 machine at a time rule enabled to have a more precise activity log and to prevent them from sharing username and password with each other and would like to keep it that way. Otherwise they will use each others logins and mess up the log ;-)
I use Captive Portal for my students and they are only allowed to be on 1 machine at a time. I use local directory
Lately I have had an increase in students being unable to log in with their credentials getting the error message: "User is already logged in from another location".
I have instructed them in the logout procedure and made an easy quicklink, that redirects to the actual logout site. This seems to work fine, but I see an increase in the above problem even for students using only one machine (no phone or tablet, only computer).
Is there an issue I am not aware of?
Can I somehow release access for users making them able to log in again (other than changing their credentials as I do now)?
When they experience the problem, they sometimes have it for days (you know how fast teenagers react...). Shouldn't Untangle automatically release their login after the session timeouts (180 minutes) and thereby be able to log in again?
I have the 1 machine at a time rule enabled to have a more precise activity log and to prevent them from sharing username and password with each other and would like to keep it that way. Otherwise they will use each others logins and mess up the log ;-)