Jump to content

Hello! 👋

These forums are now archived (read only).

Join us on Discord.

Leaderboard

  1. Nick Bolton

    Nick Bolton

    Synergy Team


    • Points

      1

    • Content Count

      2460


  2. Gabriel Lujan

    Gabriel Lujan

    Synergy User


    • Points

      1

    • Content Count

      3


  3. Paul Suarez

    Paul Suarez

    Synergy User


    • Points

      1

    • Content Count

      2492


  4. Paul C Craggs

    Paul C Craggs

    Synergy User


    • Points

      1

    • Content Count

      33


Popular Content

Showing content with the highest reputation on 08/07/17 in all areas

  1. I'll do a rolling start, then final one where the mouse gets stuck and ghosts.
    1 point
  2. @Paul Suarez The problem has nothing to do with DNS. Synergy simply connects through the first working network connection that it finds. It's pure coincidence that it didn't use the manually configured ethernet connection. It doesn't matter if there is DNS configured or not. As long as one of your connections has valid DNS configured, the cloud discovery feature will work. I think we'll be forced into doing this sadly, but it'll be a hidden/advanced setting for sure. Going forward, we'll probably try implementing a feature to test all available connections simultaneously, choosing the
    1 point
  3. Thanks @Gabriel Lujan. Our developers are trying to reproduce it. They might be able to cross reference your logs to what they will be getting(if it crashes on them).
    1 point
  4. I'm having the same issue and just wanted to pass along another log from my machine. Hopefully it helps. :-) I took Paul's lead and created a Gist for it: https://gist.github.com/anonymous/3c0cf802d193857466e35d2617f9ef69.
    1 point
×
×
  • Create New...