A VNC bug ?

[Martin Valley]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Don't know if I can explain this clearly or not.

 

Computer "A":
   Running TightVNC Server ver 1.3.10
   Set up to use Ports - with main port = 1234
Computer "B":
   Running TightVNC Server ver 1.3.9
   Set up to use Ports - with main port = 1234
Computer "C":
   Running TightVNC Client ver 1.3.9

 

For purposes of this test, all 3 computers on my LAN where I have physical access to them.

 

Using the client on computer "C", I connect to computer "B". From the client, I double-click the VNC Server icon on computer "B". The server's interface window pops up and I can do what ever I want. When I'm done I close the server's interface window. Everything works normally.

 

Using the client on computer "C", I connect to computer "A". From the client, I double-click the VNC Server icon on computer "A". The server's interface window pops up and computer "C" immediately looses it's connection to computer "A"!  When I look at the screen on computer "A", I see that the "Display or port numbers to use:" is showing "Display:" as selected (with a display number of 7 - which I used to use on this machine) instead on "Ports:" !!!  At this point, computer "C" cannot re-connect to computer "A". If I use the mouse on computer "A" to close the VNC window then computer "C" can once again connect to computer "A" (using port 1234).

 

It appears that opening and closing the VNCServer window by using the mouse physically attached to computer "A" works normally but doing the same thing using the client connection, activates the wrong port settings and cuts the client off - but only so long as the serverside window is open!!!

 

Am I doing something wrong or is this a bug introduced in version 1.3.10?

 

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
___________________________________________________________
TightVNC mailing list, VNC-Tight-list@...
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list

[Constantin Kaplinsky]

Hello Martin,

>>>>> Martin Valley wrote:

> It appears that opening and closing the VNCServer window by using the
> mouse physically attached to computer "A" works normally but doing
> the same thing using the client connection, activates the wrong port
> settings and cuts the client off - but only so long as the serverside
> window is open!!!
>
> Am I doing something wrong or is this a bug introduced in version
> 1.3.10?

It rather looks like a bug. However, we were not able to reproduce it
locally, so I'm not sure what's wrong in your case.

Does clearing all the settings (in both HKLM\SOFTWARE\ORL\WinVNC3\ and
HKCU\SOFTWARE\ORL\WinVNC3\) and then entering the settings again affect
the behavior?

--
With Best Wishes,
Constantin



------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
___________________________________________________________
TightVNC mailing list, VNC-Tight-list@...
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list