We have a user getting a network connect session timeout message, when the feature is disabled??
Also, the message says -
'The Network Connect session will time out due to inactivity in 71582746 minutes 35 seconds.
Why is that happening when the feature itself is disabled??
First step is to uninstall Network Connect and let it re-install.....
You want to check your Default Options under User Roles>Roles. These take precidence. Also check your NC connection policy, specifically the selected Roles.
Hi, did you get to a resolution in this case?
I have the same problem in 6.3R2
Are you serious? The default role takes precedence over the configured role settings?
Is this true?
Regarding to JTAC, the Session popup for GINA is a old problem that has been comming back in 6.3R2 and shuld be resolved in 6.3R3
a little bit late and maybe also now not interesting anymore, but I wanted to add the following:
If you use ESP as the Transport Protocol of your wish...
All of the above fits.
But in case you use oNCP/NCP(!) you should keep an eye on the SYSTEM -> CONFIGURATION -> NCP Settings ;-)
There individual timeouts for oNCP/NCP to adjust.
Did any one find out why this was happening? I have a user that gets this every couple of minutes and all my time outs are set for 480 min + and why the 316 years timeout? i am running 6.4R4
Which option is disabled, the session reminder timer?
Does this happen for all users or just the one?
The session will always have a timeout on it (max session and idle).
Do you have merging or single roles? If merging, are they all configured without the reminder timer configured OR is the role without the reminder timer configured the first mapped role?
Can you post a screenshot of your role session timer configuration?