EZ-IP Force Disconnect
Hi! Can someone tell us if there's a way to force a disconnect of user sessions from the EZ-IP panel? Somewhere in Settings or somewhere?
Especially with folks who have been connected for days?
We are currently using using version 9.0.5x151 of Acronis ExtremeZ-IP. Any help would be appreciated.
Okay great! And yes, we know about the disconnect option which is what we are trying to avoid. Sucks having to do it manually one by one. We will try this idle time fix.
@Mike - Sorry, just want to be sure. The valuedata for this binaryvalue is currently set to 0 (zero). any preference on what we should set it to?
Yes, as mentioned previously 0 is the default value for TimeoutIdleUsers (0 = off, 1 = on). There are no real preferences from the support perspective of view: if enabled - it will control that idle users are timed out after some period of time, if disabled - it won't control. That's it. So, in your use-case I would turn it on and check the difference.
Okay thanks! It's on. Let's see how it works! Would be nice to know what the actual idle time is. Is there a way to check?
Hi monaronyc,
Here you'll find additional information on how to set certain timeout periods and the default values.
Thank you,
Can you tell us if there's maybe a way to set the disconnects using the Connected Time column instead of the Idle Time? It appears that there is always activity using the idle time and these setting(s) are not working the way they should.
No standard way I'm aware of. I'd raise a support ticket for your specific scenario, so that our engineers can look into.
Thank you,
Okay then how about this... is there a way to disconnect a particular user after so many hours of being connected?
If you want to disconnect a particular user, you can do this via Users tab in the Access Connect Administrator window. Additionally we can configure default policies using the following registry keys. These policies will be applied to all users. If you want to implement a non-standard scenario that is not covered in the provided sources, it's highly recommended to open a support ticket. Our engineers have direct contact to the development team and can better address your particular scenario.
Thank you,
Using a similar approach of:
this.socket = io.connect( 'ws://127.0.0.1:3000', {
reconnection: true,
reconnectionDelay: 1000,
reconnectionDelayMax : 5000,
reconnectionAttempts: Infinity
} );
Unfortunately, this causes the socket to use http protocol, rather than web sockets.
Still seeking a good approach for a persistent web socket connection.
Have I missed something???