pbaines

First installation, they can't see each other.

17 posts in this topic

I've been searching the forums and it seems lots of people have similar issues and you request the logs, so I've preemptively pasted them below:

Server (windows):

[ UI ] [2017-08-08T11:58:33] WARNNIG: no font file: Raleway.otf
[ UI ] [2017-08-08T11:58:33] INFO: log filename: C:/Users/pbaines/AppData/Local/Symless/Synergy/synergy.log
[ UI ] [2017-08-08T11:58:33] DEBUG: new added screen pos: 257 161
[ UI ] [2017-08-08T11:58:34] DEBUG: Profile ID: 1211 name: default
[ UI ] [2017-08-08T11:58:34] DEBUG: current version is update to date
[ UI ] [2017-08-08T11:58:35] INFO: write configuration file complete
[Core] [2017-08-08T11:58:35] INFO: drag and drop enabled
[Core] [2017-08-08T11:58:35] DEBUG: opening configuration "C:/Users/pbaines/AppData/Local/Symless/Synergy/synergy.conf"
[Core] [2017-08-08T11:58:35] DEBUG: configuration read successfully
[Core] [2017-08-08T11:58:35] DEBUG: screen shape: 0,-1080 2777x2160 (multi-monitor)
[Core] [2017-08-08T11:58:35] DEBUG: window is 0x00060016
[Core] [2017-08-08T11:58:35] DEBUG: using desktop for drop target: C:\Users\pbaines\Desktop
[Core] [2017-08-08T11:58:35] DEBUG: adopting new buffer
[Core] [2017-08-08T11:58:35] DEBUG: opened display
[Core] [2017-08-08T11:58:35] DEBUG: active sides: 2
[Core] [2017-08-08T11:58:35] DEBUG: active sides: 2
[Core] [2017-08-08T11:58:35] DEBUG: desk Default window is 0x001209a6
[Core] [2017-08-08T11:58:35] DEBUG: switched to desk "Default"
[Core] [2017-08-08T11:58:35] DEBUG: desktop is now accessible
[Core] [2017-08-08T11:58:35] DEBUG: registered hotkey ScrollLock (id=ef14 mask=0000) as id=1
[Core] [2017-08-08T11:58:35] NOTE: started server, waiting for clients
[Core] [2017-08-08T11:58:35] DEBUG: event queue is ready
[Core] [2017-08-08T11:58:35] DEBUG: add pending events to buffer
[Core] [2017-08-08T11:58:35] DEBUG: screen "DESKTOP-3363NPM" shape changed
[ UI ] [2017-08-08T11:58:38] DEBUG: report to cloud: destId 2570 successfulIp  failedIp 25.62.77.158,192.168.0.38

 

 

Client (osx) endlessly repeats:

[ UI ] [2017-08-08T12:05:45] DEBUG: retry in 3 seconds
[ UI ] [2017-08-08T12:05:48] DEBUG: can not find any successful connectivity result for the server screen: 2569
[ UI ] [2017-08-08T12:05:48] DEBUG: retry in 3 seconds
[ UI ] [2017-08-08T12:05:51] DEBUG: can not find any successful connectivity result for the server screen: 2569
[ UI ] [2017-08-08T12:05:51] DEBUG: retry in 3 seconds



 

