On 06/03/2014 05:43 AM, Liam Proven issued this missive:
On 3 June 2014 00:02, Rick Stevens wrote:
If you don't specify the server's IP address to the client, then the
client will probably be trying to connect over the OTHER network, and
no, that won't work.
Success!
It was the firewall in
On 3 June 2014 00:02, Rick Stevens wrote:
> If you don't specify the server's IP address to the client, then the
> client will probably be trying to connect over the OTHER network, and
> no, that won't work.
Success!
It was the firewall in the end; Synergy's error message is misleading.
It says
On 3 June 2014 00:02, Rick Stevens wrote:
I checked on the server; nothing was listening. Ran Synergy, then it
was listening.
> synergyc -d ERROR 192.168.v.w
This seems to fail silently.
When I run the desktop client interactively, I get:
NOTE: starting client
NOTE: config file: /tm
On 06/02/2014 02:13 PM, Liam Proven issued this missive:
On 2 June 2014 19:04, Rick Stevens wrote:
Ok, the machines MUST be able to ping each other. If they can't, you
need to get that sorted first. If they have funky network configs, you
should try to ping via IP addresses instead of host name
On 2 June 2014 19:04, Rick Stevens wrote:
> Ok, the machines MUST be able to ping each other. If they can't, you
> need to get that sorted first. If they have funky network configs, you
> should try to ping via IP addresses instead of host names and see if
> that works and you may have to add some
On 06/02/2014 08:57 AM, Liam Proven issued this missive:
On 30 May 2014 19:56, Rick Stevens wrote:
Hope that helps.
Thanks very much for the exhaustive reply!
Sadly not. I suspect it might be something to do with the odd network
configuration at $JOB; my machines both have 2 different IP add
On 30 May 2014 19:56, Rick Stevens wrote:
> Hope that helps.
Thanks very much for the exhaustive reply!
Sadly not. I suspect it might be something to do with the odd network
configuration at $JOB; my machines both have 2 different IP addresses
on 2 different subnets.
I've tried both IPs, althou
On 05/30/2014 10:16 AM, Liam Proven issued this missive:
On 30 May 2014 18:44, Rick Stevens wrote:
I use synergy all the time between F19 and F20 machines (the console is
currently on an F19 box).
On the F20 box (XFCE), right-click on the firewall icon and edit the
current zone (I'm using "Pub
On 30 May 2014 18:44, Rick Stevens wrote:
> I use synergy all the time between F19 and F20 machines (the console is
> currently on an F19 box).
>
> On the F20 box (XFCE), right-click on the firewall icon and edit the
> current zone (I'm using "Public"). Click on the "Ports" tab, then click
> the "
On 05/30/2014 07:47 AM, Liam Proven issued this missive:
Has anyone successfully got this working between two Fedora 20 machines?
The app says that the default port -- 24800 -- is not available. I
don't know why, I can't see anything taking it in the firewall or
anything, but anyway, changing to
Has anyone successfully got this working between two Fedora 20 machines?
The app says that the default port -- 24800 -- is not available. I
don't know why, I can't see anything taking it in the firewall or
anything, but anyway, changing to different ports doesn't seem to
help... the client and ser
11 matches
Mail list logo
