swaziloo

Connectivity Issues Linux (Debian) <-> Windows 10 Corp Network

9 posts in this topic

This can easily be firewall-related, though for a while yesterday it was working perfectly, somehow.

Linux log:

[ UI ] [2017-08-08T12:51:08] DEBUG: new added screen pos: 257 161
[ UI ] [2017-08-08T12:51:08] ERROR: Reply status code: 502
[ UI ] [2017-08-08T12:51:08] ERROR: Reply status code: 502
[ UI ] [2017-08-08T12:51:08] ERROR: exception caught: failed to check update: Error transferring https://v1.api.cloud.symless.com/update - server replied: Bad Gateway
[ UI ] [2017-08-08T13:01:06] INFO: log filename: /home/......../.config/Symless/Synergy/synergy.log
[ UI ] [2017-08-08T13:01:06] DEBUG: new added screen pos: 257 161
[ UI ] [2017-08-08T13:01:06] DEBUG: Profile ID: 1203 name: default
[ UI ] [2017-08-08T13:01:06] DEBUG: current version is update to date
[ UI ] [2017-08-08T13:01:07] INFO: write configuration file complete
[ UI ] [2017-08-08T13:01:07] DEBUG: can not find any successful connectivity result for the server screen: 2553
[ UI ] [2017-08-08T13:01:07] DEBUG: retry in 3 seconds
[ UI ] [2017-08-08T13:01:10] DEBUG: can not find any successful connectivity result for the server screen: 2553
[ UI ] [2017-08-08T13:01:10] DEBUG: retry in 3 seconds
[ UI ] [2017-08-08T13:01:13] DEBUG: can not find any successful connectivity result for the server screen: 2553 
[ UI ] [2017-08-08T13:01:13] DEBUG: retry in 3 seconds
[ UI ] [2017-08-08T13:01:16] DEBUG: can not find any successful connectivity result for the server screen: 2553 
[ UI ] [2017-08-08T13:01:16] DEBUG: retry in 3 seconds
[ UI ] [2017-08-08T13:01:17] DEBUG: report to cloud: destId 2553 successfulIp  failedIp 10.53.213.65,172.16.6.62,172.16.6.64
[ UI ] [2017-08-08T13:01:19] DEBUG: can not find any successful connectivity result for the server screen: 2553 
[ UI ] [2017-08-08T13:01:19] DEBUG: retry in 3 seconds
[ UI ] [2017-08-08T13:01:22] DEBUG: can not find any successful connectivity result for the server screen: 2553 
[ UI ] [2017-08-08T13:01:22] DEBUG: retry in 3 seconds
[ UI ] [2017-08-08T13:01:25] DEBUG: can not find any successful connectivity result for the server screen: 2553 
[ UI ] [2017-08-08T13:01:25] DEBUG: retry in 3 seconds
[ UI ] [2017-08-08T13:01:28] DEBUG: can not find any successful connectivity result for the server screen: 2553 
[ UI ] [2017-08-08T13:01:28] DEBUG: retry in 3 seconds
[ UI ] [2017-08-08T13:01:31] DEBUG: can not find any successful connectivity result for the server screen: 2553 
[ UI ] [2017-08-08T13:01:31] DEBUG: retry in 3 seconds
[ UI ] [2017-08-08T13:01:34] DEBUG: can not find any successful connectivity result for the server screen: 2553 
[ UI ] [2017-08-08T13:01:34] DEBUG: retry in 3 seconds
....

Windows log:

