|
Info: I have the server running on a Windows XP 32-bit machine, and a single client running on a Redhat 64-bit machine. Both machines are running version 1.3.1 of Synergy because of a dependency issue for GLIBC++. The problem is, synergyc is constantly dropping the connection to the server. The process is not crashing, because it has the same PID. However, when I run netstat, I can see that it opens a new local port to connect to the server after each disconnect. I don't think the server is dropping the connection, because when I run a 3rd party tool, CurrPorts, it supplies the time stamp of when the port (24800) was first opened. That time doesn't change unless I kill the server. I've also noticed that once a connection is dropped, a new port will be opened on the Redhat (client) side. It takes several minutes for the old port to be closed. After several "connect and then the connection drops" scenarios, I'm left with several open ports to the server:24800 in the state of TIME_WAIT. Any suggestions??
showing 5 of 7
show all
|
|
Can't say which is loosing connection first, but that doesn't really make much difference. Your problem sounds like a network issue. I would let your IT department/person know, so they can trace the problem. It may be network hardware, or you may have a machine on your network that is generating excessive network traffic. |
Could you please include a copy of your log file?
Sorry for having to copy/paste here - I don't have a server to link to currently.
Client Log
Server log (Windows)
Are these machines on the same subnet? Are either of them running on wireless?
I'm fairly certain they're both on the same subnet - They both have the same subnet mask (255.255.252.0)? Neither computer is using a wireless connection.
My only recommendation at this point would be to try to resolve whatever dependency issue you have, and load the latest version.
Some days, like today, it's acting perfectly fine. My guess would be that it's probably unrelated to the software, and instead a problem with the network traffic. I have spoken with others within my company that use Synergy and they do not have this problem. The communication is over TCP, so the transfer of the packets should be guaranteed for as long as the connection remains open on both ends. Could you or anyone else provide any thoughts on what could disrupt the communication between the client and server?
Also one other question - Based on the log output I provided, which entity do you think is closing the connection first? The server? I could look into the code for myself, but maybe you know based on that output.
Thanks for the input!
Cheap Network Routers and Switches can plague a network with "Ghost problems". But hey, you get what you pay for. My suggestion is to monitor it and log it, if a router, or switch reboot fixes the problem then you've narrowed it down, pat yourself on the back and pick up a cisco 2950 on ebay for $20-30.
Krazy2K