Jump to content

Hello! 👋

These forums are now archived (read only).

Join us on Discord.

Can't connect from Mac to Windows server


Recommended Posts

Dave Birkbeck

Hello,

I've been using Synergy for years, with mixed results. I love it when it works, but run into random connectivity issues with new versions.

I just got a new Windows laptop and cannot get Mac to connect as a client. Here are some logs. 

 

[2017-05-18T15:19:24] INFO: OpenSSL 1.0.2 22 Jan 2015

[2017-05-18T15:19:24] INFO: accepted secure socket

[2017-05-18T15:19:24] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD

[2017-05-18T15:19:24] NOTE: accepted client connection

[2017-05-18T15:19:24] WARNING: unrecognised client name "Davids-MacBook-Pro-2.local", check server config

[2017-05-18T15:19:24] NOTE: disconnecting client "Davids-MacBook-Pro-2.local"

[2017-05-18T15:19:24] NOTE: client "Davids-MacBook-Pro-2.local" has disconnected

[2017-05-18T15:19:26] INFO: OpenSSL 1.0.2 22 Jan 2015

[2017-05-18T15:19:27] INFO: accepted secure socket

[2017-05-18T15:19:27] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD

[2017-05-18T15:19:27] NOTE: accepted client connection

[2017-05-18T15:19:27] WARNING: unrecognised client name "Davids-MacBook-Pro-2.local", check server config

[2017-05-18T15:19:27] NOTE: disconnecting client "Davids-MacBook-Pro-2.local"

[2017-05-18T15:19:27] NOTE: client "Davids-MacBook-Pro-2.local" has disconnected

[2017-05-18T15:19:29] INFO: OpenSSL 1.0.2 22 Jan 2015

[2017-05-18T15:19:29] INFO: accepted secure socket

[2017-05-18T15:19:29] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD

[2017-05-18T15:19:29] NOTE: accepted client connection

[2017-05-18T15:19:29] WARNING: unrecognised client name "Davids-MacBook-Pro-2.local", check server config

[2017-05-18T15:19:29] NOTE: disconnecting client "Davids-MacBook-Pro-2.local"

[2017-05-18T15:19:29] NOTE: client "Davids-MacBook-Pro-2.local" has disconnected

Link to post
Share on other sites
Paul Suarez

This usually occurs when you connect a new machine to an existing configuration. Please make sure that you update the Server Configuration for it to recognize the new machine. Since that is a new machine, that should have a different screen name. You need to add a new screen name on the server configuration if you are planning to add that new machine to the existing client and server configuration. You can edit the existing client name if you are planning to replace the previous client machine you have used. You can refer to this knowledge base article for configuration steps.

Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...