Re: suddenly not connecting to remote machines

I haven't heard of the following affecting VNC yet, and partly because
VNC is likely using openSSL and/or openSSH for your encrypted
connection (I'm guessing and don't know exactly what you've set up)

But you might find interesting that on many Desktops on some distros
that receive most recent upstream packages that gnutls packages have
wreaked havoc, and the solution has been to downgrade.

I haven't heard that openSSL or openSSH have experienced similar
problems yet, but it seems that some encryption changes may be coming
and your distro(s) might have received such in an update.


On Tue, May 28, 2019 at 8:21 AM Gary Dale <[email protected]> wrote:
>
> I doubt it. Different clients and different servers all developing the
> same problem at the same time? After thinking about it some more, I'm
> thinking that the problem lies in the only common component - the ssh
> tunnel and specifically the port forwarding. If that isn't working, it
> would explain the symptoms exactly.
>
> I'm going to raise the issue on a Debian list.
>
>
> On 2019-05-28 6:03 a.m., Pencoys wrote:
> > vnc has a timeout timer for inactivity. depending on the vnc version you have,
> > i.e. Realvnc Tightvnc etc. it will be called something different, but similar
> > to activity timeout. somewhere in general settings - set it to zero IIRC
> > This could be your problem. hth, Mike G8NXD
> >
> > On 28 May 2019 at 5:28, Gary Dale wrote:
> >
> >> I'm running Debian/Testing on an AMD64 machine.
> >>
> >> I follow what I believe is a fairly conventional way of connecting to
> >> remote machines. Firstly I establish an SSH tunnel using a command like:
> >>
> >>     ssh <remote server public IP> -L 5902:<remote workstation local
> >> IP>:5900
> >>
> >> where the remote server public IP is that of the router (DD-WRT) with
> >> port 22 forwarded to the local IP of a remote Debian/Stable server. The
> >> remote workstation IPs are in the 192.168.1.* range. The SSH connection
> >> works fine.
> >>
> >> Then I connect to localhost:5902 using a VNC viewer (tried a few).  I've
> >> been doing this for a decade with no significant problems.
> >>
> >> However I haven't been able to do this since at least yesterday
> >> (previous remote login was a week ago. It worked). No matter which
> >> remote machine I try to connect to, I never get to the password prompt.
> >> Instead the connection attempt eventually attempt times out.
> >>
> >> I can log onto a KVM virtual machine running on the remote server using
> >> the Virtual Machine Manager GUI. From there I can connect to the other
> >> (real) machines using the Tight VNC viewer.
> >>
> >> I'm stumped. The KVM service is clearly working on the remote
> >> workstations since I can connect to them from the virtual machine. Any
> >> ideas?
> >>
> >>
> >>
> >> ___________________________________________________________
> >> TightVNC mailing list, [email protected]
> >> To change your subscription or to UNSUBSCRIBE, please visit
> >> https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
> >
> >
>
>
> ___________________________________________________________
> TightVNC mailing list, [email protected]
> To change your subscription or to UNSUBSCRIBE, please visit
> https://lists.sourceforge.net/lists/listinfo/vnc-tight-list


___________________________________________________________
TightVNC mailing list, [email protected]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list