On Mon, Feb 1, 2021 at 12:25 PM Bernd Hofner <b...@hofner-informatik.de> wrote:
> ... > My expectation was, that an RDP session opened via Guacamole stays open > "indefinetly". > Yes, that is the standard behavior. Guacamole will maintain connections indefinitely unless they are otherwise disconnected. The current record at my day job for leaving a connection to a work desktop running is 11 days. Is the XRDP setting not working (the sesman.ini warned that IdleTimeLimit > needs xorgxrdp >v0.2.9, so I should be ok there)? > Is there a second place (e.g. in the Guacamole settings) that could cause > a session disconnect? > No, if your users are consistently being disconnected after 10 minutes, the cause must be external to Guacamole. > I hade a look in "Chaper 5 Configuring Guacamole", but couldn't find a > timeout setting except "*api-session-timeout*", > which I would not expect to apply to user sessions. Furthermore, the > default setting of 60 min wouldn't fit to the reported behaviour. > If by "user sessions" you mean "remote desktop sessions", you are correct. The "api-session-timeout" property dictates how long a user will remain logged into Guacamole if they are inactive. Guacamole considers being connected to a remote desktop to be activity. Could a TCP load balancer in front of the Guacamole App servers cause a > similar effect? > Sure - it's conceivable that a balancer might not like long-running TCP connections. I wouldn't expect this to be default behavior. I've only ever encountered that sort of behavior with mobile networks, where the service provider automatically terminates any TCP connections lasting longer than 10 or 15 minutes. - Mike