Just a bit more feedback, I had no idea how to get to the console as there is no way from the UI to know I had to press ` - I had to search the forum (maybe display some manual or quick start commands on the UI, or a help dropdown to drill into keyboard shortcuts). Once I got the console open it is extremely difficult to read (super large text can only see 5 lines at a time) and copy and paste was super frustrating, each time I dragged the lines I wanted, it refreshed losing the line I was trying to copy (maybe have a 'open in text editor' option?).

Share this post


Link to post
Share on other sites

This could be an issue related to the intermittent up time of our cloud server @pbaines. Most likely that the client is trying to connect to the server before the server had the change to reconfigure itself to adapt to the client's new computer name.

Please bear with us on this. We are still currently fixing these cloud server issues.

Share this post


Link to post
Share on other sites

Hmm, @Paul Suarez I don't see any 502 errors in the log, and the cloud server has had 100% uptime for the last 12 hours. This error seems to be the main issue...

[ UI ] [2017-08-09T09:01:13] DEBUG: can not find any successful connectivity result for the server screen: 2569
[ UI ] [2017-08-09T09:01:13] DEBUG: retry in 3 seconds
[ UI ] [2017-08-09T09:01:16] DEBUG: can not find any successful connectivity result for the server screen: 2569
[ UI ] [2017-08-09T09:01:16] DEBUG: retry in 3 seconds

The issue is that the client simply can't connect to the server (the logs show that the server is online). This is usually because of a firewall issue, or because it's trying to connect to an outdated IP address. Try temporarily disabling your firewalls, and restarting Synergy on both computers.

Share this post


Link to post
Share on other sites

There are no firewalls on either side.

The server has two interfaces, one is on the 192.x.x.x range and the other on 10.x.x.x the client only one interface to the 192.x.x.x subnet (as well as the internet). I am assuming that synergy2 doesn't listen on all interfaces so the server was only listening on the 10.x.x.x and the client was trying to connect to 192.x.x.x but as I couldn't find any config options / debug information I couldn't go any further.

 

If it helps you debug, this is what I need to achieve (which works fine in 1.8);

Server (windows) listens on 192.168.0.1 and 10.15.20.1

Client A (osx) connects to 192.168.0.1

Client B (debian) connects to 10.15.20.1

 

 

I've had to revert to 1.8 for the time being, I will try again on the next beta release if this is something you plan to address.

Edited by pbaines

Share this post


Link to post
Share on other sites

@Nick Bolton, this is what I think is something interesting in the logs. I checked with @Andrew Nelless and he agreed about it.

[Core] [2017-08-08T11:56:09] DEBUG: desktop is now accessible
[Core] [2017-08-08T11:56:09] DEBUG: registered hotkey ScrollLock (id=ef14 mask=0000) as id=1
[Core] [2017-08-08T11:56:09] NOTE: started server, waiting for clients
[Core] [2017-08-08T11:56:09] DEBUG: event queue is ready
[Core] [2017-08-08T11:56:09] DEBUG: add pending events to buffer
[Core] [2017-08-08T11:56:09] DEBUG: screen "DESKTOP-3363NPM" shape changed
[ UI ] [2017-08-08T11:56:12] DEBUG: report to cloud: destId 2570 successfulIp  failedIp 25.62.77.158,192.168.0.38
[Core] [2017-08-08T11:56:12] NOTE: accepted client connection
[Core] [2017-08-08T11:56:13] DEBUG: received client "pbdev" info shape=0,0 1920x1080 at 960,540
[Core] [2017-08-08T11:56:13] NOTE: disconnecting client "pbdev"
[Core] [2017-08-08T11:56:13] DEBUG: active sides: 2
[ UI ] [2017-08-08T11:56:13] ERROR: [2017-08-08T11:56:13] WARNING: unrecognised client name "pbdev", check server config
[Core] [2017-08-08T11:56:13] NOTE: client "pbdev" has disconnected
[Core] [2017-08-08T11:56:14] NOTE: accepted client connection
[Core] [2017-08-08T11:56:14] DEBUG: received client "pbdev" info shape=0,0 1920x1080 at 960,540
[ UI ] [2017-08-08T11:56:14] ERROR: [2017-08-08T11:56:14] WARNING: unrecognised client name "pbdev", check server config
[Core] [2017-08-08T11:56:14] NOTE: disconnecting client "pbdev"
[Core] [2017-08-08T11:56:14] DEBUG: active sides: 2
[Core] [2017-08-08T11:56:14] NOTE: client "pbdev" has disconnected

Although, our servers are working fine now. Can you try to check on it now @pbaines?

Share this post


Link to post
Share on other sites

Interesting, pbdev is 'Client B' in my previous post, i.e. it is one on the 10.x range, it is still on synergy1 so I would expect it to fail but this is more evidence that Synergy2 is not listening on the 192.x range as it is not complaining about 'Client A'

Can you see in the logs what IP and ports it is bound to ?

Synergy1 was fine at bridiging the networks, is this something that should not yet be possible in synergy2 ?

Edited by pbaines

Share this post


Link to post
Share on other sites
31 minutes ago, pbaines said:

it is still on synergy1

Please install Synergy 2 on both computers. Synergy 2 is not compatible with Synergy 1.

Share this post


Link to post
Share on other sites

Hi Nick,

You've misunderstood me, let me try to clear it up,  I have 3 computers

Windows (Server)

Macbook (Client A)

Ubuntu (Client B)

 

1.8 works fine on all 3.

 

I have installed Synergy 2 on the Windows and Macbook, Synergy won't connect to each other.

 

The Ubuntu machine (pbdev) is still trying to connect to the Windows machine, but that is just background noise, I don't expect this to work, that is just a red herring that Paul spotted in the logs.

 

The problem seems to be that Synergy on the Windows machine has decided to bind to the 10.x address, which the Macbook cannot see - instead I want Synergy on the Windows machine to listen on the 192. address which the Macbook can see.

Share this post


Link to post
Share on other sites

Hmm... you understand that you need Synergy 2 installed on all 3 computers. Right?

Share this post


Link to post
Share on other sites

I just want to get Synergy working between the Windows and Macbook - I installed Synergy 2 on both, it doesn't work - I've given you my best guess why several times. 

 

 

Share this post


Link to post
Share on other sites

Could you try temporarily disabling your firewalls?

Share this post


Link to post
Share on other sites

Hey, sorry. I'm on the phone to @Andrew Nelless trying to solve this. The server will be listening on both the 10.x.x.x IP and the 192.x.x.x IP. It's tricky to see what's happening because the logs are truncated to 1000 lines. It looks like you left it running over night.

Could you uninstall Synergy 1 and reinstall Synergy 2 on all 3 machines. Then start Synergy 2 at more or less the same time on all computers, then upload the logs within 5-10 seconds of opening Synergy. Please clearly indicate which logs are for which computers.

Share this post


Link to post
Share on other sites

Thanks Nick, forget about the 3rd machine (Client B) I should never of mentioned it, it just popped up in the logs so I thought I'd explain why.

I am solely trying to get synergy2 working between the Server (windows) and Client A (osx), however I may not get a chance to get you the logs you've requested until Tuesday.

Share this post


Link to post
Share on other sites

Got it! Make sure you let me know which log is for the server and which is for the client.

Share this post


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