Hi,
We get the error 'Failed to recv data from socket' when connecting with TightVNC client to TightVNC server (both latest version).
There are topics about the same error, but those are describing the issue as occurring after a short while.
In our case the error pops up immediately.
We've tried various encoding settings, disabling authentication, etc, but none seem to help.
Strange thing is that when I try the RealVNC client to connect to the same TightVNC server, the connection works flawless. So it seems the RealVNC client works in a different way that is more compatible with TightVNC server than the TightVNC client.
I've enclosed the following files:
I hope someone can help us with this. Please let me know if additional information or logging is needed.
Replicated this on separate systems. Seems to be unique to TightVNC server 2.8.63 (earlier versions also TBD). Occurs when TightVNC server is running remotely. Issue occurred when connected with Tight VNC Client 2.8.63 and Ultra VNC viewer 1.3.6.0.
After changing server from Tight VNC 2.8.63 to UltraVNC Server 1.3.6.0, the issue no longer occurred with either TightVNC Viewer or UltraVNC viewer.
Replicated with a local gigabit direct connection.
Both server and client were Windows 10.
Last edit: J Murphy 2022-01-10
Exact the same here.
Could you test with viewer from previouse version?
https://www.tightvnc.com/download/2.8.59/tightvnc-2.8.59-gpl-setup-64bit.msi