james612 / android-vnc-viewer

Automatically exported from code.google.com/p/android-vnc-viewer
0 stars 0 forks source link

Inconsistent connection behaviour between ports to Linux desktop #118

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?

1. On Asus EEE 701 running stock Xandros release as shipped with netbook,
have vncserver and x11vnc running, so that on port 5900 you can connect to
the main desktop (via x11vnc) and on port 5901 you can connect to a new
desktop (via vncserver). Window manager is standard icewm as shipped with
device.

2. Observe that both FreeVNC for Windows and Jaadu on iPhone will correctly
connect to either port 5900 or port 5901 as expected, displaying the
appropriate desktop and interacting correctly with it.

3. Observe that the latest (Jan 30) build of Android VNC will correctly
connect on port 5901 but will not connect on port 5900. This behaviour is
identical to the version currently available on the Android market.

Expected output: the default desktop on the EEE is shown

Actual output. A message is displayed indicating that the Android VNC
client is waiting for handshake (i.e 'establishing handshake. Please wait').

This message never goes away. If the BACK key is pressed, a dialogue is
displayed to indicate that the session has been terminated. ('VNC
connection aborted').

At this stage the screen remains blank. If BACK is pressed again, control
returns to the connection dialogue. It is possible from this point to
successfully connect to port 5901 following the port 5900 failure, but an
attempt to reconnect to port 5900 will cause the above sequence of events
to repeat. 

Changing colour depth does not resolve the issue.Neither does altering the
'use local bitmap' nor 'local mouse pointer' settings.

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by ajaym...@gmail.com on 8 Feb 2010 at 8:33

GoogleCodeExporter commented 8 years ago
I am having the same issue running TightVNC 1.3.10, but for 5900 and 5901.

Original comment by ryanmul...@gmail.com on 9 Feb 2010 at 7:08