Jump to content

Server refused client


multiforme

Recommended Posts

Posted
[2017-04-19T11:27:10] INFO: OpenSSL 1.0.2 22 Jan 2015
[2017-04-19T11:27:10] INFO: accepted secure socket
[2017-04-19T11:27:10] INFO: AES256-GCM-SHA384       TLSv1.2 Kx=RSA      Au=RSA  Enc=AESGCM(256) Mac=AEAD
[2017-04-19T11:27:10] NOTE: accepted client connection
[2017-04-19T11:27:10] WARNING: unrecognised client name "xxxxx", check server config
[2017-04-19T11:27:10] NOTE: disconnecting client "xxxxx"
[2017-04-19T11:27:10] NOTE: client "xxxxx" has disconnected

This is from the server logs (Windows 10, last version of Synergy). I have allowed Synergy in the Windows firewall (and it's not something that has to do with the network firewall as the same config used to work before I formatted my Win machine). The network is set as private and the PC is discoverable from network devices.

This instead is from the client (Macbook running OSX):

[2017-04-19T11:28:28] NOTE: connecting to '10.0.110.194': 10.0.110.194:24800
[2017-04-19T11:28:28] INFO: OpenSSL 1.0.2 22 Jan 2015
[2017-04-19T11:28:28] NOTE: server fingerprint: B7:C0:1C:47:CE:95:C9:xx:xx:XX:XX:XX:XX:XX:XX:XX:XX:XX:D8:4C
[2017-04-19T11:28:28] INFO: connected to secure socket
[2017-04-19T11:28:28] INFO: server ssl certificate info: /CN=Synergy
[2017-04-19T11:28:28] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD
[2017-04-19T11:28:28] ERROR: server refused client with name "xxxxx"
[2017-04-19T11:28:29] WARNING: failed to connect to server: server refused client with our name

I have read somewhere that previous versions had a problem with dashes in the client/server names so I removed them from both but no luck.

  • 4 weeks later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...