djashdj

Win10Pro - MacOS 10.14.5 - No connection either way over wifi

5 posts in this topic

Posted (edited)

Hello!  

I've tried a few things here and read several other posts with similar subjects.  Those were all fixed primarily by making sure machines were on same subnet. 

Using Synergy 1.10.2 
Win10Pro  IP: 172.16.30.187
MacOS 10.14.5  IP: 172.16.30.199

---
Tried Server mode on Windows and on Mac.  Have no results either way.  Both machines are on the same subnet, Turned off all firewall rules on Win10Pro and Turned them on and made sure the synergy ones were configured.  All looks good.  Same results.  The windows machine does show some additional external IP's but they aren't active.  Only one IP on the mac.  

 

Here are the debug logs with Windows as a server and mac as client. Mac IP is 172.16.30.199. These are connected to a ubiquiti wireless access point and getting dhcp from that device. No Domain or anything but they are on different work groups if that matters. At first I thought this was a firewall issue with windows. After verifying the rules, and then disabling all firewall features and having no different results. I then reversed the connection with windows as client and Mac as Server. Same exact errors just from different sides. (and different ip listed)

I feel like it's a communication thing perhaps.  Something on the AP maybe?  Any assistance is helpful, Thank you! 

 

From Windows with windows as Server: 

[2019-06-11T09:04:27] INFO: connecting to service...

[2019-06-11T09:04:29] INFO: connection established

[2019-06-11T09:04:18] DEBUG: ipc disconnect, closing stream

[2019-06-11T09:04:18] DEBUG: ipc client disconnected

[2019-06-11T09:04:18] DEBUG: ipc client proxy removed, connected=1

[2019-06-11T09:04:18] INFO: process started but command is empty, shutting down

[2019-06-11T09:04:18] DEBUG: start ipc handle data

[2019-06-11T09:04:18] DEBUG: ipc read: ISDN

[2019-06-11T09:04:18] DEBUG: finished ipc handle data

[2019-06-11T09:04:18] INFO: got ipc shutdown message

[2019-06-11T09:04:18] DEBUG: event queue is ready

[2019-06-11T09:04:18] DEBUG: unregistered hotkey id=1

[2019-06-11T09:04:18] DEBUG: adopting new buffer

[2019-06-11T09:04:18] DEBUG: discarding 1 event(s)

[2019-06-11T09:04:18] DEBUG: closed display

[2019-06-11T09:04:18] DEBUG: ipc disconnect, closing stream

[2019-06-11T09:04:18] NOTE: stopped server

[2019-06-11T09:04:18] DEBUG: ipc disconnect, closing stream

[2019-06-11T09:04:18] DEBUG: ipc client disconnected

[2019-06-11T09:04:18] DEBUG: ipc client proxy removed, connected=0

[2019-06-11T09:04:19] DEBUG: process 13536 was shutdown gracefully

[2019-06-11T09:04:28] DEBUG: accepted ipc client connection

[2019-06-11T09:04:29] DEBUG: start ipc handle data

[2019-06-11T09:04:29] DEBUG: ipc read: IHEL

[2019-06-11T09:04:29] DEBUG: finished ipc handle data

[2019-06-11T09:04:29] DEBUG: ipc hello, type=gui

[2019-06-11T09:04:29] INFO: service status: idle

 

---Logs from Client (mac)

[2019-06-11T09:08:35] DEBUG: starting process

[2019-06-11T09:08:35] INFO: starting client

[2019-06-11T09:08:35] INFO: config file: /var/folders/tc/wjhskbd96jg8wk7jsjg_bsb40000gn/T/Synergy.L21276

[2019-06-11T09:08:35] INFO: log level: DEBUG

[2019-06-11T09:08:35] INFO: drag and drop enabled

[2019-06-11T09:08:35] DEBUG: screen shape: center=0,0 size=1280x800 on 1 display

[2019-06-11T09:08:35] DEBUG: starting watchSystemPowerThread

[2019-06-11T09:08:35] DEBUG: adopting new buffer

[2019-06-11T09:08:35] DEBUG: opened display

[2019-06-11T09:08:35] DEBUG: started watchSystemPowerThread

[2019-06-11T09:08:35] DEBUG: waiting for event loop

[2019-06-11T09:08:35] NOTE: started client

[2019-06-11T09:08:35] NOTE: connecting to '172.16.30.187': 172.16.30.187:24800

[2019-06-11T09:08:35] DEBUG: openssl version: OpenSSL 1.0.2o 27 Mar 2018

[2019-06-11T09:08:35] DEBUG: waiting for carbon loop

[2019-06-11T09:08:35] DEBUG: event queue is ready

[2019-06-11T09:08:35] DEBUG: add pending events to buffer

[2019-06-11T09:08:35] DEBUG: signalling carbon loop ready

[2019-06-11T09:08:35] DEBUG: starting carbon loop

[2019-06-11T09:08:35] DEBUG: carbon loop ready

2019-06-11 09:08:35.866 synergyc[21297:2863711] starting cocoa loop

[2019-06-11T09:08:51] WARNING: failed to connect to server: Timed out

[2019-06-11T09:08:51] DEBUG: retry in 1 seconds

[2019-06-11T09:08:52] NOTE: connecting to '172.16.30.187': 172.16.30.187:24800

[2019-06-11T09:08:52] DEBUG: openssl version: OpenSSL 1.0.2o 27 Mar 2018

[2019-06-11T09:08:53] WARNING: failed to connect to server: cannot connect socket: Host is down

[2019-06-11T09:08:53] DEBUG: retry in 1 seconds

----repeats retry and warning failure from here---

 

Edited by djashdj
added IP's

Share this post


Link to post
Share on other sites

Should also be noted, I can not ping either computer in either direction.   

Share this post


Link to post
Share on other sites

If neither device can't ping either other you may have a network problem. Or there are filtering rules occurring in the network that blocks certain types of traffic.

Try running a tracert to google or 1.1.1.1 and see if any device responds to the ping in the local network.

It should look something like this

PS C:\Users\Jamie> tracert 1.1.1.1

Tracing route to one.one.one.one [1.1.1.1]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.3.1
  2    <1 ms    <1 ms    <1 ms  192.168.1.1
  3    35 ms     6 ms     6 ms  195.xxx.xxx.xxx
  4     6 ms     6 ms     6 ms  195.xxx.xxx.xxx
  5    14 ms    15 ms    15 ms  195.xxx.xxx.xxx
  6    22 ms    23 ms    25 ms  ##.####.### [80.xxx.xxx.xxx]
  7    22 ms    21 ms    21 ms  one.one.one.one [1.1.1.1]

Except for you the first few hops should be in the 172.xxx.xxx.xxx range 

Share this post


Link to post
Share on other sites

Yeah I think something is going on at the AP level.  I'll h ave to take a look tonight and report findings back here.  

The tracert results are normal and good.  5 hops to 1.1.1.1 with one 27ms ping in the middle everything else under 10ms.  

Thanks for your help!

Share this post


Link to post
Share on other sites

Check if you have an option called Client Isolation in your router, and make sure it's disabled.

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