[ UI ] [2017-08-08T13:01:12] INFO: log filename: C:/Users/........./AppData/Local/Symless/Synergy/synergy.log
[ UI ] [2017-08-08T13:01:13] DEBUG: new added screen pos: 257 161 
[ UI ] [2017-08-08T13:01:13] DEBUG: current version is update to date
[ UI ] [2017-08-08T13:01:13] DEBUG: Profile ID: 1203 name: default
[ UI ] [2017-08-08T13:01:14] INFO: write configuration file complete
[Core] [2017-08-08T13:01:14] INFO: drag and drop enabled
[Core] [2017-08-08T13:01:14] DEBUG: opening configuration "C:/Users/........./AppData/Local/Symless/Synergy/synergy.conf"
[Core] [2017-08-08T13:01:14] DEBUG: configuration read successfully
[Core] [2017-08-08T13:01:14] DEBUG: screen shape: 0,0 3200x1800 
[Core] [2017-08-08T13:01:14] DEBUG: window is 0x000b07e6
[Core] [2017-08-08T13:01:14] DEBUG: using desktop for drop target: C:\Users\.........\Desktop
[Core] [2017-08-08T13:01:14] DEBUG: adopting new buffer
[Core] [2017-08-08T13:01:14] DEBUG: opened display
[Core] [2017-08-08T13:01:14] DEBUG: active sides: 2
[Core] [2017-08-08T13:01:14] DEBUG: active sides: 2
[Core] [2017-08-08T13:01:14] DEBUG: desk Default window is 0x000608ac
[Core] [2017-08-08T13:01:14] DEBUG: switched to desk "Default"
[Core] [2017-08-08T13:01:14] DEBUG: desktop is now accessible
[Core] [2017-08-08T13:01:14] NOTE: started server, waiting for clients
[Core] [2017-08-08T13:01:14] DEBUG: event queue is ready
[Core] [2017-08-08T13:01:14] DEBUG: add pending events to buffer
[Core] [2017-08-08T13:01:14] DEBUG: screen "cacsvwl-18013" shape changed
[ UI ] [2017-08-08T13:01:14] ERROR: [2017-08-08T13:01:14] WARNING: failed to register hotkey ScrollLock (id=ef14 mask=0000)
[ UI ] [2017-08-08T13:01:17] DEBUG: report to cloud: destId 2552 successfulIp  failedIp 172.16.6.60,172.17.0.1,172.18.0.1,172.19.0.1,172.20.0.1,172.21.0.1,172.22.0.1,172.23.0.1,172.24.0.1,172.25.0.1,172.26.0.1,172.27.0.1
[Core] [2017-08-08T13:01:45] DEBUG: clipboard chain: new next: 0x00000000
[ UI ] [2017-08-08T13:04:12] ERROR: Reply status code: 504
[ UI ] [2017-08-08T13:04:13] ERROR: Reply status code: 504 
[ UI ] [2017-08-08T13:04:14] ERROR: Reply status code: 504 
...

 

Share this post


Link to post
Share on other sites

It appears that an update/reboot on the Windows 10 side at least somewhat fixed things. I don't see a way to delete this post, but please feel free to remove it.

Thanks.

Share this post


Link to post
Share on other sites

Just FYI, I use Linux, Kubuntu, Synergy Beta found and self configured promptly. 

Share this post


Link to post
Share on other sites

Further poking around, I think it might be that it's unable to connect when a VPN is active on the Windows 10 machine.

Share this post


Link to post
Share on other sites
51 minutes ago, swaziloo said:

Further poking around, I think it might be that it's unable to connect when a VPN is active on the Windows 10 machine.

That's if the VPN itself won't allow communication with local machines/computers.

Share this post


Link to post
Share on other sites

Yes, this definitely appears to be the issue. Worse yet, after disconnecting from the VPN, it's still not able to (re)connect. Only after a "clean" boot does it work once more.

Guess I need to look into a hardware switch

=(

Share this post


Link to post
Share on other sites
10 hours ago, swaziloo said:

Guess I need to look into a hardware switch

 

Sad times :(

10 hours ago, swaziloo said:

Worse yet, after disconnecting from the VPN, it's still not able to (re)connect.

Try restarting Synergy after disconnecting from VPN (maybe it's trying to connect via an outdated IP).

The good news is that we're planning to implement Cloud Bridge in version 2.1 which should solve your problem.

Share this post


Link to post
Share on other sites
8 hours ago, Nick Bolton said:

The good news is that we're planning to implement Cloud Bridge in version 2.1 which should solve your problem.

I'll definitely keep an ear out for this! It's also possible that the corporate overlords roll our local network into the borg, which likely solves (multiple) problems.

Share this post


Link to post
Share on other sites
14 hours ago, swaziloo said:

It's also possible that the corporate overlords roll our local network into the borg

Resistance is futile.

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