| 1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
|
|---|
| 2 | <html>
|
|---|
| 3 | <head>
|
|---|
| 4 | <meta HTTP-EQUIV="Content-Type" CONTENT="text/html;CHARSET=iso-8859-1">
|
|---|
| 5 | <meta name="keywords" content="Virtual Screen, Open Source, Software" />
|
|---|
| 6 | <meta name="description" content="Mouse and Keyboard Sharing" />
|
|---|
| 7 | <link rel="stylesheet" type="text/css" href="synergy.css" media="screen" />
|
|---|
| 8 | <title>Synergy Troubleshooting</title>
|
|---|
| 9 | </head>
|
|---|
| 10 | <body class="main">
|
|---|
| 11 | <p> </p>
|
|---|
| 12 | <h3>Synergy Troubleshooting</h3>
|
|---|
| 13 | <h4>Problems</h4>
|
|---|
| 14 | <ol>
|
|---|
| 15 | <li><a href="#problem1">Cannot read configuration</a>
|
|---|
| 16 | <li><a href="#problem2">Connection forcefully rejected</a>
|
|---|
| 17 | <li><a href="#problem3">Connection timed out</a>
|
|---|
| 18 | <li><a href="#problem4">Cannot listen for clients</a>
|
|---|
| 19 | <li><a href="#problem5">Unknown screen name "XXX"</a>
|
|---|
| 20 | <li><a href="#problem6">Server refused client with name "XXX"</a>
|
|---|
| 21 | <br><a href="#problem6">A client with name "XXX" is not in the map</a>
|
|---|
| 22 | <li><a href="#problem7">Server already has a connected client with name "XXX"</a>
|
|---|
| 23 | <br><a href="#problem7">A client with name "XXX" is already connected</a>
|
|---|
| 24 | <li><a href="#problem8">Server has incompatible version</a>
|
|---|
| 25 | <li><a href="#problem9">The cursor goes to secondary screen but won't come back</a>
|
|---|
| 26 | </ol>
|
|---|
| 27 | <h4>Solutions</h4>
|
|---|
| 28 | <ol>
|
|---|
| 29 | <li><a name="problem1"></a><span class="fakelink">Cannot read configuration</span>
|
|---|
| 30 | <p>
|
|---|
| 31 | There's an error in the configuration file. This error is always
|
|---|
| 32 | accompanied by another message describing the problem. Use that
|
|---|
| 33 | message and the <a href="configuration.html">configuration documentation</a>
|
|---|
| 34 | to determine the fix.
|
|---|
| 35 | </p>
|
|---|
| 36 | <li><a name="problem2"></a><span class="fakelink">Connection forcefully rejected</span>
|
|---|
| 37 | <p>
|
|---|
| 38 | The client was able to contact the server computer but the server was
|
|---|
| 39 | not listening for clients. Possible reasons are:
|
|---|
| 40 | </p>
|
|---|
| 41 | <ul>
|
|---|
| 42 | <li>The client is using the wrong server
|
|---|
| 43 | <p>
|
|---|
| 44 | Make sure the client is using the hostname or IP address of the computer
|
|---|
| 45 | running the synergy server.
|
|---|
| 46 | </p>
|
|---|
| 47 | <li>Synergy isn't running on the server
|
|---|
| 48 | <p>
|
|---|
| 49 | Make sure the synergy server is running on the server computer. Make
|
|---|
| 50 | sure the server is ready to accept connections. If another program is
|
|---|
| 51 | using synergy's port (24800 by default) then synergy can't start unless
|
|---|
| 52 | you specify a different port.
|
|---|
| 53 | </p>
|
|---|
| 54 | <li>The client is using the wrong port
|
|---|
| 55 | <p>
|
|---|
| 56 | Synergy uses port 24800 by default but you can specify a different port.
|
|---|
| 57 | If you do use a different port you must use that port on the server and
|
|---|
| 58 | all clients.
|
|---|
| 59 | </p>
|
|---|
| 60 | </ul>
|
|---|
| 61 | <li><a name="problem3"></a><span class="fakelink">Connection timed out</span>
|
|---|
| 62 | <p>
|
|---|
| 63 | The most likely reasons for this are:
|
|---|
| 64 | </p>
|
|---|
| 65 | <ul>
|
|---|
| 66 | <li>A firewall
|
|---|
| 67 | <p>
|
|---|
| 68 | A firewall is a program or device that deliberately blocks network
|
|---|
| 69 | connections for security reasons. Typically, they'll silently drop
|
|---|
| 70 | packets they don't want rather than sending a rejection to the sender.
|
|---|
| 71 | This makes it more difficult for intruders to break in.
|
|---|
| 72 | </p><p>
|
|---|
| 73 | When synergy traffic hits a firewall and gets dropped, eventually the
|
|---|
| 74 | synergy client will give up waiting for a response and time out. To
|
|---|
| 75 | allow synergy traffic through first find all the firewalls on the
|
|---|
| 76 | network between and on the synergy client and server computers.
|
|---|
| 77 | </p><p>
|
|---|
| 78 | A firewall on the server or any network device between the server and
|
|---|
| 79 | any client should allow packets to TCP port 24800. (Port 24800 is the
|
|---|
| 80 | default; use whichever port you've selected.) You'll have to consult
|
|---|
| 81 | the manual for your operating system, device, or firewall software to
|
|---|
| 82 | find out how to do this.
|
|---|
| 83 | </p><p>
|
|---|
| 84 | Usually you'll won't need to adjust a firewall on client machines.
|
|---|
| 85 | That's because firewalls normally allow incoming traffic on any port
|
|---|
| 86 | they've initiated a connection on. The reasoning is, of course, if
|
|---|
| 87 | you started a conversation you probably want to hear the reply.
|
|---|
| 88 | </p>
|
|---|
| 89 | <li>The network is down or busy
|
|---|
| 90 | <p>
|
|---|
| 91 | Correct the network problem and try again. You might try
|
|---|
| 92 | <span class="code">ping</span> to see if the two computers can see
|
|---|
| 93 | each other on the network.
|
|---|
| 94 | </p>
|
|---|
| 95 | <li>The server is frozen
|
|---|
| 96 | <p>
|
|---|
| 97 | If the synergy server is running but locked up or very busy then the
|
|---|
| 98 | client may get this message. If the server is locked up then you'll
|
|---|
| 99 | probably have to restart it. If it's just very busy then the client
|
|---|
| 100 | should successfully connect automatically once the server settles down.
|
|---|
| 101 | </p>
|
|---|
| 102 | </ul>
|
|---|
| 103 | <li><a name="problem4"></a><span class="fakelink">Cannot listen for clients</span>
|
|---|
| 104 | <p>
|
|---|
| 105 | Synergy tried to start listening for clients but the network port is
|
|---|
| 106 | unavailable for some reason. Typical reasons are:
|
|---|
| 107 | </p>
|
|---|
| 108 | <ul>
|
|---|
| 109 | <li>No network devices
|
|---|
| 110 | <p>
|
|---|
| 111 | You must have a TCP/IP network device installed and enabled to use
|
|---|
| 112 | synergy.
|
|---|
| 113 | </p>
|
|---|
| 114 | <li>A synergy server is already running
|
|---|
| 115 | <p>
|
|---|
| 116 | Check that a synergy server isn't already running.
|
|---|
| 117 | </p>
|
|---|
| 118 | <li>Another program is using synergy's port
|
|---|
| 119 | <p>
|
|---|
| 120 | Only one program at a time can listen for connections on a given port.
|
|---|
| 121 | If the specific error is that the address is already in use and you've
|
|---|
| 122 | ruled out the other causes, then it's likely another program is already
|
|---|
| 123 | using synergy's port. By default synergy uses port 24800. Try having
|
|---|
| 124 | synergy use a different port number, like 24801 or 24900. Note that
|
|---|
| 125 | the server and all clients must use the same port number. Alternatively,
|
|---|
| 126 | find the other program and stop it or have it use another port.
|
|---|
| 127 | </p>
|
|---|
| 128 | </ul>
|
|---|
| 129 | <li><a name="problem5"></a><span class="fakelink">Unknown screen name "XXX"</span>
|
|---|
| 130 | <p>
|
|---|
| 131 | This error can be reported when reading the configuration; see
|
|---|
| 132 | <a href="#problem1">cannot read configuration</a>. If the configuration
|
|---|
| 133 | was read successfully and you get this error then it means that the
|
|---|
| 134 | server's screen is not in the configuration. All screens must be listed
|
|---|
| 135 | in the configuration.
|
|---|
| 136 | </p><p>
|
|---|
| 137 | A common reason for this is when you haven't used the system's hostname
|
|---|
| 138 | as its screen name. By default, synergy uses the hostname as the screen
|
|---|
| 139 | name. If you used a different screen name in the configuration then you
|
|---|
| 140 | must tell synergy what that name is. Let's say the hostname is
|
|---|
| 141 | <span class="code">frederick</span> but the configuration defines a screen
|
|---|
| 142 | named <span class="code">fred</span>. Then you must tell the server
|
|---|
| 143 | that its screen name is <span class="code">fred</span> by using the
|
|---|
| 144 | <span class="code">--name fred</span> command line option or setting
|
|---|
| 145 | the screen name in the advanced options dialog to
|
|---|
| 146 | <span class="code">fred</span>.
|
|---|
| 147 | </p><p>
|
|---|
| 148 | Alternatively, you can specify one name as an alias of another. See
|
|---|
| 149 | the <a href="configuration.html#aliases">configuration documentation</a>
|
|---|
| 150 | for details.
|
|---|
| 151 | </p><p>
|
|---|
| 152 | Another common reason for this is a mismatch between what you think the
|
|---|
| 153 | hostname is and what synergy thinks it is. Typically this is a problem
|
|---|
| 154 | with fully qualified domain names (FQDN). Perhaps you think your system
|
|---|
| 155 | is named <span class="code">fred</span> but synergy thinks it's
|
|---|
| 156 | <span class="code">fred.nowhere.com</span> or
|
|---|
| 157 | <span class="code">fred.local</span>. You can use either solution above
|
|---|
| 158 | to fix this.
|
|---|
| 159 | </p>
|
|---|
| 160 | <li><a name="problem6"></a><span class="fakelink">Server refused client with name "XXX"</span>
|
|---|
| 161 | <br><span class="fakelink">A client with name "XXX" is not in the map</span>
|
|---|
| 162 | <p>
|
|---|
| 163 | The client is using a screen name not in the server's configuration.
|
|---|
| 164 | This is essentially the same problem as <a href="#problem5">Unknown
|
|---|
| 165 | screen name "XXX"</a> and has the same solutions: specify another
|
|---|
| 166 | screen name or add an alias.
|
|---|
| 167 | </p>
|
|---|
| 168 | <li><a name="problem7"></a><span class="fakelink">Server already has a connected client with name "XXX"</span>
|
|---|
| 169 | <br><span class="fakelink">A client with name "XXX" is already connected</span>
|
|---|
| 170 | <p>
|
|---|
| 171 | This happens when:
|
|---|
| 172 | </p>
|
|---|
| 173 | <ul>
|
|---|
| 174 | <li>Two clients try use the same screen name
|
|---|
| 175 | <p>
|
|---|
| 176 | Each client must have a unique screen name. Configure at least one
|
|---|
| 177 | client to use a different screen name.
|
|---|
| 178 | </p>
|
|---|
| 179 | <li>One client reconnects without cleanly disconnecting
|
|---|
| 180 | <p>
|
|---|
| 181 | It's possible for a client to disconnect without the server knowing,
|
|---|
| 182 | usually by being disconnected from the network or possibly by going
|
|---|
| 183 | to sleep or even crashing. The server is left thinking the client is
|
|---|
| 184 | still connected so when the client reconnects the server will think
|
|---|
| 185 | this is a different client using the same name. Synergy will usually
|
|---|
| 186 | detect and correct this problem within a few seconds. If it doesn't
|
|---|
| 187 | then restart the server.
|
|---|
| 188 | </p>
|
|---|
| 189 | </ul>
|
|---|
| 190 | <li><a name="problem8"></a><span class="fakelink">Server has incompatible version</span>
|
|---|
| 191 | <p>
|
|---|
| 192 | You're using different versions of synergy on the client and server.
|
|---|
| 193 | You should use the same version on all systems.
|
|---|
| 194 | </p>
|
|---|
| 195 | <li><a name="problem9"></a><span class="fakelink">The cursor goes to secondary screen but won't come back</span>
|
|---|
| 196 | <p>
|
|---|
| 197 | This is <a href="faq.html#faq17">FAQ #17</a> and is also mentioned in
|
|---|
| 198 | the documentation for <a href="running.html#asymmetric">using synergy</a>
|
|---|
| 199 | and <a href="configuration.html#asymmetric">configuration</a>.
|
|---|
| 200 | </p>
|
|---|
| 201 | </ol>
|
|---|
| 202 | </body>
|
|---|
| 203 |
|
|---|
| 204 | </html>
|
|---|
