|
This is a question I'm carrying over from a previous support forum. I apologize for the duplication, but I've not been able to resolve the issue and I really miss Synergy. I have a Win7/64 host and a Win7/64 client on a wireless router. I realize that this isn't ideal, but it worked great for years before suddenly failing not long after the upgrade to 1.4.2. I had the beta working beautifully for one session, with no signification lag even on a CentOS vm on the client. Then it wouldn't connect. The client shows 'Connected to XXXX-PC', and the host shows 'Waiting for clients'. I had run through some ping checks in the old support thread, but I can't recall exactly what they were. They seemed to indicate properly open channels. I've attempted to use IP addresses rather than client names, I've tried adding entries in my hosts file, and I've looked into Windows firewall settings, all with no success. Thanks in advance for any ideas.
showing 5 of 8
show 3 more comments
|
The question has been closed for the following reason "Your version is out of date, please upgrade" by nbolton 19 Jul '12, 14:32
|
Hi, I had this exact problem using two Windows 7 PCs. I have since resolved it by uninstalling the autostart function on the server - it was installed to autostart on startup, haven't tried it on login yet, may try that later and see what happens... Hope this helps! |
I have a similar problem with my setup. It was working the first time I connected, and now when I try, the client connects without issue, but the server side doesn't seam to detect it.
There are no errors in the log files and I can ping from both pcs. I hope someone comes up with a solution to this issue.
Check your process list, are you running multiple server instances? Perhaps in different window sessions.
No, I've tried starting Synergy after reboot and have checked the process list. Thanks.
I just tried again, and when I checked my log file on the server it has the following...
I spent a bunch more time on this today, pinging both ways, checking Windows firewall settings, editing host files...
...then I switched to Input Director. I had it up and running well in 3 minutes.
I like Synergy better for it's ability to shift screens vertically, and the new interface is good. Alas, if it doesn't work....
I have this exact same issue, host having windows 7, client having WinXpPro. Client connects, host is looking for clients. Input connector worked like a charm.
This is not an answer.