vnc connect timeouts (145) but ssh/telnet session does not
JAldrich "at" covista.com
Thu Jan 26 17:58:02 2006
Ahh... I see. Yes, you might want to consider increasing the timeout before
VNC Viewer closes. I think that's controlled in the server. Maybe someone on
the list with more knowledge than I can provide you with a better answer.
From: Ariel Burbaickij [mailto:ariel.burbaickij "at" gmail.com]
Sent: Thursday, January 26, 2006 12:37 PM
To: John Aldrich
Subject: Re: vnc connect timeouts (145) but ssh/telnet session does not
1) It is through the internet
2) It (vncviewer) is not tunneled from the machine it is physically running
on but its window is presented on some other machine by means of X11
forwarding of ssh.
Do you suggest to increase inactivity timer?
On 1/26/06, John Aldrich <JAldrich "at" covista.com> wrote:
> Are you connecting to the server over the local LAN or through the
> Also, if the latter is the connection tunneled? I have a similar situation
> where if I leave the viewer open, my VNC session will time out for
> inactivity and I have to relaunch it, but the SSH session, through which
> I've tunneled VNC, is still open and responding. For me, it's just an
> inactivity timeout and I can reconnect to the same desktop just fine.
> -----Original Message-----
> From: vnc-list-admin "at" realvnc.com [mailto:vnc-list-admin "at" realvnc.com]On
> Behalf Of Ariel Burbaickij
> Sent: Thursday, January 26, 2006 11:48 AM
> To: vnc-list "at" realvnc.com
> Subject: vnc connect timeouts (145) but ssh/telnet session does not
> Dear all,
> we have following IMHO strange situation where vnc connection times
> out with the code of
> 145 but ssh or telnet remains stable and run further. Could you,
> please, advise me in what
> direction to look or what additional information you would need in
> order to be able to provide
> meaningful answer.
> With Best Regards
> Ariel Burbaickij
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit: