RTHNWI

Failed to connect to server: Connection was refused

5 posts in this topic

Setup:

Server - macOS 10.12.5 running Synergy 1.8.8-stable-25a8cb2
Client - Win10 Enterprise, 64-bit running Synergy 1.8.8-stable-25a8cb2
Connecting via WiFi, Authentication via EAP-TLS

Issue:

Can't connect my Win10 PC Client to my macOS Sierra Server. Keep getting error message "failed to connect to server: Connection was refused." 

I set up my server as stated in the Getting Started Guide.

I don't know what to do next to correct the issue. Any assistance would be greatly appreciated. 

 

Screen Shot 2017-06-14 at 10.01.42 AM.png

Screen Shot 2017-06-14 at 9.57.02 AM.png

Unknown.jpeg

Share this post


Link to post
Share on other sites

Have you tried pinging the other machine from the other one?

  • Like 1

Share this post


Link to post
Share on other sites

Hi Paul!

Thanks for replying!

Ping results from PC:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minium = 11ms, Maximum = 146, Average = 84ms

Ping results from macOS:
PING 169.254.140.17 (169.254.140.17): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8

--- 169.254.140.17 ping statistics ---
10 packets transmitted, 0 packets received, 100.0% packet loss

 

I'm a decent power user of computers but the hard core stuff like command line and networking I have no clue. I couldn't tell you what this means. Does it mean that my Mac isn't talking to my PC?

Edited by RTHNWI

Share this post


Link to post
Share on other sites

AH-HA!

Accept incoming connections! I set up a VPN to make this work on the WiFi network!

Figured it out and it's working great! Thanks Paul for guiding me on the right path to figure this out!

Share this post


Link to post
Share on other sites
39 minutes ago, RTHNWI said:

AH-HA!

Accept incoming connections! I set up a VPN to make this work on the WiFi network!

Figured it out and it's working great! Thanks Paul for guiding me on the right path to figure this out!

You're welcome @RTHNWI;) Thanks for the update too. I just want to add something though.I guess the main reason why it didn't work before is that, it tries to connect to an invalid IP address (169.254.x.x). And if your machine uses an IP that starts with 169.254.x.x on that time, basically it's not really connected to the network. :)

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