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:
— Level 9 logfile from the server of a connection attempt from the TightVNC client
— Wireshark capture of a connection attempt from the TightVNC client
— Wireshark capture of a connection attempt from the RealVNC client
I hope someone can help us with this. Please let me know if additional information or logging is needed.
Измеряйте по нескольким показателям.
RTD —
ping dst_host -l 100
Jitter —
Iperf –s –u –l 100 ->> это на стороне "сервера"
Iperf -u –c адрес сервера –t 900 –b заявленная пропускная способность –l 100
Packet loss —
Iperf –s –u –l 1470 ->> это на стороне "сервера"
Iperf -u –c адрес сервера –t 900 –b заявленная пропускная способность –l 1470
Понятно дело, что это будут не совсем точные показания, т.к. в iperf задается не полная генерируемая полоса, а только полоса потокa UDP датаграмм без учета l2-l4 заголовков, есть коэф.снижения, но пока можете обойтись без них. Сделайте хотя бы так, а то с обращением «у меня проблемы с tightvnc в канале» вас любой провайдер отошлет в сад/лес. Ну и длину (-l параметр) крутите под себя
Wireshark`ом посмотрите еще, что у вас в сети происходит
Можете еще провайдера попросить выполнить измерения (Packet loss, RTD, jitter, OWD) вашего канала точка-точка, без участия вашего оборудования (ибо не хер)))
Изменено 5 августа, 2015 пользователем ilili
Posted by rod.fuller 2016-03-16T15:21:04Z
We have recently been having issues with TightVNC when connecting across the WAN VPN to remote users. We can’t stay connected. Get a socket error or an invalid data error. We’re not sure if this is caused by a recent change in AV solution (we’ve whitelisted per the AV vendor’s instructions) or a recent update in Windows. Anyone else having similar issues?
6 Replies
-
I use tight VNC and have not had this issue. Have you tried it without the new AV? Also any new firewall changes?
Was this post helpful?
thumb_up
thumb_down
-
No changes in firewalls but we have not tried removing the AV to see if it resolves it. Have tried both the app and java applet to connect with similar results. Also tried all the different options of encoding. One of the errors is: failed to receive data from socket. The other is a TCP socket error.
Was this post helpful?
thumb_up
thumb_down
-
Tads06
This person is a verified professional.
Verify your account
to enable IT peers to see that you are a professional.thai pepper
I’ve never had luck with connecting to users through a WAN VPN, I’ve always had to use something like join.me. But if it’s site-to-site VPN it should work fine.
Was this post helpful?
thumb_up
thumb_down
-
Check LAN card powersave issues.
Was this post helpful?
thumb_up
thumb_down
-
This happens when remoting into multiple sites from multiple PCs.
Was this post helpful?
thumb_up
thumb_down
-
Turns out it was Vipre even though we had VNC whitelisted as they had suggested.
Was this post helpful?
thumb_up
thumb_down
Loading
TightVNC File transferring problem
The issue i got is that when i connect remotely and try to upload file from my computer in the middle of uploading it just disconnects and this errors comes up » Failed to recv data From socket» and i discovered that if the file is less than 10mb this error wont come up if is more than 10mb like 14mb
it disconnects you and get this error » Failed to recv data From socket»
please help
Thanks in Advance
Archived post. New comments cannot be posted and votes cannot be cast.