one of the user getting , timeout message pops up saying a very long duration before disconnect will occur. It doesn't disconnect the session, which is okay, but this message should only pop up within 5 minutes of reaching the 24 hour absolute session timeout. This window is not supposed to present itself before that point, and clearly not with such a large number of seconds.
The network connect session will time out due to inactivity in 71582783 minutes 31 seconds (nc.windows.app.24052)
this message is weried and wants to fix it as it happens on cio.
Can you run a policy trace or find from he user access logs what role/roles this user is getting.
Check under those roles--->general session options the timeout settings.
I just got this, today and found my way here by Googling this message, so it's still present in modern versions of Network Connect.
71 and a half million minutes... Just shy of 136 years and 70 days! Where does that number come from? Well, it's actually 4,294,966,980 seconds, which is just shy of 4,294,967,296, which is two to the power thirty two...
So it's definitely a random 4-byte binary barf, generated by some misconfiguration in the secure gateway, or in how it's communicating with the client. Disconnecting and reconnecting usually makes it go away, but if it persists, look to the settings on the gateway.
If you allow multiple sessions, this can be an issue as I've seen this where users are connecting with multiple sessions. They use one session so the other session will time out. Check your user logs to see how many session ID's are being used.