Menu

#1542 Failed to recv data from socket

open
nobody
None
5
2025-09-25
2020-12-30
No

I'm having an issue with several P.C's using TightVNC.

I have several client P.C's both in the one venue with static I.P addresses.

When I launch a game on say (PC number 1) then launch on (PC number 2) the intro/trailer to the game on P.C number one freezes. Several moments later I'm presented with a message:

"Failed to recv data from socket"

This also appears when P.C is left idle for around an hour.

There seems to be no disconnect in terms of internet as both can be sitting in an online lobby.

Also this issue is only happening with TightVNC and there appears to be no issue (freezing) on the client P.C.

Have tried the latest version of TightVNC and also the older version.

Hope you can help.

Regards,

Stephen

Related

Bugs: #1542

Discussion

  • Anton

    Anton - 2021-01-01

    Hi, please send loglevel 9 server log to support@tightvnc.com

     
    • Stephen Kerr

      Stephen Kerr - 2021-01-02

      I will send this tomorrow. Do I need to replicate the problem that day
      before sending the log file?

      Regards,

      Stephen

      On Fri, 1 Jan 2021 at 05:56, Anton anton19286@users.sourceforge.net wrote:

      Hi, please send loglevel 9 server log to support@tightvnc.com

      Status: open
      Group:
      Created: Wed Dec 30, 2020 02:25 PM UTC by Stephen Kerr
      Last Updated: Wed Dec 30, 2020 02:25 PM UTC
      Owner: nobody

      I'm having an issue with several P.C's using TightVNC.

      I have several client P.C's both in the one venue with static I.P
      addresses.

      When I launch a game on say (PC number 1) then launch on (PC number 2) the
      intro/trailer to the game on P.C number one freezes. Several moments later
      I'm presented with a message:

      "Failed to recv data from socket"

      This also appears when P.C is left idle for around an hour.

      There seems to be no disconnect in terms of internet as both can be
      sitting in an online lobby.

      Also this issue is only happening with TightVNC and there appears to be no
      issue (freezing) on the client P.C.

      Have tried the latest version of TightVNC and also the older version.

      Hope you can help.

      Regards,

      Stephen

      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/vnc-tight/bugs/1542/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       

      Related

      Bugs: #1542

      • Stephen Kerr

        Stephen Kerr - 2021-01-09

        Hi,

        I’ve sent this through but not sure if you guys have received it or not.

        Regards,

        Stephen

        On Sat, 2 Jan 2021 at 19:11, Stephen Kerr stephenkerr@users.sourceforge.net
        wrote:

        I will send this tomorrow. Do I need to replicate the problem that day
        before sending the log file?

        Regards,

        Stephen

        On Fri, 1 Jan 2021 at 05:56, Anton anton19286@users.sourceforge.net wrote:

        Hi, please send loglevel 9 server log to support@tightvnc.com

        Status: open
        Group:
        Created: Wed Dec 30, 2020 02:25 PM UTC by Stephen Kerr
        Last Updated: Wed Dec 30, 2020 02:25 PM UTC
        Owner: nobody

        I'm having an issue with several P.C's using TightVNC.

        I have several client P.C's both in the one venue with static I.P
        addresses.

        When I launch a game on say (PC number 1) then launch on (PC number 2) the
        intro/trailer to the game on P.C number one freezes. Several moments later
        I'm presented with a message:

        "Failed to recv data from socket"

        This also appears when P.C is left idle for around an hour.

        There seems to be no disconnect in terms of internet as both can be
        sitting in an online lobby.

        Also this issue is only happening with TightVNC and there appears to be no
        issue (freezing) on the client P.C.

        Have tried the latest version of TightVNC and also the older version.

        Hope you can help.

        Regards,
        Stephen

        Sent from sourceforge.net because you indicated interest in
        https://sourceforge.net/p/vnc-tight/bugs/1542/

        To unsubscribe from further messages, please visit
        https://sourceforge.net/auth/subscriptions/


        Status: open
        Group:
        Created: Wed Dec 30, 2020 02:25 PM UTC by Stephen Kerr
        Last Updated: Fri Jan 01, 2021 05:56 AM UTC
        Owner: nobody

        I'm having an issue with several P.C's using TightVNC.

        I have several client P.C's both in the one venue with static I.P
        addresses.

        When I launch a game on say (PC number 1) then launch on (PC number 2) the
        intro/trailer to the game on P.C number one freezes. Several moments later
        I'm presented with a message:

        "Failed to recv data from socket"

        This also appears when P.C is left idle for around an hour.

        There seems to be no disconnect in terms of internet as both can be
        sitting in an online lobby.

        Also this issue is only happening with TightVNC and there appears to be no
        issue (freezing) on the client P.C.

        Have tried the latest version of TightVNC and also the older version.

        Hope you can help.

        Regards,

        Stephen

        Sent from sourceforge.net because you indicated interest in
        https://sourceforge.net/p/vnc-tight/bugs/1542/

        To unsubscribe from further messages, please visit
        https://sourceforge.net/auth/subscriptions/

         

        Related

        Bugs: #1542

  • german

    german - 2021-04-21

    The same here. Seems specific to reaching MacOS

    Will try when debugging

     
    • Stephen Kerr

      Stephen Kerr - 2021-04-22

      Task manager shows it hitting 100% over network.

      Same internet as before no change. Only change is new p.c’s

      On Thu, 22 Apr 2021 at 00:55, german lechapelaing@users.sourceforge.net
      wrote:

      The same here. Seems specific to reaching MacOS

      Will try when debugging

      Attachments:


      Status: open
      Group:
      Created: Wed Dec 30, 2020 02:25 PM UTC by Stephen Kerr
      Last Updated: Fri Jan 01, 2021 05:56 AM UTC
      Owner: nobody

      I'm having an issue with several P.C's using TightVNC.

      I have several client P.C's both in the one venue with static I.P
      addresses.

      When I launch a game on say (PC number 1) then launch on (PC number 2) the
      intro/trailer to the game on P.C number one freezes. Several moments later
      I'm presented with a message:

      "Failed to recv data from socket"

      This also appears when P.C is left idle for around an hour.

      There seems to be no disconnect in terms of internet as both can be
      sitting in an online lobby.

      Also this issue is only happening with TightVNC and there appears to be no
      issue (freezing) on the client P.C.

      Have tried the latest version of TightVNC and also the older version.

      Hope you can help.

      Regards,

      Stephen

      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/vnc-tight/bugs/1542/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       

      Related

      Bugs: #1542

  • phr3ak

    phr3ak - 2025-07-09

    Dear Developers, May I ask whether the TCP keepalive option is currently enabled, especially in the Windows build? Thank you.

     
    • german

      german - 2025-07-17

      I think I had checked that and it was.
      The connection might be dropped some other way ? It seems to happen more on small bandwidth.

       
  • phr3ak

    phr3ak - 2025-07-30

    No, it doesn't. It should be enabled and this helps in a large percentage of cases. Let's say that it's also worth setting the OS's default timer to about 5 minutes or less.

     

    Last edit: phr3ak 2025-07-30
    • german

      german - 2025-09-25

      Oh, right !

      It is the timeouts that are set!
      And I think they should not.

      I am willing to bet such is your problem (and mine) rather than the keep-alive
      I think keep-alive is more for the routing equipment in-between.

       

Log in to post a comment.

MongoDB Logo MongoDB