I don't have the technical expertise to know if issue #112 is or is not related, and I do not have an easy way to test if this behavior can be reproduced without VPN.
This morning, I was able to connect to the same session. The log shows 12 minutes elapsed until *.51 was recognized as gone. The log continues as follows: 05/02/2018 18:17:22 rfbProcessClientNormalMessage: read: Connection timed out 05/02/2018 18:17:22 Client 10.202.110.51 gone 05/02/2018 18:17:22 Statistics: 05/02/2018 18:17:22 key events received 14801, pointer events 51149 05/02/2018 18:17:22 framebuffer updates 41397, rectangles 443340, bytes 714091488 05/02/2018 18:17:22 LastRect markers 15891, bytes 190692 05/02/2018 18:17:22 cursor shape updates 2053, bytes 2475659 05/02/2018 18:17:22 cursor position updates 6, bytes 72 05/02/2018 18:17:22 CopyRect rectangles 8322, bytes 133152 05/02/2018 18:17:22 Tight rectangles 417068, bytes 711291913 05/02/2018 18:17:22 raw equivalent 15672.299680 Mbytes, compression ratio 22.033569 06/02/2018 07:34:18 Got connection from client 10.202.110.53 06/02/2018 07:34:18 Using protocol version 3.8 06/02/2018 07:34:18 Enabling TightVNC protocol extensions 06/02/2018 07:34:19 Full-control authentication enabled for 10.202.110.53 ... -- You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/6319e6ae-70b4-4f90-a820-7b824495a728%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
